Summary and recommendation
Capsule CRM 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.
Capsule CRM is an SMB-focused CRM with a straightforward role-based permission model: Administrator, Full User, and Restricted User. There are no custom role definitions - permissions are predefined, with some record-level visibility controls and team-based scoping available on higher tiers.
Every app in your stack that relies on Capsule for contact and pipeline data is affected by how cleanly user access is maintained here.
Quick facts
| Admin console path | Account Menu (top-right avatar) → Account Settings → Users & Teams |
| 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 |
|---|---|---|---|---|---|
| Administrator | Full access to all account settings, billing, user management, all contacts, opportunities, cases, tasks, and reports. Can invite and remove users, assign roles, and configure integrations. | All paid plans (Starter, Growth, Advanced, Ultimate); Free plan supports up to 2 users with admin role. | Same per-user seat cost as the plan tier; no separate admin seat pricing. | Only Administrators can access billing and account settings. There is no separate 'Owner' role distinct from Administrator in the UI. | |
| Full User | Can create, view, edit, and delete contacts, opportunities, cases, tasks, and calendar entries. Access to reports depends on plan. Cannot access account settings or billing. | Cannot manage users, change billing, or access account-level configuration. | All paid plans. | Starter: $18/user/month; Growth: $36/user/month; Advanced: $54/user/month; Ultimate: $72/user/month (billed annually; monthly billing is higher). | Each invited user consumes a paid seat regardless of activity level. |
| Restricted User (Read-Only / Limited Access) | Can view records they have been granted access to. Cannot create or edit records outside their permitted scope. | Cannot edit records, manage users, or access billing. Scope of access is controlled by the Administrator. | Available on Growth plan and above; exact availability should be verified against current help docs. | Consumes a standard paid seat at the plan's per-user rate. | Capsule does not offer a free read-only seat type; restricted users still consume a billable seat. |
Permission model
- Model type: role-based
- Description: Capsule CRM uses a role-based permission model with a small set of predefined roles (Administrator, Full User, and limited/restricted access). Administrators can restrict what individual users can see and do at the record level (e.g., limiting visibility of opportunities or cases), but there are no fully custom role definitions. Team-based access controls allow grouping users so that certain records are visible only to specific teams.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Role-level (Administrator vs. standard user) with some record-level visibility restrictions and team-based scoping. Granular field-level permissions are not available.
How to add users
- Log in as an Administrator.
- Click the account avatar or name in the top-right corner.
- Select 'Account Settings'.
- Navigate to 'Users & Teams'.
- Click 'Invite User' or 'Add User'.
- Enter the invitee's email address.
- Select the appropriate role (Administrator or standard user).
- Optionally assign the user to one or more Teams.
- Click 'Send Invitation'.
- The invitee receives an email and must accept the invitation to activate their account.
Required fields: Email address, Role selection
Watch out for:
- Adding a user immediately increases the billable seat count and will be reflected in the next billing cycle.
- The invited user must accept the email invitation before they can log in; the seat is counted as soon as the invitation is sent on some plan configurations.
- Free plan is capped at 2 users total; additional users require a paid plan upgrade.
- No bulk CSV import for users is available natively.
- Domain whitelisting (auto-provisioning users from a domain) is not supported.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | No | Not documented |
How to remove or deactivate users
- Can delete users: No
- Delete/deactivate behavior: Capsule CRM does not permanently delete user accounts. Administrators can deactivate (suspend) a user, which revokes their login access. The user's historical data, records, and activity log entries are retained and remain associated with their account. Deactivated users do not consume a billable seat.
- Log in as an Administrator.
- Navigate to Account Settings → Users & Teams.
- Locate the user to be removed.
- Click on the user's name or the options menu next to their name.
- Select 'Deactivate' or 'Remove User'.
- Confirm the action when prompted.
- Reassign or review any open tasks, opportunities, or cases previously owned by that user.
| Data impact | Behavior |
|---|---|
| Owned records | Records (contacts, opportunities, cases, tasks) previously owned by or assigned to the deactivated user remain in the account and are accessible to Administrators. Ownership can be reassigned to active users. |
| Shared content | Shared notes, activity history, and attachments associated with the deactivated user are retained in the account. |
| Integrations | Any integrations (e.g., email sync, calendar sync) connected under the deactivated user's credentials will stop functioning for that user. Administrators should disconnect or reassign integrations before deactivating. |
| License freed | The seat is freed upon deactivation and the per-user charge is removed from the next billing period. |
Watch out for:
- Open tasks and opportunities assigned to a deactivated user should be manually reassigned before deactivation to avoid orphaned records.
- Email sync (e.g., Gmail or Outlook integration) tied to the departing user's mailbox will cease; historical synced emails remain but new emails will not be captured.
- Capsule does not offer an automated offboarding workflow; record reassignment must be done manually by an Administrator.
- Deactivated users cannot be permanently deleted, so their profile remains visible in historical records.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Free Plan Seat | Up to 2 users, 250 contacts, 50 MB storage. Basic CRM features. | $0 |
| Starter Seat | Unlimited users (billed per seat), 30,000 contacts, 10 GB storage, basic sales pipeline. | $18/user/month (annual billing) |
| Growth Seat | 60,000 contacts, 20 GB storage, advanced sales reporting, multiple pipelines, team-based permissions. | $36/user/month (annual billing) |
| Advanced Seat | 120,000 contacts, 40 GB storage, advanced customization, priority support. | $54/user/month (annual billing) |
| Ultimate Seat | 240,000 contacts, 100 GB storage, dedicated customer success manager. | $72/user/month (annual billing) |
- Where to check usage: Account Settings → Users & Teams (shows active user count); Account Settings → Billing (shows current seat count and charges).
- How to identify unused seats: Administrators can review the Users & Teams list and check last login dates or activity to identify inactive users. Capsule does not provide a built-in 'last login' report in the standard UI; identification of unused seats requires manual review of user activity.
- Billing notes: Billing is per active (non-deactivated) user seat. Seats are added immediately upon invitation acceptance (or invitation sending, depending on plan). Removing a user mid-cycle may result in a prorated credit depending on billing terms. Annual plans are billed upfront; monthly plans are billed each month. Prices listed are for annual billing; monthly billing rates are higher.
The cost of manual management
Every invited user immediately consumes a paid seat - including restricted users, who have no free read-only tier. There is no bulk CSV import for users, so provisioning must happen one invitation at a time.
Deprovisioning is equally manual: open tasks and opportunities assigned to a departing user must be reassigned by an Administrator before deactivation, with no automated offboarding workflow to catch orphaned records.
What IT admins are saying
The most consistent friction reported by IT and security teams centers on SSO limitations: Capsule does not support native SAML or OIDC. The Okta integration uses SWA (password vaulting), which is widely regarded as a weaker security posture than federated SSO.
Microsoft 365 SSO is available but is also non-SAML. Secondary complaints focus on the absence of granular custom roles and the lack of a built-in last-login report, making unused seat identification a manual process.
Common complaints:
- No true SSO federation (SAML/OIDC not supported natively; Okta integration uses SWA password vaulting only).
- Limited enterprise features compared to larger CRM platforms.
- SWA-based Okta integration is considered less secure than SAML-based SSO by IT/security teams.
- No bulk user import via CSV; users must be invited one at a time.
- No automated offboarding or record reassignment workflow when removing users.
- No granular custom role creation; permission model is limited to predefined roles.
- No built-in last-login reporting to easily identify inactive seats.
- Domain whitelisting or auto-provisioning of users is not available.
- SCIM provisioning is not supported, making automated user lifecycle management from an IdP impossible.
The decision
Capsule CRM is a practical fit for small teams that do not require federated identity management or granular role customization. Teams operating under stricter IT or compliance requirements - particularly those expecting SAML-based SSO or SCIM provisioning - will find meaningful gaps.
Every app in a security-conscious stack should be evaluated against those gaps before committing to Capsule at scale. Growth plan or above is required for team-based access controls and multiple pipelines.
Bottom line
Capsule CRM delivers a clean, low-overhead user management experience for SMB teams comfortable with predefined roles and manual provisioning workflows.
The absence of SAML SSO, SCIM support, bulk user import, and automated offboarding means that every app touchpoint in your identity lifecycle requires hands-on Administrator effort.
Teams with more than a handful of users or with formal IT governance requirements should weigh those operational costs carefully before scaling on this platform.
Automate Capsule CRM 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.
