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

# Cross App Access

> Let your identity provider decide which apps your users reach through StackOne, with no per-app sign-in.

Cross App Access (XAA) creates a [Linked Account](https://docs.stackone.com/gateway/concepts/linked-accounts.md) for each user on each app you allow in your identity provider (IdP), when they sign in to StackOne through your SSO connection. XAA is an open protocol: StackOne asks your IdP for each user's access, so your IdP's policy decides who gets it and who keeps it.

> [!NOTE]
>
> XAA is in early access. If you don't see the **Cross App Access** card on your SSO connection, contact StackOne support to turn it on.

Before setting up XAA, you need:

* A verified [SSO connection](https://docs.stackone.com/secure/identity-and-access/authentication/sso/overview) through an IdP StackOne supports for XAA. Today that's [Okta](#okta), with the connection's **SSO URL (Entry Point)** on `okta.com`, `oktapreview.com`, or `okta-emea.com`. Custom domains aren't supported yet.
* The **Organization Admin** role in StackOne.
* For each app, your own OAuth app registered in it, with XAA allowed and the scopes its Connector Profile requests enabled, and that app's client ID and client secret. StackOne support sends each app's resource identifier when it turns on XAA.

## Who gets Linked Accounts

StackOne creates a user's Linked Accounts on each [Connector Profile](https://docs.stackone.com/gateway/concepts/connector-profiles.md) with **Link accounts at SSO sign-in** turned on, in every project where they're a Project Admin or Project Member. Organization Admins get them only in projects they've been added to, and a [Restricted](https://docs.stackone.com/secure/identity-and-access/roles-and-groups/connector-profile-access.md) profile links only for the users and groups granted access. Users added by [Just-in-Time](https://docs.stackone.com/secure/identity-and-access/manage-team/jit.md) or SCIM Provisioning get the role chosen under **Provisioned access**, so choose the Project Member or Project Admin role there.

* Users signed in before setup get their Linked Accounts at their next SSO sign-in.
* A Linked Account acts as its user in the app. Organization Admins and Project Admins can run actions with it unless [explicit account access](https://docs.stackone.com/secure/identity-and-access/roles-and-groups/overview#explicit-account-access) is enabled.
* StackOne asks your IdP for the scopes the Connector Profile requests when users connect the app themselves, without `offline_access` and the OpenID Connect scopes. Your IdP grants them only if its policy allows them.
* Access lasts until your IdP's grant for the user expires: with Okta, 90 days after their last SSO sign-in. When a Linked Account is used after its token expires, StackOne gets a new one through your IdP, so its current policy applies.

## Start in StackOne

**1. Turn on linking in each app's Connector Profile**

In each project that should get Linked Accounts, for each app you allow in your IdP:

1. [Add a Connector Profile](https://docs.stackone.com/gateway/quickstart.md#setup-connector-profile) for the app, or edit the one you have.
2. Set **Authentication Type** to the app's OAuth or MCP option.
3. Enter your app's **Client ID** and **Client secret**. Linking needs the client ID even where the option would otherwise leave it optional.
4. Check that **Link accounts at SSO sign-in** is on. It's on by default for a new profile, and you can turn it on or off later from the profile's settings.
5. Save the profile.

Users can still connect the app themselves through the profile's own flow.

**2. Copy the public key URL**

1. Go to [**Organization > Security > SSO**](https://app.stackone.com/organization/security/sso).
2. Open your SSO connection.
3. On the **General** tab, copy the **Public key URL** from the **Cross App Access** card.

Your IdP fetches StackOne's current key from this URL, so there's no key for you to rotate.

## Register StackOne's Agent identity

In your IdP, register StackOne's Agent identity with the public key URL, allow it each app, and copy the client ID your IdP gives it.

### Okta

You need Okta Identity Engine and the **Super Administrator** role in Okta. XAA is included in Okta Workforce SSO. Your StackOne SSO app in Okta must sign the assertion (**Assertion Signature**: `Signed`, Okta's default), because an app that signs only the response still signs users in but can't link accounts.

Switch to the Okta Admin Console, where StackOne's Agent identity is an AI agent.

**1. Register the AI agent**

1. Go to **Directory > AI Agents**.
2. Click **Register AI agent**.
3. Under **Profile**, enter a name, for example `StackOne`.
4. Click **Next**.

**2. Link it to your StackOne SSO app**

1. Under **User access and authentication**, choose **Select an existing app**.
2. Select your StackOne SSO app.
3. Click **Next**.

StackOne uses your users' existing SSO sign-in. The SSO app itself doesn't change.

**3. Add StackOne's public key**

1. On the **Client registration** tab, click **Configure** next to **Okta-generated client ID**.
2. Select **Public/private key**.
3. Choose **External**.
4. Enter the **Public key URL** from StackOne as the **JWKS URI**.
5. Click **Activate**, then **Enable**.

**4. Add a resource connection for each app**

1. Open the **Resource connections** tab.
2. Click **Add resource connection**.
3. Select the app.
4. Set the following:
   * **Client ID**: your app's client ID, the one in the Connector Profile.
   * **Resource identifier**: the app's resource identifier from StackOne support.
   * **Scopes**: select **Allow any scope**, or select **Allow specific scopes** and add the scopes the app's Connector Profile requests.
5. Click **Add**.

**5. Copy the client ID**

On the **Client registration** tab, copy the **Client ID**. It starts with `wlp`.

## Finish in StackOne

Switch back to the **Cross App Access** card in StackOne.

**1. Add the client ID**

1. Click **Edit client ID**.
2. Enter the **Client ID** from your IdP.
3. Click **Save changes**.

**2. Check that it works**

1. In a private window, sign in to StackOne through your SSO connection as a user who has been added to one of those projects as a Project Admin or Project Member.
2. Open the project's [Accounts page](https://app.stackone.com/accounts).

The user has a Linked Account for each app you connected.

## Stop access

* To stop a user, unassign them in your IdP.
* To stop an app, remove the Agent identity's access to it in your IdP (in Okta, its resource connection).

Both take effect when the app's current access token expires. Clearing the client ID in StackOne stops new Linked Accounts, and so does turning off **Link accounts at SSO sign-in** on an app's profile. Existing ones keep working until their grant from your IdP expires, or until you delete them. While the client ID is set, a deleted Linked Account comes back at the user's next SSO sign-in, so to remove it for good, stop access in your IdP or clear the client ID.

## What users see

When users [connect an AI platform](https://docs.stackone.com/ai-platforms/overview.md), StackOne's consent screen lists their Linked Accounts, and no app asks for its own consent. A Linked Account created later appears once they reconnect the AI platform.

## Troubleshooting

A Linked Account that failed to link appears at the user's next SSO sign-in once the cause is fixed. The quoted messages appear inside the errors AI platforms show. If a Linked Account is still missing, send StackOne support the user's email and when they signed in.

| Symptom | Likely cause | Fix |
| - | - | - |
| A user has no Linked Accounts | They were signed in before setup, or signed in with a password instead of SSO. | The user signs out of StackOne and signs in again through SSO. To make SSO the only way in, [require SSO](https://docs.stackone.com/secure/identity-and-access/authentication/sso/overview#require-sso). |
| No user gets Linked Accounts, or "Your identity provider does not recognize StackOne's Agent identity or its key" | The client ID in StackOne doesn't match the Agent identity, or its client registration isn't active. | Check the **Agent identity client ID** on the card, then the Agent identity's client registration in your IdP (in Okta, the AI agent's **Client registration**). If you replaced the Agent identity, users sign in again. |
| "Your identity provider does not allow StackOne's Agent identity to request access" | The Agent identity isn't linked to your StackOne SSO app, or the Connector Profile requests a scope the Agent identity isn't allowed for the app. Okta reports a scope it doesn't allow this way. | Link the Agent identity to your StackOne SSO app (in Okta, **User access and authentication**), and allow the scopes the profile requests (in Okta, on the app's resource connection). |
| One app is missing for a user | The Agent identity isn't allowed that app, its Connector Profile in that project doesn't have **Link accounts at SSO sign-in** turned on, the user is a Project Viewer there, or the profile is Restricted and the user isn't granted access. | Allow the app for the Agent identity, turn on linking in the profile, give the user the Project Member or Project Admin role in that project, or grant them access on the profile. |
| "Your identity provider has not given StackOne's Agent identity access to this app", or "Your identity provider has not given StackOne's Agent identity the scopes this app needs" | The Agent identity isn't allowed the app or the scopes its Connector Profile requests, or the app's resource identifier doesn't match what StackOne support sent. | Allow the app and the profile's scopes for the Agent identity, or fix the app's resource identifier. |
| "Your SSO sign-in has expired" | The user's grant expired (with Okta, 90 days after their last SSO sign-in), or your IdP revoked their access. | The user signs out of StackOne and signs in again through SSO. |
| "The app refused the access your identity provider granted" | Your app doesn't accept the grant: XAA isn't allowed for it, its scopes don't cover the app's, or the client ID your IdP grants access for isn't your app's. | Check your app's settings in that app, and that the client ID your IdP grants access for (in Okta, the resource connection's **Client ID**) matches the Connector Profile's. |
| "The app refused the client ID or secret in the connector profile" | The Connector Profile's client ID or secret doesn't match your app. | Update them on the Connector Profile. |
| "Your identity provider refused to give StackOne access to this app" | Your IdP refused for a reason not listed here. Its reason is in the parentheses. | Check the reason against the Agent identity's setup in your IdP, or contact StackOne support. |

## Next steps

> [card] [AI Platforms](https://docs.stackone.com/ai-platforms/overview.md)
>
> Connect an AI platform so users can work with their Linked Accounts.

> [card] [Project Roles](https://docs.stackone.com/secure/identity-and-access/roles-and-groups/project-roles.md)
>
> Give users the role that lets them hold Linked Accounts.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.