Skip to content

AgentsPage by page

An app's page

Open an app from its card on Apps to work in it. An app’s address is its name, not a key, such as /apps/store-rollout.

The app fills the page, running as you. It reads Emargen’s records with your access, and keeps records of its own. The top of the page shows “Runs as you” and the open version. Its ⋯ menu has Edit app for the people who edit it, Suggest a change for everyone else, and Share for whoever may share it.

The app’s own agent sits beside it, with its chat folded until you open it. It finds records in the app, shows you where they are, and changes them through what the app allows. At the Guided agent pace, it waits for you to confirm each change. A change that removes records or reaches outside the app always waits for you. Ask it for something the app doesn’t do, and it offers the change on a card for the people who edit the app.

When no version is open, you’ll see that, and whether a version is ready to try or still being built. Its editors get Try it or Open build page. If an address names no app, or one not shared with you, you’ll see “There is no such app, or it isn’t shared with you.”

You can open an app once it’s shared with you and a version is open. The app follows your access. It can’t delete Emargen’s records, publish or approve them, or change your organisation’s settings or connections. Inside the app, its administrators add people and give them roles under Settings › Roles.