Onboard a new planner
You want a new colleague set up with the right access and a usable view on first login.
Before you start
Decide which account type the new planner gets, because it changes what you fill in and how they receive credentials. A Microsoft Entra ID account reuses an identity that already exists in your tenant, so there is no password to hand over. A forms account lives in Dime.Scheduler's own database and is the fallback when there is no central identity system to integrate with.
You will also want to know which role the planner should get before you start, rather than deciding it in the dialog. In most tenants the answer is simply Planner.
1. Create the user account
Go to User Management → Users and add the user. Both account types need the same two things: an e-mail address and a display name. For Entra ID the e-mail has to be a real address in your tenant, since that is what the sign-in is matched against.
Language and time zone are optional. Leave them blank and the planner picks them on first login, which is usually the better default for a distributed team.
For a forms account, Dime.Scheduler generates a random password and e-mails the planner a reset link. You can pass the generated password on directly, but you do not have to: they are prompted to change it on first login either way.
See users for the full dialog.
2. Assign the role
A role is a bundle of permissions, and a user can hold several at once: their effective permission is the union. That means you compose access rather than inventing a new role for every combination.
For a planner, start with the standard Planner role, which grants full access to the planning view including creating, modifying, and deleting appointments. Add Personalization on top if you want them to build and share their own profiles, layouts, and filters. If they should look but not touch, use Viewer instead.
One thing that catches people out: role changes take effect on the next sign-in, not immediately. If you adjust a role while the planner is logged in, ask them to sign out and back in.
3. First sign-in
Point the planner at your Dime.Scheduler URL and tell them which sign-in method to use, since the login screen offers both and they have no way to guess. Entra ID users clicking the Azure / Office 365 button are asked once to consent to Dime.Scheduler using their credentials.
If you left language and time zone blank in step 1, the planner is prompted for both on that first launch. Time zone matters more than it looks: it drives how every appointment time is rendered for them, so it is worth getting right rather than clicking through.
See logging in for the first time.
4. Give them a workable starting view
A new planner lands on the standard profile, which is deliberately generic. Leaving them there is the most common reason a rollout feels worse than the demo did.
The quickest fix is to build one profile that matches how the team actually plans and make it their default: add the components they need, remove the ones they do not, then save the profile and set a default layout for each component. Step 4 of this recipe links to create a profile, which walks the whole thing end to end.
Note that building profiles requires the Personalization user action, so if you skipped it in step 2 the planner cannot do this themselves and you will need to build the profile for them.
Verify
Have the planner sign in and confirm three things: the planning view opens rather than an empty page, the components they expect are on screen, and they can drag a task onto the board and save it. If the board renders but nothing can be saved, the role is the thing to check first.
Related
- Build a personal workspace picks up where step 4 leaves off.
- Lock down with data-driven security if this planner should only see part of the data.