Documentation
Teams let multiple people work from a single Adnine subscription without duplicating effort or accidentally sharing data they should not see. Every teammate is invited by email, given a role, and then filtered automatically to the Google Ads accounts they are personally allowed to access. Use Teams whenever more than one person needs to run reports, manage automation rules, or review logs for the same set of accounts.
- Members
- Unlimited teammates on one shared subscription
- Billing
- No per-seat charge. The whole team shares one plan
- Roles
- Admin, Standard, and View-only
- Access model
- Team membership + account connected to team + your personal Google Ads access
- Best for
- Agencies, in-house teams, and freelancer-client setups
#How access control works
Joining a team does not automatically expose every connected Google Ads account to every person. Adnine checks three conditions before a teammate can see or interact with any account. All three must be true simultaneously.
The three required access checks
A teammate must pass every check below before an account becomes visible to them in Adnine.
| Check | What it means | If it fails |
|---|---|---|
| Team membership | The user is an accepted member of your Adnine team. | They cannot see any team data at all. |
| Account connected to team | An Admin has connected the Google Ads account to the team in Adnine. | Even if the user has Google Ads access, the account does not appear in Adnine. |
| Personal Google Ads access | The user has their own access to that Google Ads account (via Google Ads account permissions). | Even if the team has connected the account, that user cannot see or interact with it. |
Access scenarios at a glance
| Scenario | Can they see the account in Adnine? |
|---|---|
| User has Google Ads access, but team has not connected the account | No. The account is not visible until an Admin connects it. |
| Team has connected the account, but the user lacks personal Google Ads access | No. Adnine respects Google Ads permissions; the user sees nothing for that account. |
| Team has connected the account AND the user has personal Google Ads access | Yes. The account is visible and actionable for that user. |
| User is not a team member | No. They cannot access the team workspace at all. |
#Roles and permissions
Every team member has a role that governs what they can manage inside Adnine. Account visibility is determined separately by the access checks above. A role only controls what actions a user can take on the accounts they can already see.
Team role comparison
Assign roles at invite time. Admins can change roles at any time from team settings.
| Capability | Admin | Standard | View-only |
|---|---|---|---|
| View dashboards, reports, and logs | Yes | Yes | Yes |
| Create and manage own automation rules | Yes | Yes | No |
| Remove other users' automation rules | Yes | No | No |
| Invite or remove team members | Yes | No | No |
| Connect or disconnect Google Ads accounts | Yes | No | No |
| Change user roles | Yes | No | No |
#Setting up your team
Setting up a team takes a few minutes. You will invite teammates by email, connect the relevant Google Ads accounts, and confirm that each person's account visibility looks correct.
- Open team settings Navigate to your team settings page in Adnine. This is where you manage members, roles, and connected Google Ads accounts.
- Invite teammates by email Enter the email address of each person you want to add and select the role they should have: Admin, Standard, or View-only. They will receive an email invitation.
- Teammates accept the invitation Once a teammate accepts, they join the shared workspace. Their account visibility is determined immediately based on the access checks above.
- Connect Google Ads accounts If you have not already done so, connect the Google Ads accounts your team should work with. Only connected accounts will appear for any team member.
- Verify account visibility per member Check that each teammate sees the expected accounts. If an account is missing, confirm the account is connected to the team and that the user has personal Google Ads access to it.
#Identity and action attribution
Every action taken in Adnine is attributed to the individual who performs it, using their personal Google email address. This includes excluding search terms, applying automation rules, updating reporting workflows, and any other change that Adnine applies or logs.
- Only your name appears in Google Ads change history for actions you trigger.
- The activity log inside Adnine shows the user email behind each relevant action.
- No teammate's actions are hidden or merged into a shared identity.
#Account visibility troubleshooting
If a teammate cannot see an account they expect to find in Adnine, there are three things to check in order. Work through them top-to-bottom before escalating.
Visibility issue checklist
| Symptom | Most likely cause | How to fix |
|---|---|---|
| Account not visible for one specific user | That user does not have personal Google Ads access to the account. | Ask the Google Ads account admin to grant the user access directly in Google Ads, then have the user reconnect. |
| Account not visible for any team member | The Google Ads account has not been connected to the Adnine team. | An Admin must connect the account from team settings. |
| Account visible for some members but not others | The visible members have personal Google Ads access; the others do not. | Align Google Ads account permissions so all intended users have access, then confirm visibility in Adnine. |
| Invited user sees no accounts at all | Their invitation may not have been accepted, or no accounts are connected yet. | Confirm they accepted the invite and that at least one Google Ads account is connected to the team. |
#Best practices for team management
Well-managed teams minimise access confusion and keep your workspace organised as it grows. Apply these practices when you set up a new team or onboard new members.
- Keep at least two Admins active so account management is never blocked by one person's absence.
- Assign View-only to stakeholders who need visibility for reporting but should not create or modify automations.
- Connect only the Google Ads accounts a team actually needs. Fewer connections means a cleaner account picker for everyone.
- Review team membership periodically and remove people who no longer need access.
- Use the Prompt Library to standardise recurring reports across the team, reducing duplicated work.
- When a team member's role changes, update their Adnine role at the same time as their Google Ads access.
- Communicate clearly when connecting a new Google Ads account. Teammates only see it once both the team connection and their personal Google Ads access are in place.