
Agency Onboarding
Part of Agency onboarding
Giving an agency access without surrendering account ownership
Grant an agency the access needed to do agreed work while keeping a client administrator and a clear exit route. Shared passwords make it hard to see who changed …
Access is not ownership: the distinction that protects your account
The agency must work inside your accounts — Google Ads, analytics, design files. It does not need to own them. Scoped, revocable access keeps control, data and business continuity with you.
In Google Ads the distinction is explicit: a client account can have only one owner. An owner gets full administrative and data access privileges, which may include personally identifiable information attached to the client account.
Ownership is not a transfer of the account. The client account still owns its data and can remove ownership access by unlinking. Users with administrative access can end the relationship with the manager account at any time.
The working principle: give the agency what the work requires, keep ownership, and make sure you can revoke. Anything more is a deliberate decision, not a default.
Three ways an agency can get in — and what each one quietly gives away
Access comes in three levels, each giving away something different. At the lowest, the agency gets a user account with a role — view, edit or admin. In the middle, your account links to the agency's manager account. At the top, the agency becomes owner.
Figma mirrors this ladder. You can share a single file, a project folder, or add the agency to your team — each step widens what they can see and change.
Google Ads manager accounts work as an umbrella. A manager account is not an upgrade of your account; it is a separate Google Ads account with individual accounts linked to it. Linking alone does not hand over ownership — a linked existing account keeps ownership unless you enable it for the manager.
Ownership is the only tier that lets someone manage other users, accept link requests, transfer control or unlink your account. Only owners can invite or remove administrative users, grant or revoke admin access, and adjust security settings on the client account.
Prepare the account before anyone is invited
Confirm you hold administrative access to the account yourself before inviting anyone else. In Google Ads you cannot turn on ownership without administrative access, and you cannot change which manager holds ownership.
Give the agency its own user account rather than sharing a login. A shared credential means you cannot see who did what, set permissions per person, or revoke access without changing the password for everyone.
Tidy the structure first, because permissions attach to it. In Figma that means deciding whether work lives in a file, a project folder or a team; in Google Ads it means knowing which accounts sit under the manager umbrella.
Settle scope and duration in writing before the first invite. A services or subcontractor agreement should define the services, deliverables, milestones and approval process, and state who owns strategy documents, workshop outputs, copy, research and templates.
Pre-Invite Account Preparation Checklist
- Confirm you hold administrative access to the account
- Use individual user accounts for agency staff, not shared logins
- Organise account structure (e.g., folders in Figma, campaigns in Google Ads)
- Define scope, duration, deliverables, and IP ownership in writing
Match permissions to the job, not the relationship
Choose the role that matches the task, and change it when the task changes. An agency producing a monthly report needs view access; one building campaigns needs edit; only the person who administers the account needs admin.
Invite named individuals rather than one shared agency login. That keeps the audit trail attached to a person and lets you remove one contractor without disrupting the rest of the team.
Google Ads lets you grant users different levels of access to your manager account. The account lead and the person doing data entry do not need the same rights.
Review work through comments and version history instead of blanket edit rights. Figma records version history automatically and includes a commenting system, so feedback does not require edit access on every file for everyone.
Time-box access to the engagement. Giving full edit access to everyone and forgetting to remove old users are recurring mistakes; both are avoided by agreeing an end date at the outset.
When handing over ownership is genuinely justified — and what it costs you
Ownership exists for one specific job: controlling who else can get in. On an owner manager account in Google Ads, admin users can invite users with administrative access, remove users, grant or revoke administrative access, and accept or decline link requests from other managers.
That role can turn ownership off, transfer it to another manager, unlink other managers, and turn on remarketing list sharing. It can also adjust security settings on the client account.
The limits matter as much as the powers. A client account can have only one owner at a time, and ownership is transitive: if your manager account owns a client account, every manager above it also has ownership.
Ownership still does not let the manager change proprietary information such as the account's sign-in details. The client account retains its data and the right to unlink, which removes ownership access.
Google's guidance is to make a manager an owner if and only if it needs those privileges. If you only need campaigns built, reporting and monitoring, a linked manager account without ownership delivers that.
Ask a blunt question before signing anything: does the agency need to control user access, or only to work in the account? Only the first justifies ownership.
Keeping personal information in bounds while the agency works
Access to an account is often access to personal information — customer records in a CRM, audiences in an ad account, user data in analytics. Give the agency only what the work reasonably requires.
Under Australian Privacy Principle 3, an organisation may collect personal information only where it is reasonably necessary for its functions or activities. It must collect by lawful and fair means and from the individual concerned unless that is unreasonable or impracticable.
The OAIC treats proportionality as implicit in those requirements. That means data-minimisation: collect only the amount necessary for a specific purpose.
Collection is only half of it. APP 6 restricts use and disclosure to the purpose the information was collected for, unless an exception applies — for example, the individual consented, or would reasonably expect the use and it is related to the primary purpose.
Scope each system separately. An agency running campaigns may need aggregate performance data; a CRM export of named customers, or an ad audience built from a customer list, is a different proposition and needs a purpose that covers it.
Key Privacy and Compliance Facts (Australian Context)
- APP 3: Collection LimitationOnly collect personal information that is reasonably necessary for your functions
- APP 6: Use and DisclosurePersonal info must not be used beyond original purpose unless consented or reasonably expected
- Data Minimisation PrincipleShare only the minimum amount of personal data needed for the task
What the agreement needs to say about access, data and IP
The agreement is where access becomes enforceable. A services or subcontractor agreement for agency work should cover scope of services and deliverables, intellectual property ownership, confidentiality, privacy and client data, plus payment terms, expenses and variations.
It should also cover restraints that protect client relationships, liability, warranties and insurance, and termination and handover. Revocation of access belongs in that handover.
Deal with IP explicitly. Two recurring failures are leaving IP ownership vague and not dealing with pre-existing tools and templates, which leaves the agency's own frameworks and your deliverables in one undifferentiated pile.
Pass your own client obligations down. Where the agency subcontracts, the subcontract should carry the confidentiality and privacy duties you owe and the client-contact guardrails you have agreed.
Guardrails on direct client engagement are not optional; allowing direct engagement without them is a common mistake. Weak exit provisions are another, so state what is returned, what is deleted and when access is revoked.
Reviewing, downgrading and revoking access
Treat access as a standing list to maintain, not a setup task. Audit users periodically against active projects and remove anyone whose work has finished.
Downgrade rather than delete when a project pauses. In Figma you can remove someone from a file or downgrade their access; forgetting to remove old users is one of the most common mistakes.
At the end of an engagement, deal with ownership as well as users. In Google Ads a manager can be removed as owner, ownership transferred to another manager, or all owners removed; an account with administrative access can also unlink, which terminates the relationship.
If a login was ever shared, rotate the password when access ends. Sharing credentials means you cannot revoke access without resetting the password for everyone who had it.
Confirm the handover. Files and documentation returned, exports deleted, and remaining permissions reduced to only what you want to keep running.
How to Safely Grant and Revoke Agency Access
- Assign the minimum required role (view/edit/admin) based on task
- Invite named individuals, not shared credentials
- Set time limits for access with an end date
- Audit access regularly and downgrade or remove inactive users
- At engagement end, revoke all access and rotate passwords if shared
- Confirm handoverfiles returned, exports deleted, permissions reduced



