Summary and recommendation
6sense 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.
6sense user management lives entirely in Settings > User Management (https://analytics.6sense.com/settings/user-management). The platform uses a role-based access control model scoped per product module - ABM, Sales Intelligence (SI), and Conversational Email (CE) - with no custom role creation documented. The Primary Administrator is the single root account; all other role grants flow from that seat.
There is no SCIM provisioning available; 6sense has officially paused new SCIM enablement until Q4 2026, so every app lifecycle action - invite, role change, deactivation - is manual or dependent on JIT SSO.
Quick facts
| Admin console path | Settings > User Management |
| 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 |
|---|---|---|---|---|---|
| Primary Administrator | Full platform access across all 6sense applications. Invites and manages all other users and administrators. Configures SSO, integrations, WebTag, credits distribution, fiscal year, and security settings. Sole role that can grant other admin roles. Consumes one license on each application purchased. | Cannot be shared across multiple people; must be a single user consistent across all 6sense applications. | Any paid plan (ABM, SI, or CE) | Consumes one licensed seat per application subscribed | Primary Admin consumes one license on each application (e.g., one ABM license and one SI license if both are purchased). All users including Primary Admins count toward license totals. |
| Marketing Administrator (ABM Administrator) | Manages the Revenue Marketing (ABM) platform. Creates segments, mapping profiles, ad campaigns, audience/data workflows. Allocates credits to users. Configures contact consent settings and smart form fills. | Cannot manage SI-specific settings or SI user roles unless also granted SI Administrator access. | ABM Platform subscription | Consumes one ABM licensed seat | Assigned by the Primary Administrator. Role permissions for creating workflows must be explicitly granted at Settings > User Management > Roles > Choose App ABM. |
| Sales Administrator | Manages user permissions, credits, and integrations for Sales Intelligence. Can invite and manage Sales AE and Sales SDR users. Can edit existing user roles in bulk or individually. | Cannot manage ABM platform settings unless also granted ABM Administrator access. | Sales Intelligence (SI) subscription | Counts toward contracted SI license total | Must be granted by the Primary Administrator first. Adding any user to a sales role (including Sales Administrator) immediately counts toward the contracted SI license count. |
| Sales AE / Sales SDR (SI User) | Access to Sales Intelligence web app, Chrome Extension, and CRM/SEP iFrame. Can discover accounts and contacts, unlock contact data using credits, and export records to CRM, SEP, or CSV. | Cannot access SI export settings or mapping profiles (Administrator role required for those). Cannot manage other users. | Sales Intelligence (SI) subscription | Counts toward contracted SI license total | 6sense recommends waiting to grant access to sellers until just before a formal sales rollout. Unregistered CRM/SEP users (no SI role assigned) who access SI via CRM iFrame still count toward the SI license allowance based on 90-day activity. |
| AI Email (AIE) Administrator | Adds AIE team users, integrates with Salesforce or HubSpot CRM, sets up email provider, AI email agent, and email warmup. Adds sales reps for email routing. | Cannot manage ABM or SI platform settings unless separately granted those roles. | Conversational Email (CE) / AI Email subscription | Counts toward contracted CE license total | CE does not technically enforce license limits in-app; Primary Admin can over-invite. Customer is responsible for compliance with contracted CE seat count. |
| Insight User | Minimal access to the 6sense platform. Default role assigned to new users provisioned via SSO/JIT on first login. | Cannot access most platform features until promoted to an appropriate role by an Administrator. | Any plan | Counts toward ABM licensed seat if on ABM platform | SSO/JIT-provisioned users appear in User Management only after their first login and are assigned Insight User by default. Admin must manually promote them to the correct role. |
Permission model
- Model type: role-based
- Description: 6sense uses a role-based access control (RBAC) model. Roles are scoped per application (ABM, SI, CE). The Primary Administrator assigns application-specific roles to users. Roles are predefined per product module; there is no evidence of fully custom role creation in official documentation. Administrators can assign roles individually or in bulk via Settings > User Management.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Application-level role assignment (ABM, SI, CE) with some feature-level permission toggles (e.g., enabling/disabling CSV export globally via Settings > App Settings > Sales Intelligence > SI Actions Settings). No documented per-user granular permission overrides.
How to add users
- Log in as Primary Administrator or Sales Administrator (for SI users).
- Navigate to Settings > User Management > Invite User(s).
- Enter the email address(es) of the user(s) to invite. Separate multiple addresses with commas.
- Select the appropriate role from the dropdown (e.g., Sales Administrator, Sales AE, ABM Administrator).
- Click Send Invite(s).
- New user receives an email invitation and must accept it before logging in.
- If SSO is enabled, use the IdP console to grant the user access to the 6sense SAML application instead; the user will appear in 6sense User Management after their first SSO login and will be assigned the Insight User role by default.
- After first SSO login, navigate to Settings > User Management and promote the user to the correct role.
Required fields: Email address, Role selection
Watch out for:
- If SSO is active, email-based invitations are bypassed; users must be provisioned through the IdP and will only appear in 6sense after their first login.
- New SSO/JIT users default to the Insight User role (minimal access) and must be manually promoted by an Admin.
- Adding any user to a sales role immediately consumes an SI license seat.
- SI license limits are enforced in-app: if the contracted seat count is reached, the Primary Admin cannot invite additional SI users and will see 'License limit exhausted. Please get in touch with your CSM.'
- ABM Platform does not enforce license limits in-app; Primary Admin can over-invite beyond contracted seats. Customer is responsible for self-policing compliance.
- All users including Administrators and Primary Admins consume a licensed seat.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Yes | Settings > User Management (CSV bulk upload for sales reps, released May 2025 per release notes) |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Available on any plan with SSO configured; uses JIT (Just-in-Time) provisioning via SAML 2.0. SCIM provisioning is paused until Q4 2026. |
How to remove or deactivate users
- Can delete users: No
- Delete/deactivate behavior: Official documentation references disabling/deactivating users rather than permanent deletion. To free up an SI license seat when the limit is reached, admins must disable currently enabled users. The UI path is Settings > User Management; select the user via the ellipsis menu > View and Edit User > change status. No official documentation confirms a hard-delete option for user accounts.
- Navigate to Settings > User Management.
- Locate the user (use Filters to search by email or status if needed).
- Click the ellipsis (…) next to the user under 'Last Login'.
- Select 'View and Edit User'.
- Change the user's status to Disabled/Inactive.
- Save the change.
- For bulk status changes in SI: go to Settings > User Management > Filters, filter by email addresses, select checkboxes, then use Bulk Actions > Change SI Role or status.
| Data impact | Behavior |
|---|---|
| Owned records | Not explicitly documented in official sources. No official statement on reassignment of owned records upon deactivation. |
| Shared content | Not explicitly documented. Workflows, segments, and campaigns created by the user remain in the platform per observed behavior, but official documentation does not specify ownership transfer. |
| Integrations | Deactivating a user does not affect platform-level CRM/SEP integrations, which are tied to the integration user (API token), not individual user accounts. |
| License freed | Disabling a user frees the consumed SI license seat, allowing a new user to be invited within the contracted limit. ABM license counts are based on invited/enabled users shown in Settings > User Management > Users. |
Watch out for:
- SI license limits are enforced; to invite a new SI user when at the limit, an existing enabled user must be disabled first.
- ABM Platform does not enforce limits in-app; over-inviting is possible but the customer is contractually responsible.
- Unregistered SI CRM/SEP users (no role assigned, accessing via CRM iFrame) count toward the SI license based on 90-day activity; disabling their CRM access requires restricting the CRM package permissions, not just the 6sense platform role.
- If SSO is in use, deactivating the user in the IdP will deactivate their 6sense access (Okta integration supports deactivation when unassigned in Okta).
- No documented self-service permanent deletion of user accounts.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| ABM Platform Users | Access to the 6sense Revenue Marketing (ABM) platform, including segments, campaigns, audience workflows, data workflows, and analytics. Includes all ABM roles (Primary Admin, Marketing Admin, Insight User, etc.). | Custom contract pricing; not enforced in-app. Median buyer ~$55,211/year (Vendr). Enterprise $100,000+/year. |
| Sales Intelligence (SI) Registered Users | Named users with an SI role assigned in User Management. Access to SI web app, Chrome Extension, and CRM/SEP iFrame. Credits consumed for contact unlocks and enrichment. | Custom contract pricing per seat; SI license limits are enforced in-app. |
| SI CRM/SEP Unregistered Users | Users without an SI role in 6sense User Management who access SI features via CRM or SEP iFrame. Counted based on any activity (click, hover, scroll) in the last 90 days. | Count toward contracted SI license allowance. Tracked separately in the license usage display. |
| Conversational Email (CE) Users | Access to the AI Email (Conversational Email) platform. CE license limits are not enforced in-app; customer is responsible for compliance. | Custom contract pricing. |
- Where to check usage: Settings > User Management > Users (license usage summary displayed just below user details; shows ABM Users X/Y, SI Users X/Y, CE Users X/Y depending on subscribed packages)
- How to identify unused seats: Filter users by 'Last Login' date in Settings > User Management to identify users who have not logged in recently. For SI CRM/SEP unregistered users, the platform tracks 90-day activity. No automated unused-seat report is documented; admins must manually review the user list and last login timestamps.
- Billing notes: The 6sense ABM Platform does not enforce contractual license limits in-app; Primary Admins can over-invite. SI enforces limits in-app for registered users. Customers are responsible for self-monitoring and must contact their CSM or Account Manager if usage exceeds contracted seats. All users including Administrators consume a licensed seat. The Primary Admin consumes one license per application (e.g., one ABM seat and one SI seat if both are purchased). SI plans (Team, Growth, Enterprise) are consolidating into a single license with three variants as of May 2025 release.
The cost of manual management
Without automated provisioning, every app in your stack that touches 6sense user state requires a manual admin action.
Onboarding a seller means navigating to Settings > User Management, sending an invite, and then returning after their first SSO login to promote them from the default Insight User role (minimal access) to the correct SI or ABM role - two separate steps per user.
Offboarding has no system-level enforcement: SI registered seats are capped in-app and will block new invites when the limit is hit, but ABM and CE seats are not enforced, creating silent over-provisioning risk.
Unregistered SI users who access 6sense via a CRM iFrame still consume a licensed seat based on 90-day activity, and there is no automated report to surface them - admins must manually audit last-login timestamps in the user list.
What IT admins are saying
Recurring friction reported by 6sense admins centers on three areas. First, JIT SSO provisioning assigns every new user the Insight User role on first login regardless of their actual job function, requiring a manual promotion step that is easy to miss at scale.
Second, the absence of SCIM means role changes and offboarding have no IdP-driven automation path; deactivating a user in Okta will deactivate their 6sense access, but role synchronization is not possible.
Third, the global-only CSV export toggle (Settings > App Settings > Sales Intelligence > SI Actions Settings) is a common complaint - there is no per-user override, so enabling or disabling export affects all SI users simultaneously.
Common complaints:
- No SCIM provisioning available; paused until Q4 2026, requiring all user lifecycle management to be done manually or via JIT SSO.
- JIT SSO provisioning assigns all new users the minimal 'Insight User' role by default; admins must manually promote each user after first login.
- ABM Platform does not enforce license limits in-app, creating risk of inadvertent over-provisioning beyond contracted seats.
- Steep learning curve for platform navigation, including locating admin and user management settings.
- Sales teams report resistance to adoption due to complex interfaces and workflows that don't align with how they sell.
- No granular per-user permission overrides; CSV export toggle is global (Settings > App Settings > Sales Intelligence > SI Actions Settings), not per-user.
- Unregistered CRM/SEP users who access SI via iFrame still consume SI license seats based on 90-day activity, which can cause unexpected license overages.
- Implementation complexity is high; typical implementation takes 60+ days and costs $5,000–$50,000.
- Limited attribute mapping for SSO; no SCIM attribute sync available.
Representative quotes (verbatim):
New users are initially assigned the Insight User role, which has minimal access to the 6sense platform.
- 6sense RevCity community post (official 6sense support response), September 2022 (https://revcity.6sense.com/home/discussion/69/saml-sso-enabled-but-why-aren-039-t-users-appearing-in-6sense-once-added-in-identity-provider-idp)
License limits will not be enforced for ABM roles.
- 6sense official product announcement on RevCity, July 2023 (https://revcity.6sense.com/home/discussion/483/new-user-management-feature-licensing-metering)
Currently in Sales Intelligence, all users permissions include the ability to export to a CSV.
- 6sense staff response on RevCity, December 2025 (https://revcity.6sense.com/home/discussion/2360/si-csv-export-enhancement-notice)
The decision
6sense is appropriate for teams that can absorb manual provisioning overhead or that have a lightweight enough user base to manage JIT SSO plus post-login role promotion without significant operational drag.
Teams running frequent onboarding cycles for sales roles, or those with strict offboarding SLAs, should factor in the Q4 2026 SCIM timeline before committing to a self-service provisioning workflow. The ABM platform's lack of in-app license enforcement means over-provisioning is a real compliance risk that requires a manual audit process or CSM escalation to resolve.
If automated deprovisioning is a hard requirement today, the current architecture does not support it.
Bottom line
6sense has no SCIM and no user management API; every provisioning action is manual through Settings > User Management or dependent on JIT SSO, which only creates users on first login and cannot sync roles or handle deprovisioning.
The Primary Administrator is a single-seat root role, SI license limits are enforced in-app while ABM and CE are not, and the default role for all SSO-provisioned users is Insight User - requiring a second manual step to grant real access.
Teams should plan for ongoing admin overhead until SCIM support arrives in Q4 2026, and should establish a manual audit cadence for ABM and CE seats to avoid silent over-provisioning against contracted limits.
Automate 6sense workflows without one-off scripts
Stitchflow builds and maintains identity workflows for your exact setup. We cover every app, including the ones without APIs, and run deterministic trigger-to-report workflows with human approvals where they matter.
