Summary and recommendation
Hired user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Hired is a tech recruiting marketplace that operates on a placement-fee model rather than a traditional per-seat SaaS subscription. Unlike every app that exposes a self-service admin console, Hired routes employer account changes through a dedicated account manager or customer success representative. No publicly documented user-management interface has been identified in Hired's help center.
Quick facts
| Admin console path | Employer account team management inside the Hired workspace; public admin navigation is not documented and account-manager involvement is commonly referenced |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Enterprise |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Account Admin / Primary Contact | Presumed full access to employer account, candidate pipeline, and billing; manages team member access. Exact permission scope not publicly documented. | Role structure and exact capabilities are not publicly documented in Hired's help center. Configuration likely requires coordination with a Hired account manager. | |||
| Team Member / Recruiter | Presumed access to candidate pipeline and messaging within the employer account. Exact permission scope not publicly documented. | Likely cannot manage billing or add/remove other team members without admin privileges, but this is not confirmed in public documentation. | No publicly documented self-service workflow for adding or configuring recruiter-level team members has been identified. |
Permission model
- Model type: account-manager-mediated
- Description: Hired's employer account permission model is not publicly documented. Based on community feedback, access management for team members (e.g., adding recruiters) appears to be handled through account manager assistance rather than a self-service admin console.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Not documented
How to add users
- Sign in to the employer-side Hired account or contact the assigned Hired account manager for team access changes.
- Add the new recruiter or hiring-team member to the employer account using the available team-management flow or account-team request process.
- Assign the new user to the relevant hiring pipelines or employer workspace access scope.
- Verify that the new user can access candidate pipelines and messaging tools needed for their role.
Required fields: Work email address, Employer account association
Watch out for:
- No self-service user-invitation workflow has been confirmed in public documentation.
- Adding team members to an employer account may require contacting a Hired account manager or customer success representative.
- Steps and required fields are not publicly documented in Hired's help center.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | No | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: No public documentation exists describing whether Hired supports deactivation vs. deletion of team member accounts within an employer organization.
- Open the employer account's team-management surface or contact the Hired account manager to revoke the departing user's access.
- Remove the user from active employer-team membership.
- Confirm that candidate pipeline access and recruiter messaging access have been revoked.
- Review any candidate ownership or recruiter assignments that need to be transferred.
| Data impact | Behavior |
|---|---|
| Owned records | Not documented |
| Shared content | Not documented |
| Integrations | Not documented |
| License freed | Not documented |
Watch out for:
- No publicly documented process for removing or deactivating a team member from an employer account has been identified.
- Removal may require contacting a Hired account manager.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Employer account (placement-fee model) | Access to candidate marketplace; pricing is a percentage-based finder's fee on placed candidate annual compensation (reported at approximately 30%) or custom Enterprise pricing. Not a per-seat subscription. | Approximately 30% finder's fee on annual compensation for standard placements; custom pricing for Enterprise |
- Where to check usage: Not documented
- How to identify unused seats: Not documented
- Billing notes: Hired operates primarily as a marketplace with placement fees rather than a traditional per-seat SaaS license. Enterprise plans include custom pricing. No publicly documented seat-count or license-usage dashboard has been identified. Billing and account structure details are managed through Hired account managers.
The cost of manual management
Because Hired does not expose a self-service admin console, every access change - adding a recruiter, adjusting team member permissions, or removing a departed employee - requires a support or account manager touchpoint.
There is no documented deactivation or deletion workflow for team members, meaning offboarding a user from an employer account cannot be confirmed as a self-service action. For IT and ops teams managing access across every app in their stack, the absence of a predictable, auditable process introduces real offboarding risk.
What IT admins are saying
Employer reviewers on G2 and TrustRadius flag limited transparency into how team member roles and access are managed within an employer account.
A recurring theme is that routine tasks - such as adding recruiters or adjusting access - appear to require contacting a Hired account manager rather than using in-product controls.
The absence of publicly accessible admin documentation makes it difficult for IT and ops teams to evaluate or audit access controls independently.
Common complaints:
- Employer reviewers on G2 and TrustRadius report limited transparency into how team member access and roles are managed within an employer account.
- Some employer reviewers note that account management tasks such as adding recruiters or adjusting access appear to require contacting a Hired account manager rather than using self-service controls.
- No publicly documented SCIM, SSO, or IDP provisioning support has been confirmed for any pricing tier.
- The absence of a publicly accessible admin console or help documentation for user management makes it difficult for IT/ops teams to evaluate or audit access controls.
The decision
Hired's permission model is not publicly documented, and no confirmed role types, granularity levels, or custom role capabilities have been identified. When evaluating every app in your stack for self-service access governance, Hired stands out as a manual-touch dependency - adding or removing team members likely requires coordination with a Hired account manager.
Enterprise pricing is available with custom features, but no public documentation confirms what access-management capabilities, if any, are included.
Bottom line
Hired is purpose-built as a tech recruiting marketplace, and its access management reflects that - account changes are handled through account manager coordination rather than a self-service admin console. No SCIM, SSO, or IDP provisioning support has been confirmed at any pricing tier.
For IT and ops teams responsible for governing every app in the environment, Hired represents a manual-touch dependency with limited auditability until Hired publishes clearer admin documentation or self-service controls.
Automate Hired workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
