Members
The Members section is the source of truth for people in the workspace. Clean member data makes every other page more reliable, easier to read, and easier to share.
Use this guide when you need to
- Create and maintain the people who appear in schedules, exports, approvals, and public pages.
- Use display names consistently so the grid, exports, and member public pages stay readable.
- Make sure members are assigned to the right group before weekly planning starts.
Jump to section
Purpose
Build a roster the schedule can actually use
- Maintain the roster used everywhere else in the workspace.
- Assign people into groups so readiness and scheduling logic have the right ownership structure.
- Open individual member views for history, stats, public sharing, and approval checks.
Workflow
A clean member setup sequence
- Create or import the roster.
- Standardize display names so they are recognizable in tight schedule grids.
- Assign each member into the correct group.
- Review member detail pages for trends, public visibility, and role approvals where needed.
Guidance
Roster quality affects every downstream schedule view
Member records are more than names in a list; they are the identity layer behind group ownership, eligibility, exports, and public schedule views.
Why display names matter more than they seem
Display names are used in exported public links, group schedule grids, public member pages, and quick planning views. Long or inconsistent naming creates friction everywhere, especially on mobile or when leadership needs a fast visual scan.
A good display name is short, recognizable, and stable. If the public schedule is part of your real workflow, this matters even more because those links and labels become part of the user experience outside the dashboard.
Group assignment is part of member setup, not a separate afterthought
A member without a group is usually a planning problem waiting to happen. The system can hold the person record, but the weekly scheduling workflow becomes less accurate because group schedules and requirements are built around the group as the working container.
If readiness or schedule coverage feels wrong, one of the first things to verify is whether the right members are actually in the right group.
How the member page should be used
The member detail page is useful when you need to inspect one person more deeply: what they are working this week, which assignments appear frequently, whether they have absences, and which public page link should be shared. It is a good troubleshooting page when a leader asks about one specific person rather than a whole group.
Roster hygiene
Three member fields deserve extra attention
Display name, group placement, and role eligibility are the fields most likely to surface repeatedly during normal scheduling. If those three are clean, the grid, public pages, exports, and assignment decisions become easier to trust.
- Use stable display names people recognize immediately.
- Keep group membership current when teams reorganize.
- Review role eligibility before blaming the scheduler for a missing assignment.
Practical notes
Roster hygiene that prevents weekly friction
- Keep display names short enough to fit in grids without turning every cell into an ellipsis.
- Use the member roles page when approvals are important to the scheduling logic.
- If exports look wrong, verify display name, group placement, and public link availability together.
Questions
Practical questions about rosters, accounts, and member schedules
Answers to the questions teams usually ask about roster capacity, member logins, individual schedule visibility, and Auto-fill inputs.
How many people can I schedule in RoleSchedule?
Roster capacity is plan-based rather than hard-coded into the Members page. Free and paid plans can have different member limits, and the current limits are shown on the Pricing page. The scheduling model is built to work with larger team rosters, not just a handful of personal-calendar users.
Does every scheduled member need a RoleSchedule login?
No. A member can exist on the roster and appear on schedules without having dashboard access. Workspace accounts are for the people who need to administer, schedule, or view protected workspace information; public schedule pages can handle read-only distribution.
Can individual members see only their own schedule?
Yes. Member public pages provide a focused published schedule without exposing the planning dashboard. Supported public member schedules can also be subscribed to from Google Calendar.
What member information matters most for Auto-fill?
Group placement, role eligibility, availability or approved absences, and a clear display name are the most important inputs. If those are accurate, RoleSchedule has much better information when deciding who can cover a required role.