Groups
Groups are the working containers for weekly planning. If your organization is the top-level workspace, the group is the level where detailed scheduling and requirements become manageable.
Roster | Mon 17Covered8 / 8 | Tue 181 open7 / 8 | Wed 19Covered8 / 8 | Thu 202 open6 / 8 | Fri 21Covered8 / 8 |
|---|---|---|---|---|---|
| 1st Shift | 1st Shift | 1st Shift | 1st Shift | 1st Shift | |
Team Alpha 4shown4 assigned | |||||
Alex Morgan | SITE-A | FIELD | SITE-A | STDBY | OFF |
Jordan Lee | FIELD | SITE-A | FIELD | SITE-A | OFF |
Taylor Reed | SUPPORT | ABS | SUPPORT | FIELD | SITE-A |
Casey Brooks | STDBY | SUPPORT | SITE-A | — | SUPPORT |
Use this guide when you need to
- Use groups to break one organization into manageable planning units.
- Keep requirements, schedules, and public links anchored to a real team or platoon.
- Export group and member public URLs by display name when leaders need to share visibility quickly.
Jump to section
Purpose
Use groups to mirror real planning ownership
- Create the planning units used by schedules and requirements.
- Organize membership so the right people appear in the right schedule grid.
- Provide group-level entry points into schedules, requirements, and public sharing.
Workflow
Create the planning boundary before the schedule
- Create the groups that mirror how work is actually planned.
- Move members into the correct group.
- Use the group page as the hub for group schedule actions, requirements, and exports.
- Share public group links when a leader only needs one slice of the organization.
Design decision
Create a new group when the planning rules genuinely diverge
Do not create a separate group just because a team has a different nickname. A new group is most useful when membership, requirements, schedule ownership, or public visibility needs to be managed independently.
If two teams are always planned together and share the same weekly coverage model, keeping them together can make the scheduler easier to operate. Split them when the planning boundary is real.
Guidance
A good group boundary keeps weekly work manageable
Groups work best when they reflect who is planned together, who shares requirements, and who should appear in the same schedule context.
Why group design affects everything downstream
Groups are not just labels. They define the scope of one planning surface. If groups are too broad, the schedule becomes noisy. If they are too narrow, coverage management becomes fragmented. The best group structure usually matches how supervisors actually think about weekly work.
What a strong group page should provide
A good group page should act like a local dashboard. It should show the group name, quick access to the weekly schedule, a clear path to requirements, public-link export actions, and enough context to tell whether the group is healthy without recreating the entire organization overview.
When to use group exports
Use group export links when leadership needs a clean list of public URLs for a specific platoon or team. This is especially useful when a group leader wants to share both the group overview and each member page without manually building the link list.
Practical notes
Group design choices that age well
- Keep group names concise so navigation stays readable on desktop and mobile.
- If the wrong people appear in a schedule, verify group membership before touching the schedule grid.
- Treat the group page like a planning hub, not just a list page.
Questions
Questions about managing multiple teams in one workspace
How groups scale, when to split a team, and how group boundaries affect schedules and requirements.
Can one RoleSchedule organization manage multiple teams or sections?
Yes. Groups are specifically designed to divide one organization into separate planning units while keeping them under the same workspace. That makes it possible to manage different teams, platoons, sections, or operating elements without creating a separate account for each one.
Should I create a group for every shift?
Usually no. Groups should normally represent teams or planning ownership, while shifts represent time windows. Create a separate group when membership, requirements, schedule ownership, or public visibility needs to be managed independently.
How many groups can I create?
Group limits are controlled by the active plan and are shown on the Pricing page. Paid plans can be configured for larger multi-group operations, and Site Admin controls those limits centrally in the Plan Catalog.
Can each group have its own schedule and requirements?
Yes. Groups are the main working boundary for detailed weekly scheduling. They can have their own membership, requirements, schedule context, and public group schedule while still rolling up into the same organization.