Summary and recommendation
Teampay 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.
Teampay is a spend management platform that uses role-based access control roles such as requester, approver, and admin are documented in third-party sources, though official granular permission documentation is not publicly available.
It does not support native SCIM provisioning;
instead, user lifecycle management is handled through HR system integrations (e.g., BambooHR) and SSO IdP connectors (Okta, OneLogin).
This means every app provisioning and deprovisioning workflow runs through those upstream systems rather than directly inside Teampay.
Quick facts
| Admin console path | Public Teampay documentation does not expose a detailed internal user-admin path; user administration appears to happen in the authenticated Teampay workspace. |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Unknown |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin / finance admin | Manages cards, budgets, approvals, and workspace administration in the Teampay tenant. | Detailed public permission boundaries are not documented. | Not publicly documented | Custom contract | Public docs do not enumerate a full internal role matrix. |
| Requester / approver | Submits spend requests and participates in approval workflows as configured in the tenant. | Exact limits versus admin roles are not publicly documented. | Not publicly documented | Custom contract | Role names and boundaries should be verified in the live tenant. |
Permission model
- Model type: role-based
- Description: Teampay is documented in third-party sources as using role-based access (e.g., requester, approver, admin), but official granular permission documentation is not publicly available.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Not documented
How to add users
- Use the authenticated Teampay workspace to invite the user through the tenant-specific team or people-management area.
- Assign the appropriate role or approval responsibility during invite setup.
- If IdP provisioning is included in your contract, validate the identity flow in the tenant before relying on automated onboarding.
Required fields: Work email, Tenant-specific role assignment
Watch out for:
- Public help content does not expose the exact invite workflow, so production automation should be validated in the live tenant first.
| 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: Official documentation on delete vs. deactivate behavior is not publicly accessible. No verified source explicitly documents either capability.
- Use the tenant-specific user-management workflow inside the Teampay workspace to revoke access.
- If an IdP integration is enabled, remove or disable the user in the IdP first so authentication state stays aligned.
- Confirm delete-versus-deactivate behavior and spend-history ownership 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 |
|---|---|---|
| Custom contract | Teampay pricing is subscription-based and contract-specific rather than publicly documented per-seat tiers. | Custom |
- Where to check usage: Not documented
- How to identify unused seats: Not documented
- Billing notes: Pricing is subscription-based and varies by company size. Estimated ~$15K–$18K/year for 201–1,000 employees. Seat-level billing details are not publicly documented.
The cost of manual management
Teampay's subscription pricing is estimated at $15K–$18K/year for organizations with 201–1,000 employees, with a one-time onboarding fee of approximately $1,200 (sometimes waived). Seat-level billing details are not publicly documented, so cost-per-user calculations require direct vendor engagement. No self-serve pricing page or plan comparison is publicly available.
The decision
Teampay is a reasonable fit for teams already using BambooHR or an Okta/OneLogin IdP, since those integrations carry the provisioning load that SCIM would otherwise handle. Teams without those upstream systems in place will face a more manual access management burden, as there is no native SCIM or public API to fall back on.
Admin console path and granular permission documentation are not publicly accessible, so pre-sales discovery calls are likely necessary to validate fit.
Bottom line
Teampay covers spend management with role-based access, but its lack of native SCIM means every app access workflow depends on HR or IdP integrations being correctly configured upstream.
Official documentation on permission granularity, deactivation behavior, and seat-level billing is sparse, so teams should budget time for vendor-assisted setup and expect limited self-serve control over user lifecycle management.
Automate Teampay 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.
