Access tiers
Every message that starts a turn comes from a speaker, and every speaker has a tier.
There are three tiers, from most to least trusted: owner, admin, and member.
The bot ignores messages from people without a tier.
The default: only the owners
Section titled “The default: only the owners”With no admins or members under access, only the owners can talk to the agents.
An owner is a person listed in access.owners; roundtable init writes you as the first one, under your Discord user id.
The bot ignores other bots and answers only in agents’ and groups’ channels.
Giving other people a tier
Section titled “Giving other people a tier”List people under access in roundtable.config.ts.
Each tier takes identities, roles, or everyone:
export default { // ... access: { owners: [ { name: "Ada", principal: env("OWNER_ID"), identities: [`discord:${env("OWNER_ID")}`], }, ], admins: { identities: ["discord:<user id>"] }, members: { roles: ["discord:role:<role id>"] }, },} satisfies RoundtableConfig;| Field | Type | Meaning |
|---|---|---|
identities |
list of strings | Accounts written <provider>:<subject>, such as discord:<user id>. |
roles |
list of strings | Roles written <surface>:role:<name>, such as discord:role:<role id>. Anyone who holds one of these roles qualifies. |
everyone |
true, false, or a list of surfaces |
true admits every person on every surface; a list, such as ["discord"], only on those surfaces. |
A person gets the highest tier they qualify for: an owner first, then admins, then members.
everyone works under both admins and members.
Under admins it would make every person who writes in an agent channel an admin, so use it under members at most.
Linking accounts to one principal, with roundtable principal link, makes them one person with one tier.
A configuration written in the 0.8 form, owner and speakers with Discord user and role ids, still works and prints a deprecation warning.
roundtable upgrade rewrites it as access; the two forms cannot be mixed.
What each tier can do
Section titled “What each tier can do”A tool is offered to a speaker only when the speaker’s tier is at least the tool’s minimum tier. The table shows the tiers that the core and the built-in addons declare. The agent tools reference lists every tool with its tier.
| Tier | Can use |
|---|---|
member |
Talk to the agents and answer their own questions. Read attachments. List and read agents (agent_list, agent_get), read channels (channel_read), and message agents (message_agent). Use memory (memory_add, memory_search, memory_remove) and list schedules (schedule_list). |
admin |
Everything a member can, plus create and edit agents and groups, archive them, arrange channels, change skills and agent skills, create and change schedules, and delegate tasks. |
owner |
Everything else: the shell and file tools, notify, the discord_* administration tools, every plugin tool that does not declare a lower tier, and the /roundtable slash command. |
- Each speaker has a memory of their own, shared by all agents.
A member’s
memory_addwrites to that member’s memory. - The stop button on a long turn answers only the owner.
- A held action, such as a destructive shell command, waits for approval on a card. By default the speaker whose turn held it approves it, as long as their tier still holds the call; in a shared conversation an owner can approve too, on the card or by a confirming message. In a private conversation nobody else can, and a call above the speaker’s tier is not approved there.
- A question an agent asks with
ask_usercan be answered by the speaker whose turn asks it, and in a shared conversation by an owner. A set of questions is one card with the same rule; itsPreviewsbutton only shows the previews, so anyone who sees the card may press it. A Cancel button besideSubmitlets whoever may answer cancel the question: the agent is told it was cancelled and does not ask again.
Changing a tool’s tier
Section titled “Changing a tool’s tier”toolTiers sets the lowest tier that may use a tool, by tool name:
export default { // ... toolTiers: { delegate_task: "member", memory_remove: "admin", },} satisfies RoundtableConfig;The setting wins over everything else.
Without it, a tool needs the tier its plugin declared; failing that, the core’s default; and a tool nobody named needs the owner.
Each value must be "owner", "admin", or "member".
What other speakers see: the guest prompt
Section titled “What other speakers see: the guest prompt”Admins and members get the guest prompt in place of the shared prompt.
The agent also receives a section that names the speaker, their Discord user id, and their tier, and tells it to address them, to take their answers and approvals, and that tools above their tier are not available this turn.
Their messages reach the agent prefixed with (Message from <name>, at the <tier> tier.).
Set the guest prompt with a file path, next to the shared prompt:
export default { // ... prompts: { shared: "./persona/shared.md", guest: "./persona/guest.md", },} satisfies RoundtableConfig;Both files are read once, at start.
An unreadable or empty file stops the start and names the key, for example config prompts.guest: <path> is empty. Write the prompt in it.
Without prompts.guest, the bot uses the guest prompt bundled with the package.
It tells the agent that the person is a guest of the server, that it does not speak for the owner, that the owner’s private facts stay the owner’s, and that what it stores in memory is the guest’s alone.