What is delegated access?
- Term
- Delegated access
- Meaning
- Delegated access lets an account owner allow other people to work in the account without giving out the password. Each person signs in as themselves.
Delegated access is a way for an account owner to let other people work in an account without giving them the username and password. Each person signs in as themselves and can do only what the owner allowed. At an agency, the client is the owner, and your staff are the people allowed in.
How is delegated access different from a shared login?
Delegated access separates getting into an account from owning it. With a shared login, knowing the password gives a person the same rights as the owner. Whatever they do shows up on the platform (a service such as Google Ads or Meta) as the owner’s activity. With delegated access, the owner decides on the platform who may do what. Each person uses their own login, so the platform’s history names the person, as far as the platform keeps history.
How does delegated access work?
Platforms use different names, but delegated access has three parts.
- Permission levels set how much a person may do, such as view only, edit, or manage. Some platforms call them roles. At an agency, ask only for the level each person’s work needs.
- An invitation is how access starts. The owner names another person’s login, and that person accepts. At an agency, each staff member gets their own invitation, and no one shares a login.
- Removal is how access ends. The owner, or someone with admin rights, takes the permission away. At an agency, you ask for removal on each account when staff change.
Some platforms limit the levels on offer or who can remove people, so check before you take on an account.
What can’t delegated access do?
Delegated access works only where the platform offers it. If an admin screen has one username and password and nothing else, it isn’t an option. Even where it exists, some settings and screens may open only to the owner’s login. For those tasks, the owner’s login still gets used.
Delegated access also starts with the owner’s invitation, so the client has to act first. Until it does, you keep using the username and password you were given. Managing client accounts at an agency covers what to do when delegated access isn’t available.
How does delegated access work in Google Ads?
Google Ads Help describes a manager account (MCC) as a Google Ads account “that lets you view and manage multiple Google Ads accounts.” It works at two layers. Between businesses, the client links its Google Ads account to your agency’s manager account. Users with admin access on the client account can unlink it at any time, which is the client’s way to remove access. Inside your agency, staff are invited as users of the manager account and given an access level.
The permission levels are the access levels of the client’s Google Ads account: Email only, Billing, Read only, Standard and Admin. An Admin can grant access, change access levels, and cancel invitations that haven’t been accepted. Removing someone who already has access is a separate step. Google’s help page on managing access describes it: open Access and security and select Remove access next to that user. Manager account users have their own access levels, covered in organizing agency access with a Google Ads manager account. So Google Ads has all three parts: permission levels, invitations and removal.
Frequently asked questions
How is delegated access different from sharing a login?
With delegated access, each person signs in as themselves and never learns the owner's password. A shared login uses the owner's username and password, so the platform's records name the login, not the person.
Does delegated access get rid of shared logins?
Not entirely. Shared logins remain where a platform has no sharing feature, where some settings need the owner's login, or where the client never sends the invitation.
What happens with delegated access when a staff member leaves?
The owner, or your agency's manager account, removes that person's access on each platform. No password change is needed. To avoid missing an account, keep a list of every client account your staff work in.
How Junify handles this
- Doing this by hand
- You agree with each client on how access is handed over, add and remove people platform by platform whenever staff change, and keep track of which staff member used which client's account.
- With Junify
- Junify is mainly for platforms without delegated access, and for accounts where the client can't change its settings. Your admin adds the username and password to Junify. Staff sign in without seeing the password, each use is recorded under the person's name, and when someone rotates off, you remove their access in Junify.
Sources
- Google Ads Help: About Google Ads manager accounts
- Google Ads Help: About access levels in your Google Ads account
- Google Ads Help: Manage access to your Google Ads account
-
Account clauses an agency should propose in its client contract
Propose five: account handover, who may use accounts, records, incident notice, and offboarding. Keep your own promises apart from what the client must do.
-
How to write client account handling into your agency's security policy
Write a short public policy, an internal policy for staff, and an access summary for each client. Rewrite template rules for logins the client owns.
-
Amazon Seller Central user permissions, and how to give an agency access
Seller Central Help says not to share logins. On a Professional plan, the seller invites staff as employees and authorizes your agency as a Service Provider.