Summary and recommendation
Bombora 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.
Bombora is a B2B intent data platform with no native SCIM provisioning and no publicly documented self-service admin console for user lifecycle management. User provisioning and deprovisioning must be handled manually through the Bombora platform UI, typically with involvement from a Bombora Customer Success Manager.
SSO via SAML 2.0 is supported for Okta and Entra ID, but authentication-only - it does not automate provisioning or deprovisioning.
Quick facts
| Admin console path | Bombora does not expose a clearly documented centralized enterprise admin-console path in publicly available docs. |
| 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 |
|---|---|---|---|---|---|
| Standard user | Bombora account-level access as documented in available public resources. | Administrative operations are not clearly documented in public sources. | Unknown / not publicly documented | Unknown / contract-specific | Role boundaries require verification in tenant-specific admin documentation. |
Permission model
- Model type: role-based
- Description: Role and permission model details for Bombora are partially documented publicly; validate exact role scopes inside tenant admin settings.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Not documented
How to add users
- Use Bombora administrative user-management settings to create or invite a user (path varies by tenant deployment).
- Assign the required role/profile and verify initial access.
Watch out for:
- No publicly documented self-service user-add workflow found. User provisioning likely requires engagement with a Bombora Customer Success Manager.
- SAML SSO is available via Okta and Entra ID, but SCIM is not supported, so automated provisioning is not available.
- All admin and user-management documentation appears to be gated behind a customer login at support.bombora.com.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | No | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: No public documentation found describing deactivation or deletion workflows. SCIM is not supported, so automated deprovisioning via an IdP is not available. Manual removal likely requires contacting Bombora support or a Customer Success Manager.
- Use Bombora admin user-management settings to suspend/deactivate the account where supported.
- Verify session access is revoked and ownership handoff steps are completed if applicable.
| Data impact | Behavior |
|---|---|
| Owned records | Not documented |
| Shared content | Not documented |
| Integrations | Not documented |
| License freed | Not documented |
Watch out for:
- No SCIM support means revoking SSO access via Okta or Entra ID does not automatically deprovision the user within Bombora.
- Manual deprovisioning process is not publicly documented.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Contracted seat | Tenant access per purchased subscription | Contract / quote-based |
- Where to check usage: Not documented
- How to identify unused seats: Not documented
- Billing notes: Bombora uses custom annual contracts. Pricing tiers include Basic Surge ($25,000–$30,000/year), Enhanced ($50,000–$100,000/year), and Full Audience ($100,000+/year). Multi-year discounts of 10–20% reported. No free trial available. Seat or user-level billing details are not publicly documented.
The cost of manual management
Because Bombora lacks SCIM and self-service admin controls, every app in your stack that relies on automated provisioning will not extend to Bombora - each joiner, mover, or leaver event requires a manual step.
Account changes routed through a CSM introduce lag that creates real offboarding risk, particularly for a platform holding access to sensitive B2B intent data. Annual contracts with no free trial mean seat sprawl is difficult to audit without direct vendor engagement.
What IT admins are saying
G2 reviewers consistently flag that user and account changes require CSM engagement rather than self-service controls. No public help center documentation on roles, permissions, or seat management is available without a customer login - all such content appears gated.
The absence of SCIM means Okta and Entra ID integrations stop at SSO session control; deprovisioning is entirely manual.
Common complaints:
- No publicly accessible help center articles on user roles, permissions, or seat management were found; all such documentation appears to be gated behind a customer login.
- G2 reviewers indicate that account and user changes typically require engagement with a Bombora Customer Success Manager rather than self-service admin controls.
- No SCIM provisioning is available, meaning automated user lifecycle management via Okta or Entra ID is not supported; SSO is available via SAML but deprovisioning must be handled manually.
- Lack of public documentation on identity management and admin console functionality makes it difficult to evaluate or audit user access without direct vendor engagement.
The decision
Bombora is appropriate for teams that can absorb manual provisioning overhead and have an active CSM relationship to route access changes through. It is a poor fit for organizations requiring automated joiner/leaver workflows across every app without exception.
If your identity governance program mandates SCIM or automated deprovisioning, Bombora's current architecture will require a documented exception or compensating control.
Bottom line
Bombora offers no SCIM provisioning and no self-service admin documentation, making it one of the more operationally demanding tools to govern in an enterprise stack.
Every user lifecycle event - onboarding, role change, or offboarding - requires manual action through the platform UI or CSM escalation. Teams with strict identity governance requirements should plan for compensating controls and factor CSM response time into their offboarding SLAs.
Automate Bombora 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.
