Roles & permissions

Read as Markdown

Every member of an Organizational Unit has one role, which decides what they can see and change. Everyone starts as a Member. Owners and Scheduler Admins can change a member’s role to give them broader access.

The roles #

Owner: full administrative control of the Organizational Unit. Only Owners can remove members, off-board the Organizational Unit, turn on domain sign-up, and manage directory sync. Every Organizational Unit needs at least one Owner.
Scheduler Admin: can edit any event in the Organizational Unit, and manage scheduling configuration such as branding.
Member: the standard role for someone who creates and manages their own scheduling requests. A Member only sees the events they scheduled.
Developer: can add applications to the Organizational Unit, so custom integrations can be built.
Developer Admin: has access to all of the Organizational Unit’s applications, and can create new ones.
Integration Subscriber: only used when setting up enterprise conferencing integrations.

	Owner	Scheduler Admin	Member
Manage organization settings	Yes	No	No
Set up branding	Yes	Yes	No
Create selection rules	Yes	Yes	Yes
Invite and manage members	Yes	Yes	No
Set up integrations	Yes	No	No
Connect service accounts	Yes	No	No

Give restricted access #

Because everyone starts as a Member, people who only schedule their own events, such as engineers helping with campus recruiting, see nothing beyond what they scheduled. Only give the Scheduler Admin or Owner role to people who need to see the whole Organizational Unit’s activity.

For stricter separation, for example keeping senior-hire interviews hidden from a campus recruiting team, give that team its own Organizational Unit.