Learning plans, paths, courses, hands-on labs and instructor-led training.
Your own Monosign v2026.10 server, empty and ready. Import an employee list, create a group, connect a SAML application, give the pilot users access and require a second factor for them.
Your own Monosign v2026.10 server with a lab mail server and SMS gateway. Connect the channels, enable e-mail and SMS codes, set the order users see, enroll a user, sign in with MFA and lock the MFA state.
Your own Monosign v2026.10 server with a SAML application and a partner identity provider that both fail for real. Read the errors and the audit log, fix each fault in Monosign and prove the fix with a real sign-in.
A customer tenant with MFA already in place and five open tickets. Each ticket hides a real misconfiguration. Find the cause from the symptoms and the logs, fix it and prove the fix.
Your own Monosign v2026.10 server with staff, administrators, users at risk and an emergency account. Build a layered policy set and watch real sign-ins from different countries and networks get denied, challenged or allowed.
Ticket INC-4821 at Aldermoor Freight: Nora Lindqvist in accounts payable can no longer sign in, and she is suddenly a member of Finance Approvers, the group that may release payments. Nobody in Finance asked for that. On your own Monosign server you find out who did what from the audit log, contain the account, show from the Access Timeline when the access existed, and send the evidence to the auditor as a scheduled report.
Your own Monosign v2026.10 server next to a real LDAP directory server. Connect one directory as a user source and run its first sync, repair a second source that never synced and brings too few people, and clean up a username that now exists twice.
Your own Monosign server and a small lab client that plays an AI agent. Register the agent with an accountable owner, give it one permission, cap it with a request budget and watch Monosign throttle and then suspend it. Then look at the AI apps employees open in their browsers and decide which are sanctioned, tolerated or unsanctioned.
Register an AI agent with an owner, add an MCP server to the catalog, allow only the tools it needs, decide approvals for a destructive tool and stop the agent with the kill switch. The MCP gateway service is a separate component that this lab does not install, so a small lab client, ticket-agent, reads the same catalog and approvals in its place.
Your own Monosign server and a small lab client that plays an AI agent paying refunds. The agent never pays on its own: it asks Monosign for approval and waits. You decide who is asked, how many people must approve, how long a request waits and whether a reason is required, then approve, let a request expire, approve as a second person from an e-mail link and deny, and read in the audit trail who decided.
Your own Monosign server, three employees and a small lab client that plays their AI chat app. Build a flow that stops secrets from leaving in a prompt, run it in watching mode first and read what it would have blocked, then start enforcing and see the prompt stopped. Add a second flow that replaces personal data with placeholders, and extend the first one with your own keyword.
Your own Monosign server and a small lab client that plays an AI agent building a nightly report. The agent trades its credential for a short-lived access token, and Monosign decides at that moment whether it may have one. Limit the agent to certain hours and to a network, watch the token request being refused with the reason, read the refusals in the audit trail, and then set restrictions that let the agent work again.
A real Monopam with a Linux server and a user who can reach it at any time. Remove that standing access, offer the server through a Request Policy, then request, approve, use and revoke time-bound access while the server itself proves each step.
A real Monopam and a Linux server, with recording switched off for the whole tenant. Turn it on, grant access through a policy that denies a risky command, run an SSH session and review its recording with a shared note.
Push accounts from your own lab tenant to a real SCIM 2.0 target: create the application and its key, send a pilot group, remove a user and watch the account go, schedule a sync and deliver a webhook.