Organization Administrator Onboarding Guide
A step-by-step walkthrough of the 12 setup tasks every new Organization Administrator completes. Mirrors the Getting Started checklist at Admin → Getting Started inside the platform, plus optional setup for organizations on Microsoft 365.
Who this guide is for
Organization Administrators (the OrgAdmin role) on a newly provisioned RAIC tenant. Each setup task takes two to five minutes, and the full sequence runs in well under an hour. WorkflowAdmins, Reviewers, and other roles will find the per-module documentation in the sidebar more useful for their day-to-day tasks.
You can work through the checklist on Admin → Getting Started, or, if your organization has installed Ask RAIC in Microsoft 365 Copilot, ask it to run the startup checklist. Both read the same checklist, so progress shows in both.
Step 1. Set up allowed email domains
/admin/org-settingsPurpose
Restrict who can submit AI use case intake requests to people on your corporate email domain(s). Until at least one domain is configured, you cannot invite team members.
What to do
- Navigate to Admin → Organization Settings.
- Under "Allowed Email Domains", add each domain (e.g. acme.com).
- Save. Multiple domains are supported for multi-brand organizations.
Complete when
At least one allowed email domain is saved on the org.
Step 2. Set up email deliverability
/admin/email-deliverabilityPurpose
RAIC sends approval requests, attestation reminders and alerts by email. Microsoft 365 and similar platforms often quarantine mail from a new sending domain without telling anyone, so a one-time mail flow rule from your IT administrator keeps those messages reaching people.
What to do
- Navigate to Admin → Email Deliverability.
- Record your IT contact, mail platform, and whether a third-party email gateway is in use.
- Click Download IT instructions, or Email instructions to IT contact to send them the branded instructions (you are copied).
- Click Send test notification and answer whether it arrived.
- Tick the confirmation once IT reports the rule is in place.
Complete when
The step shows Confirmed, or Skipped with a stated reason (skipping keeps a reminder on the dashboard until it is confirmed).
Step 3. Invite team members
/admin/usersPurpose
Add the colleagues who will register AI systems, submit use cases, approve workflows, or run reports. Roles drive what each person can see and do.
What to do
- Navigate to Admin → Users.
- Click "Invite User", enter their email and role (OrgAdmin, WorkflowAdmin, Reviewer, Submitter, etc.).
- Optional: bulk-invite via the CSV template.
- Invitees receive a branded email with a one-time setup link.
Complete when
At least one additional active user exists in your organization.
Step 4. Set where you operate
/admin/operating-locationsPurpose
Record where your organization operates, so Regulatory Intelligence applies a state law only where you operate, federal law if you operate anywhere in the United States, and EU law if you operate in the European Union.
What to do
- Navigate to Admin → Where We Operate.
- Tick each region and country you operate in. The European Union is one choice that covers every member state.
- For the United States, click "All 50 states" or tick each state you operate in. DC and US territories are listed separately.
- Click "Save", or "Save and confirm" to confirm your regulatory profile.
Complete when
Your regulatory profile lists at least one place where you operate.
Step 5. Configure System Register lookups
/admin/org-tablesPurpose
Customize the dropdown values used when registering AI systems (departments, vendors, model families, deployment patterns, etc.) so they match your taxonomy.
What to do
- Navigate to Admin → System Register.
- Review the seeded lookup tables and add, hide, or rename values to match your taxonomy.
- Mark unused lookups inactive instead of deleting them.
Complete when
At least one active lookup configuration row exists for your org.
Step 6. Configure governance designations
/admin/org-settingsPurpose
Tell the platform who holds each governance role (CISO, CRO, CAIO, DPO, Privacy Officer, etc.). These designations drive who is auto-routed approvals across staged workflows.
What to do
- Navigate to Admin → Organization Settings → Governance Designations.
- Assign at least one named individual to each role you use.
- Roles you don't use can be left blank. Only assigned roles appear as approver options.
Complete when
At least one governance designation has a named individual.
Step 7. Configure use case register settings
/admin/use-case-registerPurpose
Set defaults for use case intake: starting risk tier, review cadence, the notification email for new submissions, and which approval stages apply.
What to do
- Navigate to Admin → Use Case Register.
- Set default risk tier and review cadence.
- Set the intake notification email so the right people get pinged on every new submission.
Complete when
Use case register settings are saved for your org.
Step 8. Create or receive a use case intake
/airep/use-case-intakePurpose
Capture the business use case that consumes the AI system: who, what, why, decisions made, populations affected. Use cases are the unit of risk assessment, EU AI Act scoping, and ISO 42001 impact assessments.
What to do
- Navigate to Use Cases → New Use Case (or share the public intake URL with the requesting business unit).
- Complete the 5-step form covering business context, data, deployment, risk, and stakeholders.
- Submit. The use case gets ID RC-{DEPT}-{###} and enters the staged approval workflow.
Complete when
At least one use case exists in your Use Case Register.
Step 9. Register your first AI system
/intakePurpose
Add an AI system to the registry: vendor model, internal build, agentic workflow, copilot, etc. The registry is the foundation that every other module (controls, risks, monitoring, audits) hangs off.
What to do
- Navigate to System Register → New System (or use the public intake URL printed on /admin/integrations).
- Complete the 5-step intake form. The system is auto-assigned an ID like AI-{ORG_SLUG}-YYYY-###.
- Submit. The system enters the staged approval workflow.
Complete when
At least one AI system exists in your registry.
Step 10. Define your first AI control
/controls/newPurpose
Document a control that mitigates AI risk: human-in-the-loop, output review, bias monitoring, prompt logging, vendor SLA, etc. Controls are testable and can be linked to systems, use cases, risks, and frameworks.
What to do
- Navigate to Controls → New Control.
- Complete the 8-step wizard (purpose, design, owner, testing cadence, evidence requirements, framework mappings).
- Submit. The control enters the 7-stage approval workflow.
Complete when
At least one control exists in your control library.
Step 11. Configure alert & review cadence
/admin/org-settingsPurpose
Tell the platform how far ahead to warn you about expiring approvals, overdue reviews, and lapsing evidence. The default is 30 days; tune per your operating tempo.
What to do
- Navigate to Admin → Organization Settings → Alert Configuration.
- Set the scheduling warning window (default 30 days).
- Optional: set per-record overrides on individual reviews/policies/datasets.
Complete when
Org alert configuration row is saved.
Step 12. Upload your first AI policy
/governancePurpose
Publish at least one AI policy (Acceptable Use, Generative AI, AI Agent Acceptable Use, Vendor AI, etc.) so users have something to attest to and so the AI Policy Library is not empty when auditors arrive.
What to do
- Navigate to Governance → AI Policy Library.
- Upload an existing policy OR generate a draft with Aslan AI (Suite package).
- Publish. Published policies are eligible for attestation campaigns.
Complete when
At least one policy exists in your AI Policy Library.
Optional: organizations on the Microsoft stack
If your organization uses Microsoft 365 and Microsoft Entra ID, these steps connect RAIC to your tenant without an app registration of your own and bring RAIC into Microsoft 365 Copilot. Do them in order.
1. Connect Microsoft through the RAIC agent
RAIC reads your Microsoft 365 tenant to discover AI apps, agents and non-human identities. With the RAIC agent you do not create an app registration or a secret of your own: RAIC adds an agent identity named RAIC Governance Agent to your tenant and lists it in your Agent 365 registry. A Global Administrator approves 14 Microsoft Graph application permissions: 11 read-only permissions for discovery, and 3 that let RAIC manage the agent itself (AgentIdentity.CreateAsManager, User.ReadBasic.All, AgentRegistration.ReadWrite.All).
- In RAIC, go to Admin → Integrations → RAIC agent in Microsoft Entra.
- Click Sign in with Microsoft and sign in with a work account in your tenant. That account becomes the agent's sponsor. If Microsoft is already connected for your organization, click Connect instead.
- A Global Administrator or Privileged Role Administrator approves the RAIC Governance Agent on Microsoft's page. If that is someone else, click Copy approval link and send it to them; the link works for 7 days and they need no RAIC account.
- When the card shows Identity created, click Copy registration script. A Global Administrator runs it in PowerShell 7 and pastes the Registration ID it prints back into the card.
- The card shows Connected. Click Test Connection in the Discovery app box to confirm RAIC signs in as the agent.
Full steps, permissions and troubleshooting: the RAIC Agent Registration Guide, in RAIC under Admin → Integrations → RAIC Agent Registration Guide.
2. Install Ask RAIC from your organization's app catalog
Ask RAIC is RAIC's agent in Microsoft 365 Copilot. Your Teams administrator adds the RAIC app package to your organization's app catalog, and a Global Administrator or AI Administrator deploys Ask RAIC to people. Use version 1.1.1 or later: it lets people from any Microsoft 365 tenant sign in to RAIC. Each person who uses it needs a Microsoft 365 Copilot license (or Copilot pay-as-you-go for agents) and a RAIC account.
- Download the current RAIC app package (.zip) and the RAIC Teams App Install Guide in RAIC under Admin → Integrations → RAIC app for Microsoft Teams and Copilot.
- A Teams Administrator uploads it in the Teams admin center under Teams apps → Manage apps → Upload new app and checks that RAIC is Unblocked. Your MSP partner cannot do this through GDAP; they need an account in your tenant.
- A few hours later, a Global Administrator or AI Administrator opens the Microsoft 365 admin center, goes to Agents → All agents → Ask RAIC and clicks Deploy, choosing who gets it.
- People open Microsoft 365 Copilot, pick Ask RAIC, ask a question and sign in to RAIC the first time.
Full steps, permissions and troubleshooting: the RAIC Teams App Install Guide, in RAIC under Admin → Integrations → RAIC app for Microsoft Teams and Copilot.
3. Set the MCP Scope policy to Read + Write
Ask RAIC reaches your RAIC data through the RAIC MCP server. The Scope policy starts at Read only, so Ask RAIC can answer questions but cannot change anything. To let Ask RAIC complete setup steps with you (the next section) and make other changes people approve, set it to Read + Write. Each person can still only change what their RAIC role allows.
- In RAIC, go to Admin → Integrations → MCP Server.
- Check that Enable MCP access for this organization is on.
- Set Scope policy to Read + Write.
- When a person first signs in from Ask RAIC, RAIC's consent screen lists what Ask RAIC may do. Write permissions stay off unless the person ticks them, so tick them to let Ask RAIC make changes.
4. Run the startup checklist in Ask RAIC
As an Organization Administrator, you can work through the Getting Started checklist in chat instead of on each admin page. Ask RAIC reads the same checklist as Admin → Getting Started, shows which steps are done, and takes the rest one at a time.
- In Microsoft 365 Copilot, open Ask RAIC and choose the Startup checklist conversation starter, or type "Run the startup checklist for our organization."
- For each step, Ask RAIC shows the current value, asks what to set, previews the change and saves it once you confirm. You can skip a step and come back to it.
- Inviting team members always stays in RAIC: invite people under Admin → Users.
- Your first use case, first AI system and first control are done in RAIC. Ask RAIC gives you the page to open.
- Back in RAIC, Admin → Getting Started shows the same progress, because both read the same checklist.
Next steps
Once you've completed the setup tasks, explore the per-module documentation in the sidebar (AI Use Cases, AI Systems, Controls, Reports & Analytics) for deeper guidance on the day-to-day workflows.
