Docs

Appearance

Organization Admin Path ​

Set up the organization layer: onboarding, roles, shared settings, and the access model that lets teams run governance work safely.

Outcome ​

You leave this path with:

  • organization settings configured (currency, language, profile)
  • users invited with appropriate organization and project roles
  • risk manager responsibilities assigned where needed
  • a clear separation of duties: Editors implement, Requirement Owners review and fulfill, Viewers observe

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

Path at a glance ​

Step 1: Set organization defaults ​

Goal: ensure governance and reporting are consistent across projects.

Where in Modulos

  • Organization → Settings

Do this

  • Set the default currency and language.
  • Fill out the organization profile (helps provide context across the platform).

You’re done when

  • organization defaults match how your organization operates and reports

Step 2: Onboard users and assign organization roles ​

Goal: give people the right org-level responsibilities without over-privileging.

Where in Modulos

  • Organization → Users to manage invites and organization roles

Do this

  • Invite the initial team (product, compliance, engineering, internal audit).
  • Assign organization roles:
    • Organization Admin for a small set of trusted administrators
    • Organization Risk Manager for the people maintaining risk budgets and taxonomy
    • Organization Member for baseline access

You’re done when

  • the right people can manage org settings and shared libraries

Step 3: Assign project roles and establish ownership ​

Goal: ensure each project has clear accountability and separation of duties.

Where in Modulos

  • Project → Settings → User access to assign project roles per project

Do this

  • Ensure each project has at least one Owner.
  • Assign Editors to the people implementing Controls and attaching Evidence.
  • Assign Viewers for read-only access where needed.

You’re done when

  • ownership and review responsibilities are explicit in every active project

Step 4: Establish guardrails for internal audit readiness ​

Goal: make governance work predictable and reviewable.

Where in Modulos

  • Project objects → Comments and Logs for traceability
  • Project → Requirements, Project → Controls, and Project → Dashboard → Export for project-level readiness

Do this

  • Encourage teams to record clear status-change comments on Controls and to review Requirements once their linked Controls are final.
  • Ensure internal reviewers can trace Requirements → Controls → Evidence.
  • Confirm exports and audit trail views are accessible to the right roles.

You’re done when

  • internal reviewers can validate work without needing tribal knowledge or backchannels

Next handoff ​

Compliance Lead

Drive the governance backlog to evidence-backed execution and review

Risk Manager

Maintain taxonomy and budgets so projects can quantify risk consistently

Engineer & Integrations

Connect Sources and Connectors so work is grounded in real artifacts