Docs

Appearance

Quickstart ​

Create your first project, complete one control, and generate an audit-ready snapshot.

Prerequisites ​

  • A Modulos account
  • Access to an organization workspace
  • Permission to create projects (or an existing project you can edit)

If you’re joining an existing team

If you don’t have permission to create a project, start at Step 3 inside an existing project.

Step 1: Log in ​

  1. Go to app.modulos.ai and sign in.
  2. Select your organization (if prompted).

Step 2: Create your first project ​

  1. In the sidebar, open Projects.
  2. Click New Project.
  3. Choose AI application (recommended for a first quickstart).
  4. Set a clear project name and short description (what system, where it runs, who uses it).
  5. Add project members and roles (at minimum: an editor and a reviewer/owner).
  6. Select one or more frameworks to apply (you can start with a single framework and expand later).

Best practice

Keep your first project narrow (one AI system / one use case). It’s easier to build repeatable governance patterns from a focused baseline.

Learn more: Projects

Step 3: Open a control and assign ownership ​

  1. In your project, go to Controls (or start from Requirements and open a mapped control).
  2. Pick one control that is clearly applicable to your system.
  3. Assign an owner (typically yourself for the quickstart).

Use Scout as you go (recommended)

If Scout is enabled for your organization, use it to accelerate this quickstart. Scout can reference your project context (controls, requirements, evidence) and can use connected connectors (user accounts) and sources (project service accounts) when available.

Example prompts:

  • “Summarize what this control requires and list the concrete implementation steps for our system.”
  • “Draft an initial control report outline and suggest the evidence we should attach.”
  • “What existing evidence in this project could support this control, and what’s missing?”

Learn more: Controls

Step 4: Add a report and attach evidence ​

  1. Write a short control report describing how your organization implements the control (1–3 paragraphs is enough for a first pass).
  2. Upload or link evidence that supports the report (policy, screenshot, export, log sample, test result).
  3. Ensure the evidence clearly answers: what it is, what it proves, and for which timeframe.

Evidence should be audit-ready

Prefer evidence that is stable and reproducible (versioned documents, system exports, signed policies) over informal screenshots without context.

Learn more: Evidence

Step 5: Request review and complete the control ​

  1. Request a status change for the control (typically to Executed).
  2. A reviewer (or project owner) approves the change.
  3. The control is now in a final state and becomes part of your audit trail.

Learn more: Reviews & Statuses

Step 6: Export an audit snapshot ​

  1. Open the project dashboard.
  2. Export a PDF/project snapshot to share internally or with auditors.

Learn more: Reports & Exports

Next steps ​

Core Concepts10 min

Learn the platform model and workflows

Risk Quantification

Quantify risk in monetary terms

Testing

Connect sources and track results over time

Scout

Ask questions grounded in your project context

Frameworks Overview

Apply EU AI Act, ISO 42001, NIST AI RMF, and more

From Zero to Audit-Ready

Full end-to-end workflow walkthrough