Screens built for your work

Can we get a screen built around the way we work?

If your team needs a screen built around a job of its own, here is what that takes.

Each such screen, which AIEUS calls a page, has to be written in code, with no way to assemble one by clicking. Whoever is allowed to change the page files can write it, and so can any AI app they connect, such as Claude, since it acts with their access.

New pages and changes to a page reach nobody until an admin, someone with full authority over your space, puts them live. If that step fails, it says why and the old version keeps running. Putting anything live ships whatever the page files then hold, and others may be allowed to edit them, so the admin should check each change first, above all one opening a page to the public.

A finished page can show as a tab in your space's browser app. None starts public, and an admin sets one of three audiences: admins, everyone with an account, or anyone, signed in or not. That choice lives in the page's code and changes only when a new version goes live, and it decides who the app opens the page for, not who can read the data behind it.

Keep people's names, private text and access keys out of a page's code, since anyone who can reach your browser app's web address can read that code, even without signing in.

Pages usually come in packs, bundles with their own data tables and tools. Pack code can act with your space's authority, so install packs only from people you trust.