Configure

Admin and Access Review

Technical administration for tenant operators, plus the platform Access Review queue for Super Admins approving private onboarding. These are different jobs with different roles.

/admin . Technical admin

Includes impact overview, member access control, RBAC matrix, company settings (verbosity, security stack context, settings that affect Command Center behavior), authentication posture readout (NextAuth, Entra when configured, SCIM called out as roadmap), and endpoint ingest for map correlation.

Endpoint import accepts CSV/JSON with hostname, IP, and geo fields so Infrastructure Map can place company assets and correlate malicious contacts within a configured radius. Without inventory, the map cannot show honest company endpoints.

/admin/applications . Access Review

Super Admin only. Lists pending onboarding applications with an applicant dossier (identity, company, stack, use cases, timeline). Approve or reject with optional note. Approval provisions tenant workspace membership and attempts credential email when mail is configured. Completed items leave the pending queue.

This role intentionally cannot open tenant Incidents, Hunt Ledger, Automation, or telemetry surfaces. Platform review and tenant operations stay segregated so a platform operator is not silently a tenant SOC admin.

Local development note

Local .env may define AUTH_USERNAME / AUTH_PASSWORD and LOCAL_OPERATOR_ROLE for UI work. Default local operator role should be admin for tenant console work. Setting LOCAL_OPERATOR_ROLE=super_admin confines the session to Access Review by design. That path is for development and platform testing — not a production identity model.

Privacy controls

Your visit should be as controlled as your telemetry.

We use necessary cookies to keep the site working. Optional analytics help us understand which product pages are useful. Marketing cookies stay off unless you allow them.