# Cimento

> Setup documentation for security administrators deploying Cimento phishing simulation and security training.

- [Cimento Documentation](https://docs.cimento.ai/index.md): Setup and reference documentation for security administrators deploying Cimento phishing simulation and security training.
- [Before you begin](https://docs.cimento.ai/getting-started/before-you-begin.md): What to have in place before setting up Cimento: a directory source, the admins who own each tool, and pilot groups.
- [Connect your employee directory](https://docs.cimento.ai/getting-started/employee-directory.md): Choose where Cimento imports employees and groups from, whether Okta, Microsoft Entra ID or Google Workspace, and what gets imported.
- [Integrations](https://docs.cimento.ai/integrations/overview.md): Every tool Cimento connects to, what it's used for, who you need to set it up, and a step-by-step guide for each.
- [Connect Okta](https://docs.cimento.ai/integrations/okta.md): Import employees and groups from Okta over SCIM and set up single sign-on, step by step, using the Cimento AI app from the Okta Integration Network.
- [Connect Microsoft Entra ID](https://docs.cimento.ai/integrations/microsoft-entra-id.md): Import employees and groups from Microsoft Entra ID over SCIM and set up single sign-on, step by step, with an enterprise application you create in Entra.
- [Connect Google Workspace](https://docs.cimento.ai/integrations/google-workspace.md): Import your Google Workspace directory and place phishing simulations directly in Gmail inboxes, step by step, using domain-wide delegation.
- [Connect Microsoft 365](https://docs.cimento.ai/integrations/microsoft-365.md): Place phishing simulations directly in Outlook inboxes with Microsoft 365 Direct Inject, step by step: admin consent, mailbox scoping and a connection test.
- [Phish Alert Button for Outlook](https://docs.cimento.ai/integrations/outlook-phish-alert-button.md): Deploy Cimento's report button to Outlook so employees can send suspicious email to your security team in one click.
- [Connect Slack](https://docs.cimento.ai/integrations/slack.md): Send Cimento's training and remediation notifications as Slack direct messages, step by step, with every Slack permission explained.
- [Phishing simulation overview](https://docs.cimento.ai/phishing/overview.md): How Cimento phishing simulations work across email, SMS and voice, and what a security admin configures to run them.
- [Connect email delivery](https://docs.cimento.ai/phishing/email-delivery.md): Connect Google Workspace or Microsoft 365 so Cimento can place phishing simulations directly in employee inboxes.
- [Mailbox permissions for direct delivery](https://docs.cimento.ai/phishing/mailbox-permissions.md): Every mailbox permission Cimento uses to place phishing simulations directly in Google Workspace and Microsoft 365 inboxes: what each one allows, what Cimento does with it, and how to narrow or revoke it.
- [SMS and voice simulations](https://docs.cimento.ai/phishing/sms-and-voice.md): Enroll employee phone numbers so Cimento can run SMS and voice phishing simulations.
- [Templates and campaigns](https://docs.cimento.ai/phishing/campaigns.md): Choose or build a phishing template, target an audience, schedule delivery and follow up on results.
- [Training overview](https://docs.cimento.ai/training/overview.md): How Cimento delivers security awareness courses and policy acknowledgments, and what a security admin configures to run a program.
- [Training content](https://docs.cimento.ai/training/content.md): Use Cimento's content library, build courses in the editor, import PDFs and slide decks, or generate lessons with AI.
- [Training campaigns](https://docs.cimento.ai/training/campaigns.md): Assign courses and policies to employees with due dates, reminders and completion tracking.
- [Policy acknowledgments](https://docs.cimento.ai/training/policies.md): Publish versioned policies employees must read and acknowledge, and keep an audit trail of who accepted which version.
- [Agent Hub overview](https://docs.cimento.ai/agent-hub/overview.md): Visibility into the AI coding agents on your fleet: what Agent Hub shows, what it deploys, and how to set it up through your MDM.
- [How the Agent Hub endpoint agent works](https://docs.cimento.ai/agent-hub/how-it-works.md): Components, data flow, scheduling, identity resolution, egress, fail-open behavior and code signing of the Cimento endpoint agent.
- [What data Agent Hub collects](https://docs.cimento.ai/agent-hub/data-collected.md): The exact allowlist of fields the Cimento endpoint agent sends, what never leaves the device, and how to verify it yourself.
- [Deploy Agent Hub with Jamf Pro](https://docs.cimento.ai/agent-hub/deploy/jamf.md): Create a least-privilege Jamf Pro API Role and Client so Cimento can deploy the endpoint agent to a computer group, with every privilege explained.
- [Deploy Agent Hub with Iru](https://docs.cimento.ai/agent-hub/deploy/iru.md): Create a least-privilege Iru (formerly Kandji) API token so Cimento can deploy the endpoint agent to a blueprint, with every endpoint permission explained.
- [Deploy Agent Hub with SimpleMDM](https://docs.cimento.ai/agent-hub/deploy/simplemdm.md): Create a least-privilege SimpleMDM API key and confirm your SAML-mapped email attribute so Cimento can deploy the endpoint agent to a device group.
- [Deploy Agent Hub with Microsoft Intune](https://docs.cimento.ai/agent-hub/deploy/intune.md): Grant Cimento tenant-wide consent to three Microsoft Graph permissions so it can deploy the endpoint agent to Windows PCs in an Entra security group.