/projects//settings/team/ ).
1. The Need for Granular Permissions in Scaling Agencies
As an agency grows to 20+ team members and dozens of contractors, open access becomes a massive liability. Freelance copywriters should not see PPC ad spend, and junior specialists should not have permission to delete client Google Ads integrations.
LIVE PLATFORM SCREEN & TELEMETRY
SEO Runway Team Permissions & RBAC Settings — Active Workspace
Below is the exact production screen with live parameters and dummy data illustrating the diagnostic findings and remediation buttons.
2. Managing Roles in SEO Runway
In SEO Runway → Team & Permissions, invite members and select their role: Admin, Editor, Contributor, or Client Viewer. Permissions apply instantly across all project modules.
Target System: SEO Runway AGENCY Engine
Execution Frequency: Automated Background Queue (UTC Sync)
Tested across enterprise datasets with zero rate limiting or data loss.
3. Why Agencies Need Role-Based Access Control
A five-person agency can share logins and trust everyone with everything. A 30-person agency with contractors, multiple client teams and white-label client access cannot. Without structured permissions, junior staff can accidentally publish content, former contractors keep access to client data, and clients may see information meant only for the agency. Role-based access control (RBAC) solves this by granting permissions to roles rather than individuals, then assigning each person the role that matches their job.
RBAC protects client data, reduces mistakes, simplifies onboarding and offboarding, and makes it easier to answer security questions from enterprise clients.
4. Principles of Good Access Design
- Least privilege: give each person only the access they need to do their job, and no more.
- Roles, not people: define permissions once per role, then assign people to roles, so changes apply consistently.
- Separation of duties: sensitive actions, such as publishing to a client's live site or changing billing, may require a second person's approval.
- Client data isolation: team members see only the clients they work on, unless their role requires wider access.
- Regular review: access should be reviewed and adjusted as people change roles or leave.
5. Defining Agency Roles
Start with the roles that exist in your agency. A typical multi-tier structure might include:
- Owner or administrator: full access to all clients, settings, billing and user management. Limit this to a small number of people.
- Director or head of department: access to all clients in their department, reporting and team management, but not billing or global settings.
- Account manager: full access to their assigned clients, including reports, tasks and client communication, but no access to other accounts.
- Specialist: access to the tools and tasks they work on for assigned clients, such as SEO audits, content or ad management, without client settings or billing.
- Junior or trainee: can draft and prepare work for assigned clients, but cannot publish or change live settings without approval.
- Contractor or freelancer: limited, time-bound access to specific clients and tasks only.
- Client user: access to their own reports, dashboards, approvals and tasks assigned to them, with no visibility of other clients or internal discussions.
6. Mapping Permissions to Roles
For each role, decide what they can view, create, edit, approve, publish and delete. A simple permissions matrix makes this clear.
- View: data, reports and tasks they can see.
- Create and edit: tasks, content drafts, audits and report templates.
- Approve: content, technical changes and reports before they go to clients.
- Publish: push content to websites or social accounts.
- Manage: users, client settings, integrations and billing.
- Delete: remove data, which should be restricted to senior roles.
Document the matrix and share it with the team, so everyone understands what they can and cannot do and why.
7. Client-Level Access and Data Isolation
Agencies hold data for many clients, some of whom compete with each other. Strict separation is essential.
- Assign team members to clients explicitly, rather than giving everyone access to every account.
- Restrict client users to their own workspace, with no way to see other clients' names, data or reports.
- Handle competing clients carefully: some agencies assign separate teams to competitors, and clients may ask about this during contracting.
- Separate internal notes from client-visible content, so internal discussions about strategy, pricing or performance concerns stay internal.
8. Access to Third-Party Platforms
RBAC applies beyond your own tools. Clients' analytics, ad accounts, social profiles and websites also need structured access.
- Use platform-native user management: grant access through Google Analytics user management, Search Console users, Meta Business tools, LinkedIn page roles and similar systems, rather than sharing client passwords.
- Use agency accounts where available: manager accounts for advertising platforms let agencies access client accounts centrally and remove access cleanly.
- Grant the lowest suitable level: read-only access for reporting, editor access only for those who need to make changes.
- Record who has access to what for each client, so offboarding is complete.
9. Onboarding and Offboarding Team Members
RBAC makes joining and leaving much simpler and safer.
Onboarding
- Assign the person's role in your core platforms.
- Add them to the clients they will work on.
- Grant access to third-party platforms through agency accounts.
- Require two-factor authentication on all accounts.
- Walk them through the permissions matrix and approval processes.
Offboarding
- Remove access on their last day, or immediately for unplanned departures.
- Remove them from every client workspace and third-party platform.
- Reassign their open tasks and client relationships.
- Rotate any shared credentials they may have known.
- Record the offboarding in an access log.
Contractors should have end dates set on their access when possible, so it expires automatically if nobody remembers to remove it.
10. Approval Workflows as Access Control
Permissions decide who can act; approval workflows add a second check for actions with higher risk.
- Content approval: juniors draft, seniors approve before content goes to the client.
- Client approval: clients approve deliverables before publishing.
- Technical changes: changes to live websites, such as redirects or robots.txt edits, approved by a senior specialist.
- Report review: account managers review automated reports before they are sent.
11. Audit Logs and Access Reviews
- Audit logs: use tools that record who viewed, changed, approved or deleted items, and when. Logs help investigate mistakes and demonstrate security to clients.
- Quarterly access reviews: list every user and their role, confirm each still needs that access, and remove or adjust as needed.
- Client access reviews: confirm that each client's team list is accurate and that client users are still with the client's company.
- Third-party reviews: check user lists in client analytics, ad and social accounts for former staff and contractors.
12. Answering Client Security Questions
Enterprise clients increasingly send security questionnaires before signing. A clear RBAC setup makes them easier to answer.
- Who can access our data? Named roles, assigned team members and the permissions matrix.
- How is access granted and removed? The onboarding and offboarding procedures.
- Is two-factor authentication required? State your policy.
- Are actions logged? Describe audit logs and retention.
- How do you separate client data? Explain client-level isolation.
Prepare a short security summary document that you can share with prospects, saving time on every questionnaire.
13. Common Mistakes
- Shared logins, which make it impossible to know who did what or to remove one person's access.
- Everyone as administrator, because it was easier at the start.
- Former staff and contractors with access months after leaving.
- Clients seeing internal notes or other clients' information.
- No two-factor authentication.
- Roles defined but never reviewed, drifting out of date as the agency grows.
- Too many custom roles, making the system hard to manage.
14. A Worked Example
A growing agency of 35 people had given most staff administrator access to its reporting platform, and several former contractors still had access to client analytics. After a contractor accidentally deleted a client dashboard, the agency introduced RBAC. It defined seven roles, assigned team members to specific clients, moved client users into isolated workspaces and set approval steps for publishing. A full access review removed dozens of outdated accounts across third-party platforms. The agency then created a security summary for prospects, which helped it pass an enterprise client's security review and win the account.
15. Scaling RBAC as the Agency Grows
RBAC should evolve with the agency.
- Start simple: four or five roles are enough for many small agencies.
- Add roles when responsibilities change, such as introducing team leads or specialist departments.
- Use groups or teams: assign whole teams to clients, so adding a new team member automatically gives them the right client access.
- Automate where possible: connect your HR or identity system so roles update when people change jobs.
- Single sign-on: larger agencies benefit from single sign-on across tools, making access management and offboarding faster and more reliable.
Review the role structure once a year, or whenever the agency restructures, to keep it aligned with how the team actually works.
16. Balancing Security and Speed
Too much restriction slows work and frustrates teams. If specialists constantly wait for permissions or approvals for routine tasks, they find workarounds, such as sharing logins, which defeats the purpose. Design roles around real workflows: routine, low-risk actions should be fast for the people who do them daily, while approvals are reserved for actions with real risk, such as publishing live content or changing client settings. Ask the team every few months which permissions get in the way, and adjust where it makes sense without weakening protection for sensitive data and actions.
17. Handling Emergency Access
Sometimes someone needs access urgently, such as during a client crisis when the usual specialist is away. Define a simple emergency process: a senior person can grant temporary elevated access, record why, and remove it once the situation is resolved. This avoids the common shortcut of sharing an administrator login.
18. Training the Team on Access Rules
Permissions work best when people understand them. Include a short session on access rules in every new starter's induction: why least privilege matters, how to request extra access, why logins must never be shared and how to report a suspected security issue.
19. RBAC Implementation Checklist
- List the roles in your agency, including contractors and client users.
- Build a permissions matrix for view, create, approve, publish, manage and delete.
- Assign team members to specific clients and isolate client workspaces.
- Use platform-native and agency accounts for third-party access.
- Require two-factor authentication everywhere.
- Define onboarding and offboarding procedures with access logs.
- Add approval workflows for higher-risk actions.
- Review access quarterly and the role structure yearly.
20. Your Next Step
Export the user list from your main agency platform and from your three largest clients' analytics and ad accounts. Highlight anyone who has left, anyone with more access than their job requires, and any shared logins. Fix those first, then draft a simple permissions matrix for your agency's roles.
Want the complete procedural runbook?
Visit our comprehensive step-by-step Knowledge Base for interactive screen maps, configuration parameters, and adjacent module workflows.
Open Knowledge Base Hub →

Incredible breakdown. We implemented this exact workflow last week and already saw a noticeable shift in our telemetry. As a Director of Demand Gen, this provides exactly the architectural depth we look for.