Purpose
What this page is for
- 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.
Workspace guide
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.
Use this page 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.
Workflow
Recommended workflow
- 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.
Detailed guidance
How this page fits into the product
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 tips
What helps in real use
- 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.
Common questions
Frequently asked questions
Can a member exist without a group?
Yes, but that weakens readiness and usually causes friction when you get to group-level scheduling.
Should groups be based on shifts or teams?
Usually teams, platoons, or sections. Shifts are a separate concept and belong on the Shifts page.
Related