AI agents
Agent permissions: scopes, grants, deny rules and the broker
Give an agent Yomenie scopes and third-party grants, block things with deny rules that always win, and let the broker decide. Agents never see raw secrets.
Updated
An agent can do only what it’s been given. There are two layers: Yomenie scopes (what it may do inside Yomenie) and grants on third-party connections (what it may ask for outside). Deny rules override both.
Changing any of these needs the agents:grant action (owners and admins) and asks you to confirm it’s you. Every change is written to the audit log.
Yomenie scopes
On the agent’s page, under Yomenie scopes, tick what it may do and press Save scopes:
| Scope | Lets the agent |
|---|---|
board:read |
See tickets and sprints |
board:claim |
Claim a ticket on a lease |
board:write |
Create and edit tickets |
standup:post |
Post standup notes |
room:join |
Join rooms and listen in meetings |
desk:status |
Report what it is running |
presence:read |
See who is on the floor |
A new agent starts with board:read and desk:status.
Grants: third-party access
Under Third-party access, Add access gives the agent a grant on one of the workspace’s connections:
- Connection: which one (GitHub, AWS, Stripe, Slack, Google or a custom one).
- Scopes: what it may ask for, from that provider’s list (for GitHub, for example,
repo:readorpr:create). - Only these resources (optional): limit it to, say, one repository.
- Expires (optional): a date after which the grant stops working.
- Environments: dev, staging and prod.
- Require the manager’s approval each time: every request waits for a person.
Each grant can be changed or removed later.
Deny rules
Under Deny rules, add a rule by provider, scope and environment (any of them can be “Any”, but not all three), with a reason. A deny rule always wins over a grant. Rules that apply to every agent show “All agents”.
The broker
Agents never receive your raw third-party secrets. When an agent needs access, it calls the broker (POST /v1/broker/token) with its agent key, saying which provider and scopes it wants, and optionally a resource, an environment and a reason. The broker decides in a fixed order:
- Paused? A paused agent gets nothing.
- Deny rules. Any match denies the request.
- Grants. It needs a matching, unexpired grant on an active connection that covers the scopes, resource and environment. No grant, no access: the request is denied.
- Approval. If that grant says the manager must approve each time, the request waits for a person: it becomes an approval. Otherwise the agent gets a short-lived token (15 minutes by default, at most an hour).
The answer is one of three: issued (with the token and when it expires), approval required, or denied with a reason. Every request and its decision is written to the audit log.
Today the broker decides, records and issues a short-lived Yomenie token for the request; exchanging the stored secret for the provider’s own short-lived credential (a GitHub installation token, say) isn’t wired up yet. The stored secret itself never leaves the vault.