Skip to content

Organization Admin Path ​

This path sets up the organization in Modulos: the settings, the users, the roles, and the division of duties.

Outcome ​

After this path, you have:

  • the organization settings: the currency, the language, and the description
  • users with the correct organization roles and AI System roles
  • the roles with access to all AI Systems only where they are necessary
  • a clear division of duties: Editors do the work, Requirement Owners examine it and mark Requirements Fulfilled, and Viewers read the work and add comments, but cannot change items

Time to first value: 30–60 minutes
Prerequisites: you are an Organization Admin

Path at a glance ​

  1. Set the organization settings Set the currency, the language, and the description.
  2. Invite users Invite users and give organization roles.
  3. Give AI System roles Make sure that each AI System has Owners, Editors, and Viewers.
  4. Set guardrails Prepare the AI Systems for internal audits.

Step 1: Set organization defaults ​

Goal: use the same settings for all AI Systems of the organization.

Where in Modulos

  • Organization → Settings → General

Do this

  • Set the Organization Currency.
  • Set the Default Organization Language.
  • Write the Organization Description.
  • Select Save.

Modulos uses the currency for all risk values and risk limits. The language is the first language of each invited user and of each new AI System. Scout and the Risk Agent read the description as context. See Organization Settings.

You are done when

  • the settings agree with how your organization works and reports

Step 2: Invite users and give organization roles ​

Goal: give each person the organization role that the person needs, and no more.

Where in Modulos

  • Organization → User Management to invite users and give organization roles

Do this

  • Select New User and invite the first team, for example compliance, engineering, and internal audit.
  • Give Admin only to a small group of trusted administrators.
  • Give Risk Manager to the persons who keep the risk taxonomy and the risk limits.
  • Give Policy Manager to the persons who own the Policies in Policy Center.
  • Give Registration Manager to the persons who make the approval decision on new AI Systems.

Each user is an Organization Member. Organization Admins, Organization Risk Managers, and Organization Policy Managers have all the rights of the AI System roles in each AI System of the organization. Give these roles carefully. Each active user and each open invitation uses one of the Seats that Organization → Usage shows. See User Management.

You are done when

  • the correct persons can change the organization settings, the users, the risk configuration, and the Policies

Step 3: Give AI System roles and select owners ​

Goal: give each AI System clear owners and a division of duties.

Where in Modulos

  • AI System → Settings → User Access to give the AI System roles of one AI System

Do this

  • Make sure that each AI System has one or more Owners.
  • Select Add User to the AI System to add a user.
  • Give the Editor role to the persons who do the Controls and attach Evidence.
  • Give the Viewer role to the persons who must see the work but not change it, for example internal auditors.
  • Select the Requirement Owners before the Control Owners. Only the owner of a mapped Requirement can select a Control Owner.

An AI System Owner selects the Requirement Owners. A Requirement Owner or a Control Owner must be an AI System Owner or an Editor. Modulos makes a new Requirement Owner also the Owner of each mapped Control that has no Owner. See Requirements.

You are done when

  • each active AI System has Owners, and the Owners of its Requirements and Controls are clear

Step 4: Set guardrails for internal audit readiness ​

Goal: make the governance work predictable and easy to examine.

Where in Modulos

  • Comments and Logs of each Control, Requirement, and Asset, and of the Overview of each AI System, for the history of the work
  • AI System → Graph for the links from Requirements to Controls and tests
  • AI System → Dashboard → More actions → Export for a PDF of one AI System

Do this

  • Tell the teams to write the cause of each status change in a comment on the Control.
  • Make sure that Requirement Owners examine the Controls and their Evidence before they select Mark as Fulfilled.
  • Give internal auditors the Viewer role in each AI System that they examine.

Each member of an AI System can see its history and export its PDF, and Viewers can too. See Audit Trail and Reports & Exports.

You are done when

  • internal auditors can examine the work without help from the team

Next handoff ​