---
title: "AI CTRL Enablement Sessions"
slug: "ai-ctrl-enablement-sessions"
updated: 2026-08-21T18:56:56Z
published: 2026-08-21T18:56:56Z
canonical: "kb.expedient.com/ai-ctrl-enablement-sessions"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.expedient.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AI CTRL Enablement Sessions

## AI CTRL Enablement Sessions: Who Should Attend

Onboarding includes three enablement sessions, each focused on a different part of your platform rollout. The right people in the room make the difference between a productive session and one that needs to be repeated.

## Session 1: Admin Enablement

Covers platform administration: user access and permissions, single sign-on (SSO) integration, security settings, and initial setup decisions that affect the entire organization.

**Who needs to be there:**

| Role | Why they're needed |
| --- | --- |
| Platform Administrator | Manages the platform day-to-day going forward. Needs to be hands-on for this session, not just observing. |
| IT/Identity Lead (owns Azure AD, Okta, or your SSO provider) | AI CTRL authenticates through your existing SSO. Without this person, login configuration cannot be completed during the call. |

**Who's helpful to include:**

- A security team member, if your organization requires security sign-off on user permission defaults.
- Your help desk lead, so they know what to expect from day-one user questions.

**Who doesn't need to attend the full session:** Executive sponsors are welcome to join the first 10–15 minutes for context, but the technical configuration work doesn't require their ongoing presence.

## Session 2: Workspace Enablement

Covers hands-on setup of your first custom AI assistant, along with knowledge bases, prompt templates, and suggested prompts your team will use daily.

**Who needs to be there:**

| Role | Why they're needed |
| --- | --- |
| Platform Administrator (from Session 1) | Certain settings from the Admin session must already be in place for this session to run smoothly. |
| Department Champion(s) — the people who will actually own and use the AI assistants being built (e.g., someone from HR, IT Support, or Sales) | This is a working build session, not a demo. If the people who'll use the tools aren't present, the build can't be tailored to their actual workflows. |

**Who's helpful to include:**

- One representative per department if you're standing up knowledge bases for multiple teams (HR, Sales, Legal, Product, etc.) — each is best positioned to identify what content matters most.
- Whoever is leading internal adoption or communication about the rollout.

> If more than 2–3 departments want knowledge bases or agents built, split this into follow-up sessions per department rather than covering everyone at once.

## Session 3: Compliance Enablement

Covers data retention policies, audit logging, data loss prevention (DLP) controls, and how the platform meets your industry's regulatory requirements.

**Who needs to be there:**

| Role | Why they're needed |
| --- | --- |
| CISO or Security Lead | Approves how access controls and audit logging are configured. |
| Compliance Officer or Legal Counsel | Confirms that retention periods and data handling policies meet your regulatory obligations (e.g., HIPAA, PCI, SOC 2, or industry-specific requirements). |

**Who's helpful to include:**

- Your Platform Administrator, so any settings agreed to in this session can be configured on the spot rather than in a follow-up.
- A data privacy officer, if you handle regulated personal data.
- A risk/audit team member, if your organization has a formal governance function.

**Industry-specific note:** If your organization has sector-specific requirements (e.g., OSHA recordkeeping, subcontractor data protection in construction, or patient data in healthcare), flag this in advance so the right subject-matter expertise is on the call and you've identified the right internal stakeholder.

## Quick Reference

| Session | Must attend | Should attend |
| --- | --- | --- |
| Admin | Platform Administrator, IT/Identity Lead | Security team member, Help desk lead |
| Workspace | Platform Administrator, Department Champion(s) | Additional department reps, Adoption lead |
| Compliance | CISO/Security Lead, Compliance Officer/Legal | Platform Administrator, Data Privacy Officer, Risk/Audit rep |

One person can fill multiple roles. In smaller organizations, the Platform Administrator may also be the IT/Identity Lead, and the CISO may also be the Compliance Officer. Use this guide to identify functions that need representation, not headcount.