Understanding QA Admin Roles

Overview
QA Admin roles provide controlled, read-only access for reviewing accounts and troubleshooting on behalf of users. This article explains the Account QA Admin and Team QA Admin roles, what each can do, how to assign them, and how their read-only and “login-as-member” capabilities work.


Who This Applies To

  • Account Owners and Admins who manage users and permissions

What Are QA Admin Roles?

QA Admin roles are specialized administrative roles designed for visibility and troubleshooting without the risk of modifying customer data. They allow users to:

  • View account or team configurations and content in a read-only state
  • Log in as a member to reproduce issues and validate behavior

There are two QA Admin roles:

  • Account QA Admin: scoped to the entire account
  • Team QA Admin: scoped to a specific team

How to Assign an Account QA Admin Role

  1. Go to Manage Account in the left navigation
  2. Click the Users tab
  3. Find the user you want to update
  4. Open the Account Role dropdown
  5. Choose QA Admin 

     

How to Assign a Team QA Admin Role

  1. Select a Team from the Team Selector in the left navigation
  2. Click Manage Team
  3. Select the Team Members tab
  4. Find the user you want to update
  5. Open the Team Role dropdown
  6. Choose QA Admin 


Role Comparison

CapabilityAccount QA AdminTeam QA Admin
ScopeEntire accountAssigned team only
View settings & contentYes (read-only)Yes (read-only, team-scoped)
Login as memberYes (any member in account)Yes (members within assigned team)
Edit settings/contentNoNo
Manage users/teamsNoNo
Send emails / change campaignsNoNo

Account QA Admin

What it can do

  • View all account-level settings, users, and content in read-only mode
  • Access reporting and configuration without the ability to change anything
  • Log in as any member in the account to troubleshoot issues

Best for

  • Global QA reviews
  • Support investigations that require account-wide visibility

Team QA Admin

What it can do

  • View team-level settings, members, and content in read-only mode
  • Access team reporting and configuration without editing permissions
  • Log in as members within the assigned team

Best for

  • Team-specific QA or support
  • Limiting visibility to a subset of the account

Read-Only Access Explained

QA Admin roles cannot create, edit, or delete any data. All pages, settings, and content are viewable but locked from changes. This ensures:

  • Safe auditing and troubleshooting
  • No accidental configuration changes
  • Clear separation between review and action

“Login as Member” Capability

QA Admins can log in as a user to replicate issues and verify experiences.

How it works

  • Select a user from the user list
  • Choose Login as Member
  • You will enter a session that mirrors that user’s environment

Important notes

  • Actions taken during impersonation should remain non-destructive; QA Admins still do not have edit permissions
  • The session is intended for observation and troubleshooting, not changes

FAQs

Can QA Admins make any changes while logged in as a member?
No. The role remains read-only even during impersonation.

What’s the difference between the two QA Admin roles?
Scope. New Account QA Admin covers the entire account; Team QA Admin is limited to a specific team.

Who should be assigned a QA Admin role?
Internal support, QA, or reviewers who need visibility without modification access.