Login, Register, and Create Organization
These pages are the entry point into the workspace. They should help a new user register, sign in, create an organization, and understand the right next step after setup.
Use this guide when you need to
- Create an account, sign in, and start a new organization quickly.
- Use the create-organization flow as the beginning of the workspace, not the whole setup process.
- Move into the overview page immediately after creation to continue setup in the right order.
Jump to section
Purpose
Get from account creation to a usable workspace quickly
- Support first-time account creation and secure return access.
- Create the organization shell that the rest of the workspace lives inside.
- Guide new users into the next meaningful page instead of dropping them into a confusing interface.
Workflow
The first few actions after registration matter most
- Register if you are new to the product.
- Use the login page for normal return access.
- Create the organization, then open the overview page to continue setup.
- Use the docs, overview, and members pages first if you are still learning the workflow.
First 15 minutes
Aim for structure before polish
A new owner does not need every setting perfect before the first schedule. The fastest useful path is organization → shifts → groups → roles → members → requirements → first week. Fine-tuning can happen after the scheduling model is visible.
- Create the workspace shell.
- Add the minimum structure needed for one real group.
- Build one real week before customizing everything else.
Guidance
Onboarding should hand users into the scheduling workflow
Registration is only successful when the new owner can create a workspace, understand the setup order, and reach a useful first schedule without unnecessary detours.
What the create-organization page should and should not do
The create-organization page should feel light, focused, and transitional. It should not pretend to be a full dashboard. Its job is to collect the workspace shell and then hand the user into the actual operating workflow.
How to reduce confusion for first-time users
After registration or organization creation, direct people into the overview page and docs directory rather than expecting them to understand the structure immediately. New users benefit from a simple progression: create the workspace, understand readiness, then add the core planning data.
Returning-user expectations
Returning users should be able to sign in quickly and navigate directly to the dashboard. Navigation should make it obvious how to reach organizations, public pages, and the docs area without feeling like separate products.
Practical notes
Onboarding choices that reduce first-session confusion
- Create the organization shell first, then use overview to finish setup in order.
- Keep login and register pages simple and confidence-building.
- Point new users toward the docs directory while they are learning the workflow.
Questions
Questions new RoleSchedule owners ask first
What to configure first, how Free works, whether an organization can be upgraded, and how the workspace scales.
What is the first thing I should do after creating a RoleSchedule account?
Create the organization, then build the scheduling structure in this order: shifts, groups, roles, members, requirements, and the first real week. You do not need to perfect every setting before you start.
Can I try RoleSchedule before paying?
Yes. The Free plan is intended to let a new owner build a small real workspace and understand the scheduling workflow before upgrading. Current limits and paid-plan capabilities are always shown on the Pricing page.
Can I upgrade the same organization later?
Yes. The Free workspace can be upgraded rather than recreated, so the groups, roles, members, requirements, and schedules you already built stay with the organization.
Is RoleSchedule meant only for small teams?
No. The product is structured around organizations, groups, larger rosters, role eligibility, coverage requirements, and multiple scheduling contributors. Paid-plan limits determine the exact workspace capacity, while the same scheduling model scales from a small team to a larger multi-group operation.