Navigation
VigilbaseDocs

    Type at least two letters.

    Open Vigilbase One

    Settings

    Organisation settings in Vigilbase OS - organisation details, members, grants, policy, kill switch, notifications, retention and usage.

    Vigilbase OS is in preview. Features and connectors are still being validated with customers and may change before general availability.

    Settings holds your organisation's configuration. Open it from the sidebar or press g then s. Some sections need a permission; without it, the section says which one.

    SectionWhat it holdsPermission
    OrganisationName, slug and IDs, your access, and the danger zoneNone
    MembersMembers, roles and invitationsorg.read
    GrantsScoped grants of extra permissionsorg.read
    MFA and passkeysA link to your account security in Vigilbase IdentityNone
    PolicyThe action policypolicy.read
    Kill switchStop all action executionNone to view
    NotificationsSlack and Microsoft Teams notificationsnotifications.manage
    RetentionRetention and entitlementsbilling.read
    Usage and spendIngestion allowance, investigations, and volume and cost by connectionbilling.read

    Your access

    The Your access panel under Organisation shows what the server resolved from your role and grants: your role, whether multi-factor authentication is required and satisfied in this session, until when your step-up is fresh, your scoped grants and your permissions.

    Account security

    Your password, authenticator and passkeys belong to your Vigilbase account, not to OS. Under MFA and passkeys, choose Manage account security to open Vigilbase Identity.

    Delete the organisation

    Only an owner can delete an organisation. The Danger zone is at the bottom of Organisation.

    1. Choose Delete organisation in the Danger zone.

    2. Type the organisation's slug to confirm. Optionally enter a reason; it stays in the audit log until the purge completes.

    3. Choose Delete organisation and confirm it's you.

    The page shows the deletion's progress. When it completes, a deletion receipt with a SHA-256 hash is kept.