Skip to main content
Atomcal
How it helps FAQ
Built into your Atomcal calendar

Give each organizer
the access they need.

Coordinate a team of hosts and moderators with calendar membership, roles and permission settings—so the person updating an event does not need to own the whole workspace.

See how it helps
  • Roles belong to a calendar
  • Members can hold assigned roles
  • Review access as teams change

Shared calendar control

Make responsibilities easier to hand off

Atomcal stores calendar members and role assignments separately, giving calendar owners a structured way to manage the team behind the event schedule.

Define

Set the roles your team uses

Create roles that describe the work organizers actually do, such as host or moderator, then configure the permissions available for each role.

Assign

Add members to the right role

Manage calendar membership and associate members with the roles that match their responsibilities. Keep ownership limited to the people who need it.

Review

Update access when duties change

Use the member and role lists to review who can manage the calendar. Remove or change an assignment when a moderator leaves the team.

Check permissions before sharing the calendar. Role names do not grant access by themselves; verify the actual permission settings and test the workflow with a member who has the intended role.

FAQ

Calendar roles and permissions, in practice

Can a calendar have multiple roles?

Yes. Calendar roles can be assigned to members so a group can separate organizer responsibilities.

Does a role automatically make someone the calendar owner?

No. Role membership and calendar ownership are distinct. Use ownership for the person responsible for the calendar and assign narrower roles to other organizers.

Should everyone get the same permissions?

Usually not. Match each member’s access to the work they do and review the permission configuration before relying on it for a sensitive action.

Share calendar work without sharing every permission

Define the organizer roles first, then add the members who need each level of access.