Seveso.app

Seveso.app — Getting started

Updated

This guide gets a new Seveso.app tenant from “we just signed up” to “the safety team is producing structured records” in about an hour. For in-depth product documentation, see the rest of the Seveso App category.

  • Audience: site safety manager or HSE lead and an IT administrator.
  • Time: ~60 minutes.

1. Activate your tenant

  1. Sign in at ai.teks.dev with the invitation link.
  2. Confirm your tenant name (usually the legal entity that operates the Seveso establishment).
  3. Pick a data residency — Seveso.app defaults to EU and there is no non-EU option.

Seveso.app includes SAML 2.0 / OIDC SSO and SCIM 2.0 provisioning on all plans. Set this up first so user accounts come from your identity provider.

  1. Settings → Identity → Add SSO connection.
  2. Pick your provider (Entra ID, Okta, Google Workspace).
  3. Map roles: at minimum Safety Manager, Safety Engineer, Operator, Read-only Auditor.

If you cannot do SSO today, you can still invite users by email and migrate later.

3. Define the establishment

  1. Establishment → Add new.
  2. Fill in classification (lower-tier or upper-tier), competent authority, and key identifiers.
  3. Add the process units (top level — you can refine later).
  4. Upload existing key documents (Safety Report PDF, MOC log, prior MAH analyses) into Documents. Seveso.app will index them for retrieval but will not send them to any AI provider for training.

4. Decide on AI

By default, AI features are enabled for the Safety Manager and Safety Engineer roles, and disabled for Operators and Read-only Auditors.

  • To disable AI tenant-wide: Settings → AI → toggle off.
  • To pin a single provider (e.g. Mistral EU only): Settings → AI → Provider.

Read the Seveso.app AI Statement before turning AI on for production work.

5. Run your first MAH analysis

  1. Establishment → MAH → New analysis.
  2. Select the process unit.
  3. Pick Suggest scenarios (AI) to get a starting list — the AI uses only your tenant’s data, in the EU, and the list is non-binding.
  4. Review each suggestion and Accept, Edit or Reject.
  5. Link barriers to each scenario; run the Barrier reviewer (AI) to flag inconsistencies.
  6. Promote the analysis from draft to controlled when ready (requires dual sign-off if enabled).

6. Schedule the first internal audit

  1. Audits → New.
  2. Pick a template (Seveso-III internal audit ships in the library).
  3. Assign the auditor and the auditees.
  4. Closure of findings rolls into the Actions register.

7. Next steps

  • Security & data residency — share with your procurement team.
  • AI Statement — share with your DPO and your competent authority if asked.
  • Set up the monthly Safety Committee dashboard in Settings → Reports.

If you get stuck: capptions.com/contact.

Question not answered? Ask us via the contact form