Skip to content
EmargenEmargenDocs

AdminPage by page

Agent access

Agent access sets the most any agent may do in your organisation, and shows who has one working as them. These are agents your people connect themselves, like Claude Code with a token or Claude signed in from its own app. Agent access explains it. Open the Agent access tab of People, under Admin in the menu.

Open Agent access (opens Emargen in a new tab)

ACME lets agents use every tool. Its administrator has Claude signed in, and an engineer has Claude Code working with a token.

Agent access: Agent permissions, with Topics 11 of 11, Your notes 5 of 5, Building 7 of 7, Published requirements 3 of 3 and Initiatives 3 of 3, and the button Change agent permissions; People's agents, with Ana Ruiz's Claude (Sign-in, last used 12 Oct) and Jonas Berg's Claude Code on my laptop (Token, last used 12 Oct).Agent access: Agent permissions, with Topics 11 of 11, Your notes 5 of 5, Building 7 of 7, Published requirements 3 of 3 and Initiatives 3 of 3, and the button Change agent permissions; People's agents, with Ana Ruiz's Claude (Sign-in, last used 12 Oct) and Jonas Berg's Claude Code on my laptop (Token, last used 12 Oct).
  1. Agent permissions. The most any agent may do, token or sign-in. Each person can allow their own agents less, never more.
  2. An area of Emargen’s tools, and how many of them agents may use.
  3. Change agent permissions. Opens the list of tools.
  4. People’s agents. Every agent working as one of your people. Only names and dates show, never what an agent read or wrote.
  5. An assistant that signed in: Sign-in, and its name.
  6. An agent with a token: Token, and the name its person gave it.
  7. Last used. When it last did something here, or Never.

The tools are grouped under Topics, Your notes, Building, Published requirements and Initiatives. The tools describes each one.

Choosing the tools

Section titled “Choosing the tools”

Change agent permissions opens Agent permissions, which applies to every token and assistant at once. Its switch, Agents may use every tool, including new ones, starts on. Turn it off to choose tool by tool. Each tool shows under its area, with its name for agents and Reads or Changes. Untick what agents may not use, and Save.

The Published requirements area: Search published requirements and Read a published requirement ticked, Export a requirement bundle unticked, each with its name for agents and Reads; 2 of 3 under them.The Published requirements area: Search published requirements and Read a published requirement ticked, Export a requirement bundle unticked, each with its name for agents and Reads; 2 of 3 under them.
  1. A tool agents may use.
  2. Its name for agents, and Reads: it only reads.
  3. A tool no agent may use here.

Untick a tool, and every agent loses it at its next call, even one whose person allowed it. People see it greyed out on their own Security page. With the switch off, a tool Emargen adds later stays off until you tick it. Four tools under Topics show a raw label instead of their own name.

See Decide what agents may do.

Revoking someone’s agent

Section titled “Revoking someone’s agent”

Click an agent in People’s agents to select it.

People's agents with Jonas Berg's Claude Code on my laptop selected and the Revoke button under it.People's agents with Jonas Berg's Claude Code on my laptop selected and the Revoke button under it.
  1. Revoke. Asks first, naming whose agent it is, then stops it at once.

The agent leaves the list. Its person can make a new token or connect again. Emargen doesn’t tell them, so let them know why.

Empty

Section titled “Empty”

Before anyone connects an agent, People’s agents says “Nobody has an agent working as them yet.”

Access

Section titled “Access”

People who may manage roles see the tab. You also need the permission Manage organisation settings to open it. Administrators have both. Without the second, it says “Only people who manage the organisation’s settings see this.”. What agents may do covers the rest.