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 guide 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.
Jump to section
Purpose
Define work in terms the scheduler can reason about
- 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.
Workflow
Turn recurring responsibilities into stable roles
- 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.
Guidance
Role design determines how expressive the schedule can be
Roles should represent meaningful coverage or assignment categories, not every temporary label that appears during a busy week.
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.
Avoid role sprawl
Use weekly assignments for exceptions; use roles for recurring structure
If a label only matters once, it usually belongs in the week rather than the permanent role catalog. Permanent roles should earn their place by supporting recurring coverage, eligibility, reporting, or assignment logic.
- Recurring duty or coverage need → role.
- One-time event or temporary detail → weekly adjustment.
- Qualification-sensitive responsibility → role with eligibility controls.
Practical notes
Role design patterns that keep the grid readable
- 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.
Questions
Real questions about roles, qualifications, and coverage
Including how many roles you can define, who can be assigned to them, and how role design affects automation.
How many different roles can RoleSchedule support?
RoleSchedule does not currently impose a separate fixed role-count cap in the role-creation workflow. You can define the recurring work, duty, standby, off, or other assignment roles your operation actually needs. The practical goal is to keep the catalog meaningful rather than creating a permanent role for every one-time exception.
Can I restrict a role to only qualified or approved members?
Yes. Role eligibility and approval controls can limit who is considered for a role. That allows Auto-fill and manual planning to distinguish between people who are merely available and people who are actually eligible to perform the assignment.
Can the same role be required on different shifts or days?
Yes. Roles and shifts are separate concepts. Requirements can determine how much of a role is needed for a particular planning context, while active-day settings help control when a role should participate in scheduling.
Should I create roles for leave, off days, standby, or training?
You can model non-work statuses when they help planners and viewers understand availability, but keep coverage roles distinct from absence or visibility roles. That separation makes requirements and Auto-fill easier to reason about.