Understanding schedule permissions
Schedules use the same access model as packages: three ordered privilege levels, and a grant that can sit either on the workspace's Schedules node or on one individual schedule.
A grant on the node covers every schedule in the workspace. A grant on a single schedule below it covers only that one. Both are configured under Access management.
What each action needs
| Action | Minimum level | Is a grant on one schedule enough? |
|---|---|---|
| View the Schedules list | Viewer | Yes |
| Open a schedule and read it | Viewer | Yes |
| Edit fields and save | Contributor | Yes |
| Enable or disable from the list | Contributor | Yes |
| Add, remove and reorder tasks | Contributor | Yes |
| Create | Administrator | No. The workspace Schedules node only. |
| Duplicate | Administrator | No. It is a create. |
| Delete | Administrator | No. The workspace Schedules node only. |
| Run or Stop from Executions | Workspace Administrator | No |
Administrator access on one schedule lets you edit that schedule. It does not let you create or delete others.
What a read-only user sees
View-only access gives a read-only schedule: no Save, and no Enable, Disable, Add or Remove controls.
The row checkboxes are not shown either. With read-only access the list has no checkbox column and no header checkbox, because every action they enable is closed to you. Selecting a row still opens the schedule to read. A user with edit rights on at least one schedule sees the checkboxes along with Enable and Disable.
Administrators
Workspace and global administrators are not affected by the gating described above.
Related articles
- Understanding user permissions for packages
- Understanding the Schedules list
- Add tasks to a schedule
- Manage users and roles in TimeXtender Data Platform
