A consistent handover process needs the right people involved and enough case capacity for upcoming transitions. Use these guides to set up those foundations.
People and permissions
Users and roles explains organization invitations, who can invite which roles, and how organization membership differs from participation in a case.
Manage departure dates explains how to maintain upcoming departures in People.
Company sign-in
Single sign-on explains how company sign-in works, who can use it, and what happens when you switch providers.
Follow Connect Okta SSO or Connect Microsoft Entra ID SSO for provider setup, field-by-field instructions, DNS verification, and your first login.
AI provider and governance
Customer-managed AI credentials explains how administrators connect OpenAI or Azure OpenAI, validate every AI capability before activation, rotate credentials, and respond to provider failures without a silent fallback.
Integrations
Integrations explains the shared Admin → Integrations area, its provider cards, and the Next 3 months, People, and Connection views for HR systems.
From there, follow Connect HiBob, Connect Personio, or Connect Workday for HR-system setup. Connect Slack explains workspace approval, bot permissions, case-specific conversation routing, and troubleshooting.
Billing and capacity
Billing and case credits explains how to buy credit packs and check that your organization is ready to create its next handover.
Build a repeatable practice
Agree who starts cases, who coordinates the knowledge capture, and who reviews the final documents. HR and operations can help make the process consistent, while managers and role experts check whether the knowledge is useful.
That division of responsibility helps organizations preserve institutional knowledge across employee offboarding, internal moves, and temporary leave without making every transition depend on an improvised checklist.