Give clients read-only ad access without giving them editing rights

Choose the access layer the client actually needs

Google Ads access and Adport access are separate permission systems. Grant access in Google when the client needs Google's own reports and account interface. Grant an Adport project viewer role when they need the connected cross-platform workspace.

Google documents read-only access for manager and linked client accounts. A read-only user can browse and run reports within the access they hold, while administrative actions require other permissions. Do not upgrade someone to an administrator just because a report is not visible; first check the account hierarchy and intended scope.

Adport does not automatically change the client's Google login permissions. Conversely, removing an Adport project grant is not a substitute for reviewing separate direct access the person has in an advertising platform.

Assign an Adport viewer to selected projects

1. Open the agency's Organization settings.
2. Choose Invite member and enter the client's email.
3. Select Viewer (read-only).
4. Select only the projects the client should see.
5. Save the access and have the client sign in with their own account.
6. Verify the visible project and account list together.

Organization owners and admins inherit access to all projects. Use a viewer for a client who should see one brand, and explicit project selections for someone reviewing several related brands. Do not use an organization-level admin role as a shortcut.

Read-only client viewers do not consume editing seats. Assigning the person an editing role changes both their permissions and the organization's editing-seat usage.

Verify the boundary with the client

Check the project selector first. The client should see the intended projects, not the agency's full client list. Then confirm the visible ad account IDs and a known report. An empty report can mean missing account selection or disabled account access rather than a need for a broader role.

Verification should use the client's own sign-in. Looking at the owner's dashboard does not establish what the viewer can access.

Keep AI access read-only too

If the client connects an AI assistant, authorize the same intended project. The viewer role continues to restrict advertising changes. A tool being discoverable in a client does not override the server's permission checks.

MCP authorization describes scoped access to protected servers. In Adport, the project and current member permissions are part of that access boundary. Do not share an agency operator's manual API key with a client as a substitute for their own viewer identity.

Give the client a useful reporting brief

Agree on the primary business outcome, reporting period, and meaning of conversion value. A viewer can see a number without knowing whether it represents a lead, a purchase, or an estimated value. Document those definitions once and reuse them in reports.

Share the current decision and next review date alongside the figures. If recent conversions are still arriving, identify that limitation. Keep internal hypotheses distinct from approved actions so a preliminary discussion does not look like a completed account change.

Review access at handoff and offboarding

When the engagement or the person's responsibilities change, remove unneeded project grants and review any separate platform access. Check manual keys and the person's AI connections as part of the handoff. Do not assume a shared credential disappears when an individual's membership changes.

Keep retained records and access decisions consistent with the client's agreement. For agency-wide organization and project structure, read the multi-client operations guide. For report definitions, use the CPA and ROAS guide.