Enterprise onboarding
Set up a SearchIn team with SSO, MFA, roles, provider controls, and audit export.
Share this guide with your security or IT team when moving investigations onto an OSINTverse company workspace.
What you get
A shared wallet, role-based access, optional company SSO and authenticator MFA, provider allowlists, spend caps, and searchable audit history. Personal accounts stay separate until you join a team.
Before you start
You need an OSINTverse account. One owner creates the team; everyone else joins by invite.
- Sign in at osintverse.com/login
- Open Dashboard → Team
- Create a team and switch into it (header workspace switcher)
Roles
Owners and admins invite people by email. Choose a role that matches the job:
| Role | Can search | Can bill | Can invite | Can manage SSO / controls | Can export audit |
|---|---|---|---|---|---|
| Owner | Yes | Yes | Yes | Yes | Yes (with queries) |
| Admin | Yes | Yes | Yes | Yes | Yes (with queries) |
| Member | Yes | — | — | — | View |
| Analyst | Yes | — | — | — | View |
| Billing | — | Yes | — | — | View |
| Auditor | — | — | — | — | Export (no query text) |
Typical setup: one owner, one customer admin, analysts for investigators, billing for finance, auditor for compliance.
Company SSO (optional)
On Team → Enterprise → Company SSO (OIDC).
Ask your identity provider admin for:
- Work email domain (for example
company.com) - OIDC issuer URL
- Client ID and client secret
Register this redirect URI in Okta, Entra ID, Google Workspace, or similar (use your chosen provider ID, for example okta-acme):
https://osintverse.com/api/auth/sso/callback/{providerId}Then fill in the form on Team and register the provider.
Sign-in: /login → Company SSO → enter a work email on that domain → continue at your IdP.
Access controls (optional)
Same Enterprise section:
- Require company SSO — magic-link sign-in is blocked for that domain and team members; use Company SSO only.
- Require authenticator MFA — people must enable an authenticator app under Settings before they can search.
- Allowed providers — limit which SearchIn sources the team can use.
- Monthly spend cap — stop team searches when UTC monthly spend hits the cap.
Turn on SSO enforcement only after at least one admin has signed in successfully with SSO.
Billing and API keys
- Switch to the team workspace.
- Billing — top up the shared wallet (owners, admins, billing).
- API keys — create keys while the team is selected so they bill the team.
API automation is not blocked by MFA. Human search in the UI is.
Audit export
On Searches, auditors and admins can export search history as CSV. Owners and admins can optionally include query text. Activity shows the same charges mixed with top-ups so you can track the wallet.