> ## Documentation Index
> Fetch the complete documentation index at: https://docs.strawberrybrowser.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration permissions

> Configure per-app tool permissions so companions ask, always allow, or cannot use specific connected app actions.

Integration permissions control what companions can do with connected apps.

Use them together with global AI permissions at `strawberry://settings/ai-permissions`.

## Configure tool permissions

1. Open `strawberry://settings/integrations`.
2. Open an integration's detail page.
3. Find **Permissions**.
4. Set each action to one of:
   * **Ask every time**
   * **Always allow**
   * **Disable action**

## Choosing a permission level

Use **Ask every time** for actions that:

* Send messages
* Create, update, or delete records
* Spend money
* Change billing state
* Affect customers, candidates, or teammates
* Access sensitive data

Use **Always allow** for low-risk, frequent actions that are needed for normal work, such as reading non-sensitive lists or checking routine context.

Use **Disable action** when a companion should never use that capability.

## Permanent versus chat-specific permissions

Permanent permissions apply across sessions and are managed in integration settings.

Chat-specific permissions apply only to the current chat and clear when the chat ends.

## Routine considerations

Routines can run while you are not actively watching. Review permissions carefully before giving a routine access to write actions.

For routines, it is often safer to let Strawberry read and draft, then notify you for approval before sending or mutating external systems.

## Audit checklist

Review permissions when:

* You connect a new app.
* You create a routine.
* You share a companion.
* A team member changes roles.
* Your workflow begins touching customer, payment, hiring, or production systems.