Choose what a project can use

Switch a workspace integration on for one project, choose its account, and set what the project's agent may do with it.

An integration is connected once, for the whole workspace. A shared project does not inherit it: every new project starts with every integration switched off, and its agent can use none of them until someone switches one on, for this project or for every project.

That is on purpose. Connecting the company mailbox is one decision. Letting the Marketing project’s agent send from it is another, and it is often made by someone else.

Tendo works the other way round. Apps you connect under your own settings are on for Tendo unless you switch them off, and no shared project can reach them.

Switch an app on for this project

You need editor access on the project. Organization admin is not required.

There are three other ways a project gets an app switched on:

• The organization’s Integrations page. An app’s page there has On for every Project, a default for every shared project.
• The New Project dialog. Its Integrations chips let you pick what the new project starts with; the rest stays off. See Create a project.
• In a conversation. When the agent needs an app that is connected but off here, its reply carries a card with Enable. One press by an editor, and the conversation carries on.

The organization’s switch is only a default. The project’s own switch always wins: on for every project but off here means off, and off for the organization but on here means on.

Paper is a built-in toolkit that is always on, so it has no switch.

Which account it uses

A workspace can hold several accounts for one service, like two mailboxes, or a client’s store next to your own. Under the switch, Access in this Project has an Accounts list. It starts at Any account.

Narrow it to one account, or a few, when this project should only ever touch those. When more than one account is available, the agent has to name one for every call and never guesses, so narrowing the list settles the question in advance. Clearing the list takes you back to Any account. To stop the project using the app, switch it Off.

When the project has more than one channel, a Per channel list appears too. Each channel can keep Same as Project or be set to Off.

What the agent may do

Access in this Project also sets the mode:

• Read only: the agent can fetch, search and report. A write is refused.
• Read and write: it can also create and change things, such as drafting and sending, updating a record, or posting.
• Full access: it can also make calls that cannot be undone, such as deletes. Each one still asks you first.

A channel can narrow what the project allows, never widen it. It can switch an app off for that channel, but it cannot switch on an app the project has off.

Approvals

The agent asks before any integration call that cannot be undone: deleting, cancelling, refunding, archiving, revoking. Creating and updating run without asking. Separately, a paid data lookup asks before it spends once the estimate reaches about 100 credits, and the card shows the figure, for example “About 540 credits for up to 25 rows from Ahrefs.”

The card is one sentence and a row of buttons. It names the call and shows what it will be sent with. Everyone in the conversation sees it, any editor of the conversation can answer it, and Auttendo records who did.

• Approve runs the call once.
• Deny stops it there. The agent does not carry on, and a denied paid lookup costs nothing.
• Approve always appears on integration calls, not paid lookups. It covers that one call in that channel from now on, and the card prints what it will cover before you agree. The app’s access settings list these under Runs without asking, and Ask again withdraws one.

Approve always never widens the mode. A delete you approved for good is still refused while the app is set to Read and write here. The mode is the ceiling; a standing yes only works underneath it.

Resource access

One account can reach many separate things, like thirty repositories. Resource access is a project’s permission to use one particular resource through an integration. GitHub, Sanity and Vercel have it.

Take GitHub. In the project’s Integrations section, GitHub’s page ends in a Resource access block. A grant is three choices: the Connected account, whether it applies to the whole project or one channel, and the repository, picked from a searchable list. Only repositories that account can already push to are offered. Save access writes the grant, Add resource adds another, and Edit access or Remove access change it later. A removal takes effect straight away, including for work already in progress.

Granting and selecting are different acts. Naming a repository in a request picks among what the project has already been granted; it grants nothing. If the block says “No resources granted to this Project.”, the agent has no repository to work in and will tell you so.

The agent cannot grant itself resource access or widen what it has. Only a person does that, in settings.

Troubleshooting

The app is connected for the workspace, but the agent can’t use it here

It was never switched on for this project. Every shared project starts with every integration off, including ones connected long before the project existed. Switch it on in the project’s Integrations section, or press Enable on the card the agent shows. Either needs editor access on the project.

The agent says an app is read-only here

The agent is telling you the truth: the app’s mode in this project doesn’t allow that call, so it was refused before any approval card could appear. An editor can change the mode under Access in this Project. Approve always won’t help; it never goes past the mode.

The agent asks which account to use

The project can use more than one account for that app, and the agent won’t guess. Name the account in your request, or narrow Accounts under Access in this Project to the one this project should use.

The agent says it has no repository to work in

Nothing has been granted under Resource access for this project, or not for this channel. Naming a repository in the conversation doesn’t grant it. An editor adds it on the app’s page in the project’s Integrations section.

Related

• Integrations — what an integration is and who holds it.
• Connect an integration — add an account to the workspace.
• Share a project — who gets editor access.
• Instructions and memory — tell the agent how to use what it can reach.