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

# Application permissions

> The OAuth permissions the gateway requests when you connect an application, and the risky operations Oleria recognizes in each one.

Every application on this page is connected through OAuth. When you connect one, the provider shows you a consent screen listing what the gateway is asking for. This page sets out exactly what that is, application by application, so you can review it before you connect and answer questions about it afterwards.

The applications below are a sample. Oleria supports more, and documentation for them is being added.

## How permissions are scoped

Oleria requests the same permissions for every tenant. You can't widen them, and neither can an administrator. Google Workspace is the exception - you choose your own permissions when you connect it.

Whatever the list says, OAuth can't give the gateway more access than you already have in the application. If you can't see a private repository, neither can an agent acting as you. Policy narrows that further, and never widens it.

<Note>
  This page covers OAuth applications. Non-OAuth applications are reached with a credential an administrator supplies rather than one tied to you, so their access is whatever that credential carries. See [AI Agent Gateway](/governance/ai-agent-gateway-overview).
</Note>

## Risky operations

Each application has a roster of **risky operations** - the high-impact actions Oleria recognizes and can govern separately from everything else. They are almost all destructive or permission-changing: deleting a repository, deleting a space, changing who can see a site.

These are recognized actions, not blocked ones. An administrator sets a decision for each one - **Allow**, **Allow and Alert**, **Ask**, or **Deny** - and the console shows **Ask** for any operation nobody has set yet. Until an administrator reviews the roster, treat the decisions as unconfigured rather than as protection you already have.

<Note>
  Review every risky operation for an application when you enable it, rather than relying on what the console shows by default. See [Set the application's policy](/governance/ai-agent-gateway-admin-setup#set-the-applications-policy).
</Note>

Actions outside this roster are governed by the policy layers that apply to all traffic, including any custom Rego rules an administrator has written.

## GitHub

Source code, pull requests, issues, and repository management.

| Permission | What it allows                                                                                   |
| :--------- | :----------------------------------------------------------------------------------------------- |
| `repo`     | Full read and write access to repositories, including code, issues, pull requests, and settings. |
| `read:org` | Read organization membership and team structure.                                                 |

`repo` is a broad scope - GitHub does not offer a read-only equivalent that still covers issues and pull requests, so a scope that lets an agent comment on a pull request also lets it push code. Use risky-operation decisions and custom rules to narrow what agents may actually do.

| Risky operation               | What it covers                                       |
| :---------------------------- | :--------------------------------------------------- |
| Delete repository             | Permanently deletes a repository and all its data.   |
| Transfer repository ownership | Moves a repository to another owner or organization. |

## Jira

Issue tracking, sprint planning, and project management.

| Permission        | What it allows                                              |
| :---------------- | :---------------------------------------------------------- |
| `read:jira-work`  | Read issues, projects, boards, and comments.                |
| `write:jira-work` | Create and update issues, comments, and worklogs.           |
| `read:jira-user`  | Read user profiles, to attribute work to the right person.  |
| `offline_access`  | Refresh the connection without asking you to sign in again. |

| Risky operation    | What it covers                                    |
| :----------------- | :------------------------------------------------ |
| Delete issue       | Permanently deletes an issue and its history.     |
| Delete project     | Permanently deletes a project and all its issues. |
| Bulk delete issues | Permanently deletes many issues in one operation. |

## Confluence

Team wiki, documentation, and knowledge base.

| Permission                      | What it allows                                              |
| :------------------------------ | :---------------------------------------------------------- |
| `read:confluence-space.summary` | List spaces and read their basic details.                   |
| `read:confluence-content.all`   | Read page and blog post content, including attachments.     |
| `write:confluence-content`      | Create and update pages and blog posts.                     |
| `offline_access`                | Refresh the connection without asking you to sign in again. |

| Risky operation          | What it covers                                         |
| :----------------------- | :----------------------------------------------------- |
| Delete page              | Permanently deletes a page and its content.            |
| Delete space             | Permanently deletes an entire space and all its pages. |
| Change space permissions | Modifies who can view or edit a space.                 |

## Slack

Team messaging and channel communication.

| Permission         | What it allows                                     |
| :----------------- | :------------------------------------------------- |
| `channels:read`    | List public channels and read their details.       |
| `channels:history` | Read message history in public channels.           |
| `chat:write`       | Post messages.                                     |
| `users:read`       | Read user profiles, to resolve names and mentions. |

Slack is the one application where the gateway requests two sets of permissions. The set above belongs to the Oleria app in your workspace. Alongside it, the gateway requests a second, wider set on your own behalf, so an agent reads the conversations you can read and no others:

| Permission                          | What it allows                                              |
| :---------------------------------- | :---------------------------------------------------------- |
| `channels:read`, `channels:history` | List public channels and read their history, as you.        |
| `groups:read`, `groups:history`     | List private channels you belong to and read their history. |
| `im:read`, `im:history`             | List and read your direct messages.                         |
| `mpim:read`, `mpim:history`         | List and read your group direct messages.                   |
| `search:read`                       | Search messages you have access to.                         |
| `users:read`                        | Read user profiles.                                         |

This second set is why an agent can reach a private channel or a direct message at all - the app-level permissions above cover public channels only. Slack shows both sets on the consent screen, under separate headings.

| Risky operation              | What it covers                                         |
| :--------------------------- | :----------------------------------------------------- |
| Delete channel               | Permanently deletes a channel and its message history. |
| Remove member from workspace | Revokes a user's access to the workspace.              |
| Archive channel              | Archives a channel, removing it from active use.       |

## Google Workspace

Gmail, Google Drive, Calendar, Docs, and Sheets.

Google Workspace works differently from the others. Instead of a fixed list, you choose your own permissions when you connect it, and the gateway requests only what you selected.

| Product         | Permission you can select      | Selected by default |
| :-------------- | :----------------------------- | :------------------ |
| Gmail           | Read emails                    | Yes                 |
| Gmail           | Send emails                    | No                  |
| Gmail           | Manage emails and labels       | No                  |
| Google Drive    | View files                     | Yes                 |
| Google Drive    | Edit files created by this app | No                  |
| Google Drive    | Full Drive access              | No                  |
| Google Calendar | View events                    | Yes                 |
| Google Calendar | Create and edit events         | No                  |
| Google Docs     | View documents                 | No                  |
| Google Docs     | Edit documents                 | No                  |
| Google Sheets   | View spreadsheets              | No                  |
| Google Sheets   | Edit spreadsheets              | No                  |

The defaults are read-only: read your email, view your Drive files, view your calendar. Select at least one permission, and add write permissions only if your agents need them. Every selection is also requested as an identity permission (`openid`, `email`, `profile`) so Oleria knows which account you connected.

To change your selection later, disconnect Google Workspace and connect it again. The picker reopens with your current selection already ticked, so you are adjusting it rather than starting over.

| Risky operation               | What it covers                                          |
| :---------------------------- | :------------------------------------------------------ |
| Delete user                   | Permanently deletes a user account and its data.        |
| Suspend user                  | Suspends a user's access to all Workspace applications. |
| Permanently delete Drive file | Permanently deletes a Drive file, bypassing trash.      |

## Salesforce

CRM platform for sales, service, marketing, and analytics.

| Permission                        | What it allows                                                                     |
| :-------------------------------- | :--------------------------------------------------------------------------------- |
| `api`                             | Access Salesforce data through the API, bounded by your profile and sharing rules. |
| `refresh_token`, `offline_access` | Refresh the connection without asking you to sign in again.                        |

Salesforce has no per-object OAuth scopes. `api` grants access to everything your own Salesforce profile, permission sets, and sharing rules already allow - so what an agent can reach is decided by your Salesforce permissions, not by the scope list.

To connect Salesforce through a connected app you own rather than Oleria's, see [Bring your own OAuth app](/governance/ai-agent-gateway-byo-oauth).

| Risky operation      | What it covers                                       |
| :------------------- | :--------------------------------------------------- |
| Mass delete records  | Permanently deletes many records in one operation.   |
| Modify sharing rules | Changes record visibility and access across the org. |
| Delete record        | Permanently deletes a record.                        |

## SharePoint

Intranet and document management - sites, document libraries, and lists.

| Permission            | What it allows                                                 |
| :-------------------- | :------------------------------------------------------------- |
| `Sites.ReadWrite.All` | Read and write items in all site collections you can access.   |
| `Files.ReadWrite.All` | Read and write files in all document libraries you can access. |
| `User.Read`           | Read your own profile, to identify the connected account.      |

Both `.All` permissions are delegated, meaning they apply only to the sites and files your own account can already reach. They do not grant tenant-wide access.

| Risky operation         | What it covers                                            |
| :---------------------- | :-------------------------------------------------------- |
| Delete site             | Permanently deletes a site and all its content.           |
| Delete item             | Permanently deletes a list item or document.              |
| Change site permissions | Modifies who can access a site.                           |
| Write file              | Creates or overwrites file content in a document library. |

## Reviewing and revoking access

The Governance App, under **AI Agent Gateway**, shows which applications you have connected.

To revoke access, disconnect the application there. Oleria deletes the stored credential, and agents lose access to that application on their next call.

## Contact us

For questions, contact us at [support@oleria.com](mailto:support@oleria.com).