Skip to content

Quickstart ​

Register your first AI System, complete one Control, and export a snapshot for an audit.

First time setup?

If your organization is new, do First Steps first. There you write the organization description, give roles, and set the risk limits. Then Scout has the context of your organization.

Prerequisites ​

  • A Modulos account
  • Access to the workspace of your organization
  • Governance is on for your organization. Without governance, Modulos does not show frameworks, Controls, or Export.

All users of an organization can register AI Systems.

If you join a team

If your team has AI Systems, you can start at Step 3 in an AI System where you are an Owner or an Editor.

Step 1: Sign in ​

  1. Go to app.modulos.ai and select Login.
  2. Sign in with your account.
  3. If Modulos shows the Privacy & Policy dialog, select Accept. Cancel signs you out.

Your account is part of one organization. Modulos opens the home page of that organization, with the Controls that you own and your AI Systems. If you cannot sign in, see I cannot sign in.

Questions? Ask Scout

Scout is the AI assistant of the platform. It answers questions about AI governance and about the platform. Examples are "What does the EU AI Act require for my system?" and "Where do I attach Evidence?" To open Scout, click the Scout button in the page header. When Scout is on for your organization, the button is on every page.

Step 2: Register your first AI System ​

  1. In the sidebar, open AI Registry.
  2. Click New AI System.
  3. Type a name, add a second Owner if you can, and click Create.
  4. In the wizard, type the Intended Purpose: what the system does, who uses it, and what it decides or makes.
  5. Select the Current State: Proposed, Pilot, or Already in use.
  6. Write a short description of the technology and the deployment, and click Continue.
  7. Select the user groups that use the system.
  8. Answer if the EU AI Act applies. For Yes, set Product Category and Role.
  9. Connect Sources or upload Evidence if you have them, and click Continue.
  10. Select a minimum of one framework. The wizard selects the EU AI Act framework only for a Yes answer with a classification. You can add more frameworks after this step.
  11. Click Create AI System.

If you do not know which Framework to pick, see the Frameworks Overview and the Frameworks Comparison.

Registration wizard step AI System & Details with the Intended Purpose and Current State fields and the guidance panel.

Step 1 of the registration wizard: Intended Purpose and Current State are required.

  1. Intended Purpose What the system does, who uses it, and what it decides or makes.
  2. Current State Proposed, Pilot, or Already in use.
  3. Continue Saves the step and opens the next step.

Modulos sends the AI System for approval. Its registration status changes to Pending, and its Overview opens. An Organization Admin or an Organization Registration Manager approves or rejects it. While the AI System is Pending, you can continue with the next steps. See Registration approval.

Then add Editors for the daily work in AI System → Settings → User Access.

Best practice

Keep your first AI System narrow: one deployed system or one use case. From a small scope, it is easier to make governance patterns that you can use again.

Learn more: Register an AI System

Step 3: Open a Control and set its Owner ​

  1. In your AI System, go to Requirements.
  2. Open one Requirement that clearly applies to your system.
  3. Set the Owner of the Requirement to your name.
  4. Open a mapped Control with the status Not Executed.
  5. If the Control has a different Owner, set the Owner of the Control to your name.

Only an AI System Owner can set the Owner of a Requirement. If you are an Editor, an AI System Owner must do step 3 for you. The Owner of a mapped Requirement can set the Owner of a Control. When you become the Owner of the Requirement, Modulos also makes you the Owner of each mapped Control that has no Owner. See Requirements.

Use Scout during the quickstart

If Scout is on for your organization, use it for this quickstart. Scout knows the context of your AI System: its Controls, Requirements, and Evidence. It can also use the Connectors (user accounts) and the Sources (service accounts of the AI System) that you connect.

Examples of 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 AI System could support this Control, and what's missing?"

Learn more: Controls

Step 4: Add a report and attach Evidence ​

  1. Open the Report tab of the Control.
  2. Write a short Control report about how your organization does the Control. For a first version, one to three paragraphs are sufficient.
  3. Click Submit. Without this step, Modulos does not keep the report.
  4. Open the Control tab again and find the Evidence section.
  5. To add new Evidence, click Upload New Evidence. To use an item from the Evidence Library, click Select Evidence.
  6. Make sure that the Evidence tells what it is, what it shows, and for which period.

AI System Owners and Editors, and users with access to all AI Systems, can add Evidence. Viewers cannot. Examples of Evidence are a policy, a screenshot, an export, or a test result.

When the Evidence Agent is on for your organization, it can suggest a name, a description, and the Controls for a new Evidence item. See Evidence Agent.

Use Evidence that an auditor can accept

Use Evidence that stays the same and that you can make again. Examples are documents with versions, system exports, and signed policies. Do not use screenshots without context.

Learn more: Evidence

Step 5: Complete the Control and the Requirement ​

  1. Change the status of the Control to Executed. The Owner of the Control or an Owner of a mapped Requirement can change the status. After this change, you cannot edit the report.
  2. When all Controls of a Requirement are Executed, Out of scope, or Archived, the Requirement shows "Requirement is ready to be reviewed."
  3. The Requirement Owner examines the Controls and selects Mark as Fulfilled.
Control page with the open Status select (Not Executed, Executed, Out of Scope), the mapped Requirements, and one Evidence item.

Set the status of a Control on its page.

  1. Status Set Executed when the Control is done. No comment is necessary for this change.
  2. Mapped Requirement(s) The Owner of the Control and the Owners of these Requirements can change the status.
  3. Evidence The Evidence that supports the Control.
Requirement with the banner Requirement is ready to be reviewed, the Mark as Fulfilled button, and the Comments and Logs history.

When all mapped Controls have a final status, the Requirement Owner can mark the Requirement as Fulfilled.

  1. Requirement is ready to be reviewed. Shows that all mapped Controls have a final status.
  2. Mark as Fulfilled Records the fulfillment decision of the Requirement Owner.
  3. Comments and Logs Shows when the Requirement became ready for review.
  4. Status Stays Not Fulfilled until the Requirement Owner marks it as Fulfilled.

Learn more: Reviews & Statuses

Step 6: Export an audit snapshot ​

  1. Open the dashboard of the AI System.
  2. Click More actions, the button with three dots at the top right.
  3. Click Export. Modulos makes a PDF of the AI System that you can give to your team or to auditors.

Learn more: Reports & Exports

Next steps ​