# Choose your workspace and team access.

Source: https://adsuperpowers.ai/docs/workspaces

Use your own identity, connect to the intended workspace and keep account access separate from write permission.

## Choose your workspace

A workspace brings together platform connections, client profiles, team members and usage. Select the intended workspace in your [dashboard](https://app.adsuperpowers.ai/dashboard) before connecting accounts or managing the team.

When you authorize an AI connector, choose the same workspace on the Ad Superpowers **Select workspace** screen. With multiple workspaces, make an explicit choice. New OAuth connections and API keys are bound to one workspace. Changing the dashboard selector does not move an existing connector or key.

If your assistant is connected to a personal workspace with no accounts, authorize the connector again and choose the team workspace. For API-key setup, use your own key created for that workspace. Follow your [client's installation guide](https://adsuperpowers.ai/docs/setup) for the connection steps.

## Share accounts with your team

1. The owner or the person responsible for connections selects the team workspace and [connects the platform accounts](https://adsuperpowers.ai/docs/accounts#connect-a-platform).
2. An owner or admin opens **Settings → Team → Members → Invite Member**, enters the colleague's email address and chooses a role. The invitation has a seven-day validity period. **Copy invite link** is available for a still-valid invitation if the email is missing.
3. The colleague accepts the invitation using their own Ad Superpowers account with that email address. Accept the invitation before connecting the AI client.
4. For selective access, use the **Member** role. After acceptance, open **Account Access → By Member** or **By Account** and tick the intended assignments. Changes save directly. New accounts are not automatically assigned to members.
5. The colleague connects their AI client with their own Ad Superpowers login, or their own workspace key, and chooses the team workspace.
6. Run the [workspace and account check](https://adsuperpowers.ai/docs/workspaces#verify-your-context) before starting work.

A new registration through a valid invitation adopts the team workspace as its default. An existing user can retain a personal default. The workspace choice during connector authorization remains important in both cases.

Use an individual login and key for every colleague. A shared owner key runs as the owner, with the owner's account access and attribution. It does not preserve each colleague's identity.

## Understand roles

| Role | Platform account access in this workspace | Team administration |
| --- | --- | --- |
| Owner | Active, selected workspace connections; assignments do not narrow this role | Owner controls, including workspace write permissions |
| Admin | Active, selected workspace connections; assignments do not narrow this role | Team and account-assignment management |
| Member | Assigned accounts plus their own selected platform connections | No owner/admin team-management authority |

Platform permissions, connection health and subscription limits still apply. An Ad Superpowers role cannot give a platform login access it does not have.

Do not make someone an admin merely to give them an account. Admin also grants team-management authority. Use member assignments when that narrower role fits.

### Assignment changes can take time

The MCP account-list cache can retain an earlier list for up to 30 minutes. A newly assigned account can therefore remain unavailable, and a removed assignment can remain usable until the cached list refreshes. Starting a new chat or reconnecting the AI client is not a guaranteed cache reset.

Set initial assignments before the colleague's first account request. After later changes, repeat the access check after the cache window. For urgent removal, do not rely on account assignment changes alone; contact [support](mailto:support@adsuperpowers.ai) to establish the appropriate access action.

## Set write permission separately

Account access answers **which accounts can this person reach?** Write permission answers **can this person make changes?** A member can have account access while remaining read-only.

The owner manages **Settings → Team → Permissions**. Set a colleague to **Read-only**, **Read + Write** or **Inherit**, or turn writing off for the whole workspace. When writing is disabled for the workspace, a personal write setting does not override it. With workspace writing enabled, a personal Read-only setting still blocks that colleague's writes.

An instruction such as “do not change anything” is useful task context. The workspace and member permission controls enforce read-only access. Check `can_write` before assuming the workspace is read-only.

## Verify your context

```text
Use workspace_info. Show the workspace name, my role, whether I can write,
and whether this connection is bound to that workspace.
Then list the [platform] accounts I can access. Do not make changes.
```

`workspace_info` returns `workspace_name`, `role` and `can_write` within `attributed_workspace`, and connection binding within `credential_context`. `attribution: credential_bound` means the credential is bound to that workspace.

Use a known account ID for a small read request. With a member role, also check that an unassigned account that you did not connect yourself is unavailable, allowing for the assignment cache described above.

## Usage, seats and attribution

Tool calls are charged to the workspace used by the request. A workflow that makes several tool calls uses several calls. The Team plan's standard allowance is five seats including the owner; workspace overrides can change the effective limit. Check the dashboard and [pricing](https://adsuperpowers.ai/pricing) for the allowance that applies to your workspace.

Ad Superpowers records the authenticated identity for its own usage and recorded actions. A platform's own change history may identify the person who authorized the shared platform connection, rather than the colleague using it. These are different records; see [change history](https://adsuperpowers.ai/docs/change-history#two-kinds-of-history).

If your check shows the wrong workspace or missing accounts, continue with [troubleshooting](https://adsuperpowers.ai/docs/troubleshooting#missing-accounts).