Purpose
What this page is for
- Create the role definitions used in requirements and schedules.
- Support both work roles and non-work roles such as absence, off, or fallback types.
- Control how roles are labeled and displayed across the app.
Workspace guide
Roles
Roles are the language of coverage. They tell the system what types of assignments exist, when they are active, and how they should appear across the workspace.
Use this page when you need to
- Define the duty structure that powers requirements, schedule cells, and public pages.
- Use concise role keys so dense schedule grids stay readable.
- Set active days carefully because requirements and date overrides respect them.
Workflow
Recommended workflow
- Create your core work roles first.
- Add non-coverage roles such as leave, pass, training, off, or standby support roles as needed.
- Set the active-day behavior so the role appears when it should and disappears when it should not.
- Verify approvals or eligibility rules on the member role matrix if your process depends on it.
Detailed guidance
How this page fits into the product
Role keys should be designed for dense grids
Long role names are fine as descriptive labels, but the short role key is what often saves readability on the schedule grid, public pages, and summary blocks. Strong role keys are short, distinct, and easy to recognize quickly.
Active days influence more than appearance
Active days are not just decorative. They determine whether a role should be considered available for a day in the requirements matrix and whether specific schedule behavior makes sense on a given date. If active days are wrong, the scheduler may look broken when the real problem is role configuration.
Work roles versus absence roles
Keep your work roles and your visibility roles conceptually clean. Coverage roles drive actual staffing needs. Absence or off roles help the planner and public pages explain why someone is unavailable. Mixing those purposes too heavily makes the schedule harder to interpret.
Practical tips
What helps in real use
- Use short keys, readable names, and predictable active days.
- If a role appears on the wrong days, fix it in Roles before changing a week by hand.
- Use role colors carefully so they add quick meaning without overwhelming the page.
Common questions
Frequently asked questions
Why does the requirements page care about role active days?
Because the matrix uses role activity to decide whether a role should be treated as available or inactive for a date.
Should standby be a role?
That depends on your workflow, but many organizations model standby or reserve behavior through dedicated roles and scheduler rules.
Related