Permissions Management
An administrator opens Permissions in the sidebar to grant or change app access for Microsoft 365 users. Permissions apply to the selected schedule. A role in a global schedule does not automatically give the same role in a separate channel/chat schedule.
Role capabilities
| Capability | Admin | Self-Editor | Viewer | None / no role |
|---|---|---|---|---|
| View schedule appointments | Yes | Yes | Yes | No |
| Create appointments | Any assignees | Must include themselves | No | No |
| Edit/delete appointments, including recurrence | All Schedules appointments | Only appointments already assigned to themselves | No | No |
| Manage team, groups and projects | Yes | No | No | No |
| Change permissions and shared settings | Yes | No | No | No |
| Use My Settings and personal group visibility | Yes | Yes | Yes | No |
| Access API credentials, redeem licences, request organization deletion | Yes | No | No | No |
| Generate a calendar subscription URL | Yes | No | Yes | No |
A Self-Editor cannot remove themselves from an appointment while editing it. The owner/assignee rule applies even if someone else created the appointment. Outlook overlay appointments remain read-only regardless of Schedules role.
Membership is not access
Adding a person on Team makes them available for planning. It does not create a login or assign an app role. Conversely, granting app access does not automatically add that person to the planning list. A manual team entry is not a sign-in identity.
Grant and verify access
- Open the intended global or channel/chat schedule.
- Open Permissions and select the Microsoft 365 user.
- Assign the minimum required role and save the change.
- Ask the user to reopen the same schedule with the correct work account.
Use None to deny app access; manage team archive/removal separately. Keep another administrator available before changing administrator permissions. Microsoft 365 admin consent permits directory integration; it does not replace Schedules app roles.