Summary and recommendation
Criteria 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.
Criteria is a pre-employment assessment platform used by HR and talent acquisition teams to evaluate candidates across cognitive, personality, and skills-based tests.
Admin access is managed through the web console at app.criteriacorp.com.
Because Criteria does not offer native SCIM provisioning, every app lifecycle event - onboarding, role changes, and offboarding - must be handled manually by an administrator.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| 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 |
|---|---|---|---|---|---|
| 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: Criteria 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 | No | 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 |
|---|---|---|
| Named user | Administrative or standard access to the tenant. |
- 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: Subscription or per-assessment pricing available. Pricing ranges from approximately $1,200/year (Professional) to custom enterprise contracts averaging ~$32,000/year. Specific seat-cost details are not publicly documented.
The cost of manual management
Without automated provisioning, every app requires an admin to add or remove users by hand each time someone joins, moves teams, or leaves the organization. Criteria's pricing spans a wide range - from approximately $1,200/year at the Professional tier to enterprise contracts averaging around $32,000/year - meaning unused or orphaned accounts carry real cost exposure.
Specific per-seat billing details are not publicly documented, so identifying and reclaiming unused licenses requires direct coordination with Criteria's support or account team.
The decision
Criteria is a reasonable fit for teams that already manage candidate assessment workflows through connected ATS platforms like Greenhouse, Lever, or Workday, where data flow is handled via pre-built connectors.
Teams expecting directory-driven provisioning or automated deprovisioning will find a gap: there is no SCIM endpoint and no IdP connector support confirmed for Okta, Entra ID, Google Workspace, or OneLogin.
The manual overhead is proportional to hiring volume and org size - low-volume teams may find it manageable, while high-growth orgs should factor in the operational cost of fully manual access control.
Bottom line
Criteria delivers structured pre-employment assessment capabilities but ships no native SCIM or automated provisioning support, leaving every app access event as a manual admin task.
For organizations where Criteria sits inside a broader HR tech stack, the pre-built ATS/HRIS connectors partially offset this gap - but user lifecycle management remains outside the scope of those integrations.
Teams with strict access governance requirements should engage Criteria's enterprise sales team early to understand what, if any, directory integration options exist under a custom contract.
Automate Criteria 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.
