Summary and recommendation
PathFactory 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.
PathFactory does not offer native SCIM provisioning, and its official help documentation is largely gated behind a customer login.
This means that verifying exact user management workflows - add, deactivate, or role assignment - requires authenticated access to PathFactory's help center.
Like every app that lacks a provisioning standard, PathFactory places the operational burden squarely on your IT or ops team.
Pricing is custom/enterprise only, with no publicly available seat-cost or tier breakdown.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| SCIM available | No |
| SCIM tier required | N/A |
| 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 capabilities outside the modules or features enabled for the tenant. | Detailed built-in role names are not fully documented publicly. | ||
| Standard User | Can use the core product features exposed to their assigned role. | May not be able to manage tenant settings, integrations, or other users. | Exact privileges can vary by tenant configuration and contract scope. |
Permission model
- Model type: role-based
- Description: PathFactory is documented by third-party SSO integration guides as using role-based access control, but official granular role definitions are not publicly available without a logged-in help center session.
- 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 before the user can sign in.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | Unknown | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Official documentation on delete vs. deactivate behavior is not publicly accessible; cannot confirm either capability without authenticated help center access.
- 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, service accounts, or 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 content and workspace records typically remain available unless separately removed or reassigned. |
| Integrations | Review service credentials, workflow ownership, and integrations 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, integration, and service-account review, not just interactive login removal.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Named User | Access to the tenant features exposed to the assigned role. Seat entitlements are generally tied to the subscription contract. | Custom pricing; determined by contract and plan. |
- 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: PathFactory pricing is custom/enterprise only; no public seat-cost or tier breakdown is available.
The cost of manual management
Without SCIM or a public provisioning API, every app in your stack that lacks automation creates a recurring manual overhead - and PathFactory is one of them. Offboarding in particular carries risk: official documentation on delete vs.
deactivate behavior is not publicly confirmed, so IT teams cannot verify whether removing a user fully revokes access or simply suspends it. At custom/enterprise pricing with no public seat model, untracked active seats have an unquantifiable but real cost.
The decision
PathFactory's permission model is role-based, but granular role definitions are not publicly available - and like every app where role documentation is gated, this creates blind spots for access governance reviews.
Custom roles, their scope, and which plan tier (if any) unlocks them cannot be confirmed without authenticated help center access or direct contact with PathFactory support. Teams evaluating PathFactory for environments with strict access governance should treat role granularity as an open question until confirmed with their account team.
Bottom line
PathFactory is a content intelligence platform built for marketing teams, not one designed with IT-friendly provisioning in mind. There is no SCIM, no public user management API, and no publicly accessible documentation on deactivation behavior or role granularity.
Every app without automated provisioning adds manual lift to your joiner-mover-leaver workflows, and PathFactory currently sits firmly in that category. Until PathFactory exposes a provisioning interface or publishes its admin documentation openly, user lifecycle management will depend on manual processes and direct vendor support.
Automate PathFactory 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.
