Agency ad management: organize clients, access, and approvals

Use an organization for the agency and projects for clients

The organization holds the team and shared subscription. Projects hold the client's connected platforms, selected ad accounts, policies, approvals, and audit history. This lets your team reuse one operating process without mixing the clients' credentials or decision records.

These are illustrative names. Choose names your operators recognize from briefs and invoices. Avoid vague names such as “main” for several unrelated clients. A useful project name is a small but effective defense against reviewing the wrong account.

Create a client project and select only its accounts

1. Open Settings, then Projects.
2. Create a project using the client or brand name.
3. Connect the required platforms in that project.
4. Save the accounts that belong to this client.
5. Enable only the accounts agents should use.
6. Check the project policy and invite the appropriate people.

A Google manager account can provide access across several clients, but linking does not automatically grant administrative ownership. Google distinguishes manager access levels and ownership. Your Adport structure should reflect the access the agency actually has, rather than assuming the manager login gives every operator every administrative capability.

Assign roles at the correct level

Organization owners and admins can access every project. Use those roles for people who should operate across the agency. Other members and viewers receive explicit access to selected projects. Do not make a client an organization admin just to let them read one report.

A viewer can inspect the projects they are assigned without changing ads. Owners, admins, and editing members use the plan's editing allowance; read-only client viewers are free. One person editing several projects in the same organization uses one editing seat.

Active account and editing-member allowances are pooled across projects. Separate projects do not create separate pools. Use the plan comparison when estimating capacity, and count the accounts you intend to enable rather than every account your providers can discover.

Bind each agent connection to a client project

When connecting an AI client, authorize the intended Adport project. Keep the client name and account IDs in the working brief. Changing the dashboard project does not retarget an existing agent grant.

MCP provides the common tool interface; Adport supplies the project boundary and advertising policy. A shared endpoint can therefore serve many clients without making every authorization interchangeable. If your MCP client supports multiple entries, name them by client and verify account access at the start of a review.

Define who proposes, approves, and verifies

Keep the commercial approval process clear alongside the technical one. Decide who may propose a change, who can approve a budget or launch decision, and who checks the resulting platform state. A client email approving an overall plan does not make every later model-generated operation part of that approval.

For a supported change, review the exact preview, including the account, old and new values, currency, policy adjustments, and validation result. Apply only the matching pending operation with identical arguments. Keep the business reason with the decision record, then read back the platform state after applying.

Use the same review template for every client, while keeping conversion definitions, targets, and reporting currencies client-specific. A reusable process should not become a universal budget or negative-keyword list.

Maintain access as the agency changes

When a teammate leaves or a client engagement ends, review project grants, organization roles, enabled accounts, provider connections, and manual API keys. Remove access you no longer intend to support. Archiving a project is different from deleting its data; choose the lifecycle action deliberately.

Review shared capacity periodically and keep billing ownership with the agency's actual decision-maker. Document which provider identity owns each connection so a departing employee does not become the single point of failure.

The client access guide covers viewer setup. The agency reporting guide explains how to compare performance without merging incompatible currencies or conversion definitions.