Team Members — Add Users, Roles & Environments

Invite teammates to your Personyze account and control what they can access. How to add new or existing users, and what the Member/Manager roles and Test/Production environments allow.

Team Members Overview

The Team members page is where you invite teammates to your Personyze account and control what they can access. Every team member gets a role (what they’re allowed to do) and one or more environments (which campaigns they’re allowed to touch). Managers can add new users, change roles, and update environment permissions at any time.

To open it, go to Settings → Team members in the Personyze left menu.

The Personyze Team members page listing users with their role, environments, and date added — The Team members list: each row shows the user, their role, the environments they can access, and when they were added. Use the search box and the Role / Environment filters to narrow the list, and the ⋮ menu on any row to edit or remove that member.

Adding a Team Member

Click + Add user at the top right of the Team members page. The Add team member panel opens with two tabs — pick the one that matches the person you’re adding.

Register a New User

Use this tab when the person doesn’t have a Personyze login yet. Enter their work email, and Personyze sends them an invite email so they can set their own password. If you’d rather not wait on an email, choose Set a password manually instead and hand them the credentials yourself.

The Add team member panel on the Register new user tab, showing work email, role, and environment options — Register new user: enter their work email, choose a role and environments, then click Send invite. They’ll receive an email to set their own password — or use “Set a password manually” to skip the invite.

Add an Existing User

Use this tab when the person already has a Personyze user account — for example, a colleague who works on another one of your accounts, or an agency partner. Enter the email of their existing Personyze user, pick the role and environments, and click Add user. No invite email or new password is involved; their existing login simply gains access to this account.

The Add team member panel on the Add existing user tab, showing work email, role, and environment options — Add existing user: enter the email of an existing Personyze user to grant their current login access to this account, with the role and environments you select.

Roles

Every team member is either a Member or a Manager:

Member — can use campaigns, actions, and reports. Cannot manage team members.
Manager — full access, including adding, removing, and managing other team members.

Only Managers can reach the Team members page, so keep at least one Manager on every account.

Environments

Environments decide which campaigns a team member can work on. They’re independent of the role — you can have a Manager restricted to Test, or a Member with Production access.

Test — build and QA campaigns on the test bucket. No real visitors are affected. Test access is always granted; it’s the baseline every team member gets.
Production — publish, pause, and edit live campaigns that run for real visitors. Grant this only to people you want touching live traffic.

A common setup is to give new teammates, contractors, or agencies Test only while they learn the account, then add Production once you’re confident in their work. Someone with Test but not Production can build and QA a campaign end-to-end but can’t push it live — a useful safety net that pairs naturally with the QA workflow.

The Environments column on the Team members list shows each person’s access at a glance: an environment they can’t access appears grayed out.

Managing Existing Members

From the Team members list you can:

Search by name or email to find someone in a large account.
Filter the list by Role or by Environment — for example, to audit everyone who currently has Production access.
Sort by user, role, or the date they were added.
Use the ⋮ menu on any row to change that member’s role, adjust their environments, or remove them from the account.

Removing someone from this account doesn’t delete their Personyze user — it only revokes their access here.

QA Campaigns — the full workflow for previewing and verifying a campaign before it goes live.
Personyze Test Mode in Console — how test mode works for your own session.
Set up a single sign-on (SSO) client — connect your identity provider instead of managing passwords per user.