Offboard a colleague
Hand over business responsibilities and remove personal and automation access.
Offboarding removes a departing colleague's access while preserving business-owned services and records. Coordinate the work between an organization administrator, IT, finance, and the owners of affected products.
Hand over responsibilities
Transfer organization ownership before the owner leaves. Add replacement billing contacts and confirm they can access invoices. Assign ownership of integrations, operational duties, and renewal decisions to current colleagues.
Assign an accountable business owner to product automation. Use the affected product's credential guide to replace personal credentials used by jobs, then confirm those jobs work with their replacement.
Remove access
- In Console, select the organization and open Organization Settings → Members.
- For a directory-managed member, have IT deactivate the organization assignment in the upstream directory. Check Security → Provisioning → Sync history for the result, following directory provisioning. Review independent local grants in the member's Effective access view.
- Open Members → Member → Sessions and select Revoke all to end sessions for this organization. Follow session revocation before removing the member record.
- In Members, remove any remaining local membership and revoke pending invitations for the departing person. Confirm the member no longer appears as active and inspect audit activity.
- Have IT remove external identity-provider access and company device access that remain outside the organization assignment.
- Have product administrators revoke the person's product credentials and remote sessions, remove obsolete integrations, and rotate copied secrets through the affected product's access procedures.
Credential revocation blocks new requests; accepted work requires a separate review. Inspect Infra operations and Guard response actions for work submitted by the departing person. Use each product's cancellation controls for eligible work and inspect the final result before requesting a reversal.
Review every organization the person could access. A change to one organization's membership does not establish removal from another organization or an external service.
Verify business continuity
Confirm replacement administrators can sign in, finance can retrieve invoices, and affected automation runs successfully. Escalate unexpected access or disruption through support, including the organization, product, and time.
Removing membership is separate from deleting the person's Solarius account. The individual can request account deletion; organization data follows the business's retention requirements.