Integrations and policies
Decide who in your workspace can connect each integration, block the tools you don't want the agent to use, and answer requests from members.
Owners and Admins manage integrations in Workspace settings › Integrations. Everyone else sees the integrations you’ve made available and connects their own account to the ones they’re allowed to use. For installing the GitHub App and linking accounts, start with Connect your code.
Choose who can use an integration
Open an integration and go to Who can use it. Pick one of these:
| Choice | What it means |
|---|---|
| Everyone | Anyone with an account in the workspace can connect it. This is the default for a new one. |
| Selected audiences | Only people in the audiences you pick. |
| Nobody yet | Everyone sees it with a Request button, but nobody can connect it yet. |
| Only me | Only the Admin who chose it can connect it, so they can try it first. Everyone else sees Request. |
Someone outside the audience can’t connect the integration, even with a direct link.
When you add an integration, its drawer opens on Who can use it. If nothing else is left to set up, saving your choice there turns the integration on with that audience. If a step is still left, such as a setting or a sign-in, Evergreen keeps your choice and turns the integration on once you finish that step. After an integration has been on once, saving Who can use it changes only the audience. Integrations covers the install steps.
The drawer for each integration has four tabs: Overview, Who can use it, Tools, and Connections. Code hosts have a tab of their own for their repositories, bot, or groups. Under Connections you can see who has connected it.
Remove an integration
Removing an integration revokes the tokens of everyone who connected it and deletes their connections, settings, blocked tools, and requests. It works even while people are connected, so check Connections first.
Block tools
On the Tools tab, Blocked tools lists the tools an integration offers. Block any you don’t want the agent to use. A blocked tool isn’t offered to the agent in anyone’s session, starting with the next run. If a session already has it, the call is refused the next time the agent tries it.
Answer requests
When an integration is set to Nobody yet, or someone isn’t in its audience, they can choose Request and say what it’s for. Identical requests are merged, and the requester can withdraw theirs.
-
Find the requests
On Workspace settings › Integrations, use the Requests filter.
-
Approve or decline
Choose Approve and pick who gets it: everyone in the workspace (Everyone at and your workspace’s name), Their audiences, which is already picked, or Choose audiences. Evergreen gives access by audience, so anyone who asked and isn’t in a picked audience keeps waiting. Or choose Decline, and fill in Tell them why if you like. The requester sees your name and the note.
The requester is told in Evergreen’s notifications either way. Only Owners and Admins can decide a request.
A request for an integration that isn’t installed yet shows Install now in place of Approve. A request for a new server shows Review and install, which opens Add provider with the server’s address filled in. Adding the server approves the request. See Add your own server.
Let members connect simple integrations
Some integrations need nothing from you. A member signs in at the vendor and the integration is installed for them alone. This is off until you turn it on.
Choose Settings on the Integrations page and turn on Members can connect integrations that need no setup. It applies only to integrations where you haven’t chosen the audience. Integrations that need your own values or your own app still wait for you to enable them.
Note
Turning the policy off stops new connections. Connections people already made keep working until you change the audience or remove the integration.
Last updated