PlatformPlatform architectureProduct tourProduct graphRisk intelligenceContinuous governanceEvidence & auditDeploymentIntegrationsExecutive view
BOM SuiteSBOMCBOMQBOMAIBOMHBOMBOM Governance
SolutionsSecurityComplianceSupply chain riskQuantum readinessAI governanceDigital trust
ComplianceCERT-InRBISEBI / CSCRFMeitYNISTEU CRAEU AI ActCERT-In SBOM guide
IndustriesBanking & Financial ServicesGovernment & Public SectorDefence & Critical InfrastructureHealthcareIndian enterprises
ResourcesResource centreSBOM resourcesCBOM resourcesQBOM resourcesAIBOM resourcesHBOM resourcesProgramme & regulationBlogVulnerability disclosuresResearch
CompanyAboutSecurity & trustContact
Request a DemoTalk to an expert
DocumentationPlatform guideUpdated October 2026

Notifications, settings and access control

Route alerts, create users and roles, connect SSO, and manage branding and CI tokens.

Notifications and alerts

Notifications & Alerts collects live alerts from vulnerability scans, quantum risk and SBOM activity. Tiles show Unread, Total and Groups, with a Machines filter. The Notification Feed filters All, Unread, Vulns, Scans and Quantum; each alert shows severity, category, machine and age, with Mark all read and Clear read.

Notification Groups hold recipients (full name, designation, email, phone and role: Admin, Editor, Viewer, Read-Only), entered by hand and separate from platform accounts. Send Alert is a three-step wizard: pick a machine and run, preview their vulnerabilities, then send. A run whose SBOMs are still Pending shows No SBOM applications found.

Access control

Settings opens from the bottom of the sidebar. Access Control is one page with four tabs:

  • Users: list, Create User (username, email, name, password, temporary-password flag, enabled flag, roles), View Roles, Edit, Delete.
  • Privileges: 46 system-defined privileges grouped by function: per-BOM-type access, page access, and actions such as run security scan, download BOMs, export CSV and manage CI tokens.
  • Roles: composite roles that bundle privileges (for example bom-admin, Platform Administrator, ApplicationViewer). Create Role drags privileges from Available to Assigned.
  • Identity Providers: SSO providers alongside username and password (for example Microsoft Entra ID over OIDC, Google, GitHub, Custom OIDC, SAML 2.0). Sign-in runs on Keycloak.

As an example, ApplicationViewer holds 14 page-access privileges and no action privileges, so its users can look but not scan, upload, download or delete.

Branding and CI tokens

  • Company Logo: PNG, JPEG or WebP up to 2 MB, shown in the header and on every downloaded BOM report.
  • CI Tokens: generate tokens for CI pipelines. Pick the user, enter the CI username (it must match the CI actor on GitHub or GitLab), choose validity (30 days to 1 year) and an optional label. Admins grant or remove token access per user and can revoke tokens from the history.
  • Font & Size: application-wide font and text size.
  • Sign Out.
See it on your own stack.Register an asset, run a scan and read your first BOM in minutes.
Request a Demo