Managing cloud accounts
Once a provider has at least one connected account, its card on Clouds lists each account as its own row under the provider name. A gear icon sits next to the "Connected" badge for account and project management.
Can I connect more than one account?
Yes. You can connect any number of accounts per provider (see Connecting a cloud account), for example one AWS account per environment. Each account row shows the account name the platform resolved on connect, plus status tags:
default: the first or primary account for the provider (shown only where project-usage marking does not apply, see below).- A status other than active (
pending,expired,revoked,error): shown as a yellow tag with the raw status. new permissions: the credential is active but the provider now requires scopes it was not granted; hovering shows which ones.
When a credential breaks
If the platform's last attempt to use an account failed (an expired key, a revoked service principal, a permissions change), the row shows a red error strip beneath it with the error code, which part of the platform hit it (for example discovery, health checks), and when it happened. A reconnect link appears next to the row whenever it is inactive or needs new permissions; for cloud accounts this reopens the same credential form you used to connect, pre-scoped to that provider, so you can paste a fresh credential without losing the account's history.
How do I disconnect?
The trash-can icon on an account row disconnects it immediately; there is no confirmation step. Disconnecting removes the credential from the vault, and anything that depended on it (an in-progress infra census, a scheduled health check) will start failing until you reconnect or connect a replacement.
Assigning an account to a project
Click the gear icon on a provider's card to open Manage <Provider> accounts, subtitled Each project can use one <Provider> account. This is the same modal used for every integration type, with two view modes:
- By project: one row per workspace project, each with a dropdown of every connected account for that provider (or "Not connected"). Picking an account assigns it to that project immediately, and the footer confirms "Changes are saved automatically."
- By account: pick one account from a dropdown, then check off the projects it should serve. A project already served by a different account shows an
on <other account>tag next to its checkbox.
Because a project can use only one account per provider, assigning an account that is already serving a project from a different account prompts a confirmation ("Replace account on this project?") before swapping it. In "By project" mode the dropdown just does the swap directly (replace: true), while "By account" mode asks first, since the checkbox click is one step removed from picking a specific account.
Both a search box (to filter projects by name) and a live busy/loading indicator are present in the modal; there is no separate save step, and every change is written on click.
What do you need?
All of the above (reconnect, disconnect, assign) requires org:integrations:manage; see Clouds permissions. Viewing account status and error details only requires org:integrations:read.