Knowledge base
Managing multiple ad accounts
SpendSignoff supports multiple linked accounts from the start. The plan you are on determines how many accounts the operator watches; the safety model is the same across all of them.
How accounts are organized
Each linked ad account is a connected account — an OAuth link from SpendSignoff to a Google Ads or Meta account you own. Accounts are added one by one through the Accounts screen; each one authorizes read access first, and write draft access only after you confirm.
The operator watches every connected account within your plan ceiling simultaneously. If the autonomy loop is running, it stages drafts across all watched accounts and routes each one to the approval queue scoped to that account.
Account limits by plan
Account count is the one number that changes across plans. The safety model does not.
- Free — one connected account, read-only. The approve control is locked. Useful for evaluating what the operator would do.
- Solo — multiple accounts; exact ceiling in the current pricing page. Approval is live. One autonomy loop can run per account.
- Pro — higher account and concurrent loop ceilings for an in-house team managing several brands.
- Agency — multi-tenant workspaces, each with its own account pool, member roles, and audit log.
Adding a second account
Open Accounts
Navigate to the Accounts screen from the sidebar. Connected accounts are listed with their platform, token health, and current plan slot.
Connect a new account
Click Add account, choose the platform (Google Ads or Meta), and authorize the OAuth flow. The link starts read-only.
Confirm the connection
After OAuth returns, SpendSignoff runs a read check and shows the account as connected. The operator starts syncing it within the next ingest cycle.
Enable drafts
Draft write access is gated on your plan and requires a second explicit confirmation in the Accounts screen. Read-only is always available; write-draft is opt-in per account.
The audit log across multiple accounts
Every approved action is scoped to the account it touches. The main audit log view shows all accounts. You can filter by account to see the full history of a single connection — what changed, who approved it, when, and what the before value was.
Rollback works per action per account. Reverting a change on one account has no effect on any other.
One approval queue, scoped correctly
Next
Using SpendSignoff from multiple AI clients
One operator, multiple AI clients — how sessions, scopes, and the audit log work.