Set up a workspace
Bring a team into Ridian while preserving account ownership and policy boundaries.
Reviewed · 2026-09-20 / Ridian
Separate people, accounts and the workspace
Section titled “Separate people, accounts and the workspace”A workspace organizes collaboration and policy. A member connects their own calendar account; ownership does not move to the workspace simply because the organization pays. An organization role is not blanket access to another member’s personal calendar contents.
Before inviting people, choose the business purpose, who should administer the workspace, which provider tenants are allowed, and which content may leave work calendars. Document these decisions in terms users can understand.
Prepare, then invite
Section titled “Prepare, then invite”- Select the intended workspace and verify your owner/admin role.
- Review organizational policies and tenant restrictions before connecting work accounts.
- Check the agreed seats and entitlement. Beta or pilot arrangements can be managed separately from a self-service subscription.
- Invite a colleague using their intended workspace identity. Ask them to check which workspace they enter after accepting.
- Let each person connect and grant access to their own permitted accounts.
Test a representative boundary
Section titled “Test a representative boundary”Have an authorized member use a synthetic test calendar with limited client rights. Confirm the allowed operation and an explicitly denied operation. Changing only the visible tool list is not a sufficient test of enforcement.
Offboarding
Section titled “Offboarding”Workspace membership, an assistant grant and a provider connection are separate relationships. Review each when a person leaves. Do not assume removing a workspace member deletes their provider events or their personally owned calendar account.
For the underlying rule model, read permissions. For contract and pilot questions, use the agreed commercial contact rather than interpreting a trial banner as the whole agreement.