> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/identity-access-and-administration/connection-access-and-execution-identity.md).

# Connection Access and Execution Identity

A person who runs a workflow and the account that an action uses in an external service can be different. Check the action's connection settings before sharing a workflow that reads or changes provider data.

{% embed url="<https://1957915746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FfJ64MVBQ6xkniS4rpnOj%2Fconnection-access-and-execution-identity.mp4?alt=media&token=2c634d96-9d67-415f-b7c9-0b88c69b4613>" %}
A short walkthrough of connection access and execution identity.
{% endembed %}

## Key concepts

| Term                     | Meaning                                                                                                                                        |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Run identity             | The authenticated person or application starting the StackAI run.                                                                              |
| Provider identity        | The provider user or application represented by a saved connection. Its provider permissions determine which external resources it can access. |
| Saved connection         | Authorization for a provider account, selected in an action's settings.                                                                        |
| Delegated authentication | A supported action configuration that resolves a connection for the verified end user instead of using one fixed saved connection.             |

## Which account does the action use?

| Configuration                                   | Provider account used                                                        | What to check                                                                                                                                                                            |
| ----------------------------------------------- | ---------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A fixed saved connection is selected            | The account authorized in that saved connection                              | Check the account and its provider access. A different person running the workflow does not by itself replace this connection.                                                           |
| The action uses delegated authentication        | The connection resolved for the verified user and configured connector       | The run must have a verified user identity. The user may need to connect or reconnect the provider account.                                                                              |
| A saved connection uses application credentials | The provider application or service account represented by those credentials | Check application permissions and explicit resource grants, such as SharePoint site access. The workflow viewer's personal provider permissions do not replace the application's grants. |

Delegated authentication is a configuration of supported actions. It is not implied by a chat conversation ID, email field, or the fact that the workflow has multiple users.

## Check the identity before sharing a workflow

1. Open each provider action and inspect its connection settings.
2. For a fixed connection, confirm which provider account is authorized. Choose an account with the access required for the action.
3. For a delegated action, confirm that the intended user can complete the provider connection flow in the interface that will run the workflow.
4. Run a read operation with the intended user and a resource they should be able to access. Check the returned resource and the account used. An owner's successful run is not sufficient evidence of another user's access.

See [connection ownership and sharing](https://docs.stackai.com/technical-reference/connections-and-tool-execution/connection-ownership-sharing-and-permissions.md) for StackAI access controls. Use the provider's catalog page for OAuth scopes, service-account permissions, and resource grants.

## When access fails

| Symptom                                                | Check                                                                                                                                                     |
| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Connection is missing or unavailable                   | Confirm the organization, selected connection, and the user's access to it. For delegated authentication, complete the required end-user connection flow. |
| Reconnection is requested                              | Reconnect the account shown in the request. Creating an unrelated connection does not repair the selected account's authorization.                        |
| Authentication succeeds but a file or record is denied | Check provider permissions and access to that specific resource. For app-only SharePoint, check both consent and the site grant.                          |
| Results differ between users                           | Compare the authentication configuration and resolved provider accounts before changing the workflow logic.                                               |

## Limits of this reference

Provider-action identity and knowledge-base retrieval access are separate controls. For indexed documents and permission filtering, see [Source Permissions and Retrieval Access](https://docs.stackai.com/technical-reference/files-knowledge-and-retrieval/source-permissions-and-retrieval-access.md). A memory or conversation identifier is not an authorization credential.

## Related resources

[Organization Roles and Permissions](https://docs.stackai.com/technical-reference/identity-access-and-administration/organization-roles-and-permissions.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/technical-reference/identity-access-and-administration/connection-access-and-execution-identity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
