Summary and recommendation
seoClarity 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.
seoClarity is an enterprise SEO platform with pricing structured around keywords tracked and modules enabled - not per-seat fees.
Unlimited users are included across plans per public pricing documentation, which removes seat-count as a provisioning concern.
However, the exact workflow for inviting or managing users is not publicly documented in official help content.
Like every app that lacks SCIM, access changes depend entirely on manual UI steps.
Quick facts
| Admin console path | Public seoClarity help content does not expose a detailed user-admin click path; user administration occurs in the authenticated seoClarity workspace. |
| 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 | Workspace administration and user management inside the seoClarity tenant. | Detailed public permission boundaries are not documented. | Not publicly documented | Included in plan | Public docs do not enumerate a detailed role matrix. |
| Standard user | Uses SEO analysis and workflow features assigned in the tenant. | Exact admin restrictions are not publicly documented. | Not publicly documented | Included in plan | Unlimited users are included publicly, but invite and role-assignment steps are not documented in accessible help content. |
Permission model
- Model type: role-based
- Description: seoClarity publicly references role-based access controls, but specific role names, permission boundaries, and plan-tier requirements are not documented in publicly accessible official sources.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Not documented
How to add users
- Use the authenticated seoClarity workspace to invite or create the user through the tenant user-management area.
- Assign the appropriate role and workspace access in the tenant.
- If SSO is enabled through Okta or Entra ID, validate the identity flow in the live tenant because SCIM is not publicly documented.
Required fields: Work email, Tenant-specific role assignment
Watch out for:
- Unlimited users are included per the pricing page, but the exact invite or provisioning workflow is not documented in publicly accessible help content.
- SSO via Okta (SAML) is confirmed, but automated provisioning (SCIM) is not publicly documented, meaning user creation may require manual steps even in SSO configurations.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | Yes | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: No official documentation found publicly describing whether users can be deleted or only deactivated, or what happens to their data upon removal.
- Use the tenant-specific user-management workflow inside the seoClarity workspace to revoke access.
- If SSO is enabled, remove or disable the user in the IdP so authentication state stays aligned.
- Confirm delete-versus-deactivate behavior and downstream data impact directly in the tenant because public docs do not describe those semantics.
| Data impact | Behavior |
|---|---|
| Owned records | Not documented |
| Shared content | Not documented |
| Integrations | Not documented |
| License freed | Not documented |
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| User seat | Unlimited users included across plans per public pricing page; no per-seat fee documented. | Included in plan |
- Where to check usage: Not documented
- How to identify unused seats: Not documented
- Billing notes: Pricing is based on keywords tracked and modules enabled, not per-seat. Publicly listed plan starting prices: Essentials ~$750/mo, Research & Content ~$2,500/mo, Technical SEO ~$3,200/mo, Enterprise $4,500+/mo. Seat counts are not a billing variable per public documentation.
The cost of manual management
Because seoClarity does not publicly document SCIM provisioning, deprovisioning a departing employee requires manual UI steps with no confirmed guidance on deletion versus deactivation. There is no public documentation describing what happens to user-associated data upon removal. This makes audit-readiness harder to maintain at scale without a defined offboarding process.
The decision
Every app in your stack without automated provisioning adds manual overhead - seoClarity is no exception. SSO via Okta or Microsoft Entra ID is confirmed and handles session-level access control, but does not cover provisioning.
Teams requiring fully automated user lifecycle management should verify SCIM availability directly with seoClarity before committing, as no public documentation confirms it exists.
Bottom line
seoClarity's unlimited-user model removes per-seat cost friction, but the absence of publicly documented SCIM or a clear offboarding workflow means identity lifecycle management falls entirely on admins. SSO via Okta covers authentication, not provisioning.
Until seoClarity documents a programmatic user-management path, every access change - onboarding or offboarding - requires manual intervention through the web UI.
Automate seoClarity 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.
