Features and delegations
Choose who gets Agentic Code Review, Automations, and Standup, and hand the Billing, Usage, and Audit log pages to people who aren't Admins.
Workspace settings › Features holds the workspace’s features, the access you delegate to individual people, and the audiences that both can point at. Under them, Early access lists any betas the Evergreen team has given your workspace and who has them. Only the Evergreen team changes those.
Workspace features
A workspace feature is something you can turn on for some people and off for others.
| Feature | What it does |
|---|---|
| Agentic Code Review | An agent reviews each session’s branches before its pull request opens. |
| Automations | Workflows that start a session when an event arrives or a schedule comes round. |
| Standup | A page of what each person shipped, has in flight, and is waiting on, drafted from their sessions. |
For each feature, Who gets it has three choices:
- Everyone means everyone in the workspace, including people who join later. This is the default.
- Audiences means only the people in the audiences you pick.
- Nobody turns it off for the whole workspace.
Admins aren’t exempt. If you choose audiences and an Admin isn’t in one, they don’t get the feature. Evergreen asks you to confirm before it narrows a feature, and says what changes for the people who lose it:
- Agentic Code Review. Their pull requests open without a review, starting at the next turn end of their running sessions. Past reviews stay.
- Automations. Their automations stop firing. Events that arrive are recorded and start nothing, and schedules skip. Nothing is deleted or changed, so widening the choice again restores exactly what was there, but the events you missed aren’t replayed.
- Standup. The Standup page and the Standup band on their profile go away, and no deck is drafted for them. Past decks stay.
Someone without a feature sees that it isn’t on for them, with a pointer to Workspace settings › Features.
Audiences
An audience is a named set of people. Use one when you want to point several choices at the same group, such as a feature, a delegation, an integration, or a budget.
- Under Audiences, choose New audience.
- Give it a Name and, if you like, a Description.
- Add the people.
Names are unique in a workspace. An Admin can’t add the Owner or another Admin to an audience. Deleting an audience takes away whatever it gave its members, unless they have it another way.
Your identity provider’s group rules can also put people in an audience. Those people show a tag in place of Remove, and they leave the audience when they leave the group in your provider.
Note
Audiences are separate from the People groups that your identity provider can push through SCIM. A People group doesn’t gate anything by itself, but a group rule can use it to give people a role or an audience.
Delegated access
Three pages in Workspace settings are open to people who aren’t Admins, once you give them the access. Delegated access is where you do it. You can give it to any active person or to an audience. Agent accounts can’t hold it.
| Delegation | What it opens | Who has it without a grant |
|---|---|---|
| Billing | The balance, usage, payments, statements and, to read, the budgets. | Owner and Admins. |
| Usage | Every view on the Usage page, and its CSV exports. | Owner and Admins. |
| Audit log | The Audit log page and its export. | The Owner, at first sign-in. |
The Audit log is different. Admins don’t hold it by role, so you have to grant it to them like anyone else. The Owner holds it from their first sign-in, and you can take it away.
Billing is handy for someone in finance. They can see and manage the balance without being able to change roles or integrations. They can read the budgets, but only Owners and Admins can change them. See Billing for what they see.
An Admin can grant a delegation to anyone they could change the role of, and to themselves.
If the Evergreen team has given your workspace the Impact beta, Delegated access also lists Impact and People data. Nobody holds either by role, so an Admin grants them like any other delegation.
Last updated