Roles and permissions
A complete reference for what admins and recruiters can do, where the All and My scope toggle applies, and what is shared versus private.
Roles and permissions
QualifyCode uses two roles inside a workspace. This page is the precise reference for what each role can do, where the All / My scope toggle applies, and what stays private to a single recruiter.
Role summary
| Role | Purpose |
|---|---|
| Admin | Owns the workspace. Manages members, billing, and settings. Can see and edit every assessment, candidate, and result. |
| Recruiter | Runs their own hiring pipeline. Creates and edits their own assessments, sees their own candidates, and records screening decisions. |
A user has exactly one role per workspace. Roles are workspace-wide, not per-assessment.
Assessment access
| Action | Admin | Recruiter |
|---|---|---|
| Create an assessment | Yes | Yes |
| Edit a draft assessment | Yes (any) | Yes (own) |
| View an assessment | Yes (any) | Yes (own) |
| Cancel an assessment | Yes (any) | Yes (own) |
| Delete a draft assessment | Yes (any) | Yes (own) |
| Share an assessment with another user (VIEW or EDIT) | Yes (any) | Yes (own, OWN permission only) |
| See the All / My scope toggle | Yes | No (always My) |
| Use the All scope | Yes | No |
When an assessment is shared with a user, the recipient gains the chosen permission for that assessment only, without joining its owner's hiring pipeline. See Sharing and collaboration for the full model.
Candidate and result access
| Action | Admin | Recruiter |
|---|---|---|
| Add candidates to an assessment | Yes (any) | Yes (own) |
| Send invitations and reminders | Yes (any) | Yes (own) |
| View candidate results | Yes (any) | Yes (own) |
| Record a screening verdict | Yes (any) | Yes (own) |
| Add private notes | Yes (any) | Yes (own) |
| Add a candidate to a shortlist | Yes (any) | Yes (own) |
The Screening console lists candidates across all of your own assessments. Candidates from other recruiters' assessments are not visible.
Templates
| Action | Admin | Recruiter |
|---|---|---|
| Create a template from an assessment | Yes (any) | Yes (own) |
| Use a template to launch a new assessment | Yes | Yes |
| Share a template company-wide | Yes | Yes (own) |
| Archive a template | Yes (any) | Yes (own) |
See Templates for the lifecycle.
Templates and policy (Role Bar)
| Action | Admin | Recruiter |
|---|---|---|
| Author a screening policy (Role Bar) | Yes | No |
| Preview a policy's impact | Yes | Yes |
| Adopt a new policy version | Yes | No |
| Configure automation | Yes | No |
| Halt automation | Yes | Yes |
See Role Bar and policy and Automation.
Assessment approval
The optional assessment approval step adds a third participant — an approver — distinct from the admin and recruiter workspace roles. Approval is performed by authorized recruiters and hiring managers who have been designated as approvers for the workspace.
| Action | Eligible approver | Other members |
|---|---|---|
| Request approval | Yes | Yes |
| Approve the design | Yes | No |
| Request changes | Yes | No |
| Continue safe preparation while approval is pending | Yes | Yes |
A dual approval policy requires both a recruiter and a hiring manager to sign off. Under single approval, one authorized approver is enough. The approver designation is separate from the admin and recruiter roles: an approver's scope is limited to signing off assessment designs, not managing the workspace.
Billing
| Action | Admin | Recruiter |
|---|---|---|
| Buy credits | Yes | No |
| See workspace ledger and spend | Yes | No (own spend only) |
| Manage payment methods | Yes | No |
See Payments.
Notifications
Notifications split into what the workspace shares and what is private to you. The chat app is connected once for the whole workspace (any member can do that first connect), its shared destinations are an admin decision, and every person controls their own personal delivery.
| Action | Admin | Recruiter |
|---|---|---|
| Connect the workspace Slack/Teams app (one-time, workspace-wide) | Yes | Yes, if not connected yet |
| Add or remove the workspace's shared destinations | Yes | No |
| Choose which events post to the shared Slack channel | Yes | No |
| Link my own Slack/Teams account for direct messages | Yes | Yes |
| Choose which events send me a direct message | Yes | Yes |
Two things are worth calling out:
- Linking is self-scoped. A direct-message link belongs to the person who created it; it never lets one member see another's messages, and it never posts to a shared channel.
- The workspace connection is one app for everyone. It is installed once for the whole workspace (any member can do that first install). Choosing and changing the shared destinations, and disconnecting the app, stay with administrators. When a workspace restricts installation, a member sees a Request an admin action instead — that only notifies the admins, it grants no permission.
See Notifications for the setup steps.
Workspace and settings
| Action | Admin | Recruiter |
|---|---|---|
| Open the Workspace page | Yes | No |
| Invite, promote, demote, or remove members | Yes | No |
| Open Settings | Yes | No |
| Delete own account | Yes (with the "last admin" safeguard) | Yes |
What is shared versus private
- Shared across the workspace: problem library, AI-generated variations, public templates (the Shared tab), the screening policy, and the wallet ledger (admins only).
- Private to the creator: an assessment's candidates, results, notes, shortlists, private templates (the Mine tab), and the candidate screening verdicts.
The All / My scope toggle on the assessment list determines whether admins see company-wide assessments or just their own. It does not change candidate or result visibility within a single assessment once opened.