Manage Team and Accounts

Use these settings to keep team permissions clear and account access healthy.

Fast Path

Review who has access, change only the permissions that need to change, confirm another admin exists before removing admin coverage, and reconnect accounts before token health becomes a blocker.

How To Use This

Good admin work is mostly preventive. You are trying to avoid two common failures:

1. the wrong person has more access than they need
2. the right person loses access only when urgent work appears

That means role reviews and connection-health checks are not chores. They are operational safeguards.

What To Watch For

Do not remove or demote the last admin without replacing that coverage first. Admin guardrails exist for a reason.

For account access, broad team access is convenient but expensive when you are trying to keep sensitive accounts limited to a smaller operator group. Use account-specific access deliberately.

FAQ

Can I invite someone as an admin immediately?

The safer pattern is to start with the minimum role needed and promote later only if the ongoing responsibility requires it.

If an account needs reconnecting, do we lose history?

No. Re-authentication restores access. It does not wipe the existing team history around that account.

Next Steps

Continue to Configure Optimization and Dayparting when the next question is account settings, or use Fix Common Issues if token or access problems are already blocking work.