Summary and recommendation
AmazingHiring 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.
AmazingHiring is a recruiter-facing sourcing platform sold on a pay-per-seat, annual billing model.
There is no native SCIM support and no publicly documented IdP integration, which means every app lifecycle event onboarding, role change, offboarding must be handled manually through the platform's own admin interface.
Exact admin console paths and permission model details are not publicly documented;
confirm current workflows directly with AmazingHiring support before building any internal runbook.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| SCIM available | No |
| SCIM tier required | Custom |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Can manage tenant settings, integrations, and user access. | Cannot grant functionality outside the modules licensed for the tenant. | Detailed built-in role names are not fully documented publicly. | ||
| Standard User | Can use the core product features exposed to their role. | May not be able to manage tenant settings or other users. | Exact privileges can vary by tenant configuration. |
Permission model
- Model type: role-based
- Description: AmazingHiring appears to use role-based access for tenant administration and general product use, but the detailed permission matrix is not publicly documented in full.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Expect administrative access to be separated from standard user access, with exact scopes configured per tenant.
How to add users
- Log in as an administrator.
- Open settings or administration and navigate to users.
- Choose the add or invite user action.
- Enter the user's work email and assign the appropriate role.
- Save the user and complete any activation or SSO steps required by the tenant.
Required fields: Work email address, Role
Watch out for:
- Public documentation for user administration is limited, so exact labels may vary by tenant.
- If SSO is enabled, upstream IdP assignment may still be required.
| 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: Public docs do not clearly document whether users are disabled, deleted, or both. Treat lifecycle behavior as tenant-specific unless confirmed in-product.
- Open the users area as an administrator.
- Locate the user to offboard.
- Disable, revoke, or remove the account using the controls available in that tenant.
- Review any integrations or service credentials associated with the departing user.
| Data impact | Behavior |
|---|---|
| Owned records | Tenant data remains in the workspace; public docs do not describe user-owned content semantics in detail. |
| Shared content | Shared dashboards, configurations, and records remain available unless separately removed. |
| Integrations | Review service credentials and integration ownership separately during admin offboarding. |
| License freed | Seat reuse behavior is contract-dependent and not publicly documented in detail. |
Watch out for:
- Offboarding should include token and integration review, not just interactive login removal.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Recruiter seat | Full platform access per recruiter; exact feature scope per seat not publicly documented | From $4,800/user/year (~$400/user/month) based on publicly available pricing estimates |
- Where to check usage: Settings / Administration > Users and Roles
- How to identify unused seats: Review the tenant user list and any visible login or activity metadata. No public unused-seat report was verified.
- Billing notes: Pay-per-seat, annual billing model. A team of 5 recruiter seats costs approximately $24,000/year. Free trial available. Exact overage, mid-cycle add, or removal credit policies are not publicly documented.
The cost of manual management
At the publicly available estimate of $4,800 per seat per year, a five-recruiter team runs approximately $24,000 annually. Because there is no automated deprovisioning, a departing recruiter's seat continues to accrue cost until an admin manually removes it.
Mid-cycle removal credits, overage policies, and partial-month billing behavior are not publicly documented - meaning unmanaged seats represent a direct, unrecovered spend risk at this price point.
The decision
AmazingHiring is appropriate for recruiting teams that can absorb a fully manual identity lifecycle and are comfortable negotiating access and billing terms directly with the vendor. Every app in your stack that lacks SCIM adds compounding manual overhead; factor that into total IT cost when evaluating seat count.
Teams requiring automated provisioning, SSO enforcement, or audit-ready deprovisioning logs should treat the absence of those features as a hard constraint, not a roadmap item.
Bottom line
AmazingHiring offers no native SCIM, no confirmed IdP integrations, and no public API for user management - every provisioning and deprovisioning action is manual.
At $4,800 per seat per year, unmanaged seats carry real cost exposure, and the lack of community-documented admin workflows means teams should budget time to establish and validate their own internal processes directly with the vendor.
Automate AmazingHiring 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.
