Skip to content

Quickstart

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

First time setting up?

If this is a new organization, complete First Steps first to configure your organization description, project context, and risk limits. This ensures Scout has the context it needs and risk quantification is unblocked.

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

Go to app.modulos.ai and sign in. Your account belongs to one organization, so you land in your workspace directly.

Questions along the way? Ask Scout

Scout, the AI assistant built into the platform, answers questions about AI governance ("What does the EU AI Act require for my system?") and about the platform itself ("Where do I attach Evidence?"). Open it from the Scout button on any project page.

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 Owner; add Editors for the day-to-day work).
  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: Complete the Control and fulfill the Requirement

  1. Change the Control's status (typically to Executed). You confirm the change with a comment, which is logged in the Control's Comments and Logs.
  2. When all Controls linked to a Requirement reach a final status, the Requirement is marked ready for review.
  3. The Requirement Owner reviews the completed Controls and marks the Requirement as Fulfilled.

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