Outcome and audience

For Owners and Admins removing a person, team, or provider connection.

Before you begin

Identify the exact workspace membership or connection, confirm the replacement owner, and preserve required financial records according to policy.

Where to go

Use People & access for users and Data sources for provider connections.

Complete the workflow

Keep the selected workspace, provider, period, currency, cost basis, and data-through date visible as you work.

  1. Reassign owned Saved Views, budgets, anomaly investigations, and alert destinations when required.
  2. Remove the customer membership or revoke the invitation.
  3. Revoke the PruneFox data-source connection.
  4. Revoke or delete the provider-side credential.
  5. Confirm active sessions or new cost syncs no longer continue for the removed authority.

Interpret the result

Revocation prevents future access. Historical cost remains subject to workspace retention and does not restore a deleted provider credential.

Loading, empty, partial, and unavailable states

Loading preserves the current scope. Empty means no records match the authorized scope. Partial or stale data keeps its completed-through boundary visible. Unavailable or permission-denied states explain the missing prerequisite and never substitute zero or another provider.

Provider differences

Provider-side credential and report cleanup differs; follow the provider guide's Rotate or revoke access section.

Synthetic example

Illustrative example · synthetic data Example: Northstar Labs transfers an AWS Saved View, revokes one user's membership, revokes the AWS connection, and removes the dedicated role at AWS.

Common mistakes

Do not remove only the visible card, leave an active provider credential, or delete history before confirming financial retention requirements.