Account & access
How accounts are created, how members get in, and what each role can do.
The operational problem
Frontline operations rarely give the same person every kind of access. A site manager needs the roster and the rewards ledger, not the billing page. A recruiter needs jobs and candidates, not goal configuration. When everyone has the same login, sensitive work is one click from the wrong hand, and audit trails fall apart.
How Array HQ solves it
Access is scoped two ways: by organization (the workspace) and by role (the permission set). Together they decide what each member sees. New members come in by invitation from an Owner or Admin, with a role chosen at the moment of invite. Roles are editable later — access changes don't require recreating the account.
How it works
Account creation
Array HQ provisions your account at the start of the relationship. Owners are seeded by Array; everything from there is self-serve.
Inviting members
Owners and Admins invite new members from Administration → Invite members. The invitation captures email, role, and organization scope. The invitee sets a password on first login.
Roles
The role catalog is fixed today:
| Role | Sees | Does |
|---|---|---|
| Owner | Everything | Anything, including billing |
| Admin | Everything except billing | Manage members, configure goals, run both products |
| Operator | Roster, goals, rewards in their organization | Run //Ops day-to-day |
| Recruiter | Jobs and candidates in their organization | Run //Recruiting day-to-day |
| Team Member | Their own profile, points, leaderboard | Earn and redeem points |
See Members and roles for the full permission matrix.
Logging in
Members log in at the operator portal (web) or the Talent app (mobile, for Team Members). Both share the same identity. A Team Member who later becomes a manager simply gets a role change — they don't get a second login.
What you'll be able to do
- Invite a recruiter and have them seeing only //Recruiting.
- Promote a Team Member to Operator after a role change on the roster.
- Remove access immediately when someone leaves — without breaking their historical data.