Users
A user account is the bridge between a person and Dime.Scheduler: it controls whether they can sign in, what they see when they do, and what they are allowed to change. This page is where you create those accounts, attach the permissions and security data that decide each user's experience, and clean up after people who have moved on.
It is the busiest administration page in most tenants, because user setup is rarely one-and-done. People join, change rolesUser roleA named bundle of user actions assigned to users and user groups. Permissions flow through roles, never directly to a user., leave, swap teams, get extra responsibilities. The view is built around that churn: a grid of users on top, and below it a panel of assignments that follows whichever user you select. A draggable splitter between the two lets you give either half more room.
The users grid
The grid lists every registered user. Select a row and the assignment panel underneath switches to that user.
Each user has these properties:
| Column | Description | Required |
|---|---|---|
| Type | The account type: Forms or Azure AD. See Choosing an account type. | ✔️ |
| The user's e-mail address. For forms users this is also the login name. | ✔️ | |
| Display Name | The name shown throughout Dime.Scheduler. | ✔️ |
| Language | The language Dime.Scheduler renders in for this user. | ❌ |
| Time zone | The time zone Dime.Scheduler renders dates and times in for this user. | ✔️ |
Two columns do not store data. The one before Type shows a warning icon when the user owns shared content that other people depend on; the last one holds a pencil icon that opens the user for editing. More on the warning in Deleting a user.
The grid behaves like the other administration grids: you can filter on any column, group rows, page through long lists, export the current view to Excel with Export, and tick several rows to delete them in one go.
Adding a user
Before clicking Add, decide what account type you want this person to use, because the choice changes how they sign in and it cannot be changed afterwards. See Choosing an account type. The default and simplest choice is Forms, a Dime.Scheduler-managed account.
Add opens a dialog with the five fields from the table above. E-mail, display name and time zone are required; language is optional. If you leave language blank, the user is asked to pick one at first login:
Once chosen, the user can change both anytime from the preferences page:
When you create a forms user, Dime.Scheduler generates a password and shows it once, in a dialog with a copy button, right after you click Create. Copy it before closing the dialog: it is not shown again. At the same time Dime.Scheduler emails the new user a confirmation link; following it opens a page where they set a password of their own, so you only need to pass the generated one on if they want to sign in before confirming. The user side of that flow is on the first sign-in guide.
Editing a user
Click the pencil icon at the end of a row, or double-click the row, to open the same dialog with the user's details filled in. Everything can be changed except the account type, which is fixed once the user exists. To move someone from a forms account to an Azure AD account, create a new user and delete the old one.
Deleting a user
Most user records can be deleted directly: tick the row, click Delete, confirm. The complication is shared content.
When a user owns shared layoutsLayoutA saved arrangement of the planning board - visible resources, columns, and settings - that can be reused., profilesProfileA saved snapshot of a user’s planning board configuration, including the chosen layout and view options., or filters that other users depend on, the warning icon appears next to their row. Deleting that user without reassigning the content can leave broken references in the views of everyone they shared with.
Hover the icon to see which kinds of content are affected, and click it to open the Shared Content dialog. The dialog has a tab per content type (Filters, Layouts, Profiles) and lists each item with a Transfer to dropdown. Pick a new owner for each item, click Reassign Ownership, and the content moves over. When the warning icon is gone, the user is safe to remove. The User Generated Content page offers the same reassignment across the whole tenant.
Attaching permissions, groups, and security data
The panel below the grid is where you give a user their permissions and data-driven securityData-driven securityRestricting which records a user can see based on the data itself - for example a region or business unit - rather than on their role.. It is scoped to the user currently selected in the grid, so the workflow is select user, tick what applies, move to the next user.
The panel is split in two. The left half holds the tabs Roles, User Groups and User Profiles; the right half holds Filter Values, Categories and Time Markers. Both halves show a list of items with a checkbox in front of each, and a checkbox in the header to select or deselect the whole list at once. Drag the vertical splitter between them if one side needs more space.
The example below shows a user with every role assigned:
And one with all roles except one:
Assignment is a single click: tick the checkbox next to whatever you want to grant, and the change is saved immediately.
Changes to a user's assignments only take effect after that user signs out and back in. If a planner just lost a permission they should no longer have, ask them to log out before assuming the change "didn't work".
What each tab controls:
| Tab | What it does |
|---|---|
| Roles | Assigns roles (Planner, Administrator, Viewer, …) to the user. |
| User Groups | Adds the user to user groups. |
| User Profiles | Marks which shared profiles are available to the user. The star next to an assigned profile makes it the user's default. |
| Filter Values | Restricts the user to specific filter values, grouped by filter group. Empty means "access to all". |
| Categories | Restricts the user to specific categories. Empty means "access to all". |
| Time Markers | Restricts the user to specific time markers. Empty means "access to all". |
The last three matter most for what a planner can see and do in the planning viewPlanning viewThe main screen of Dime.Scheduler, where a profile lays out the components a planner works with. A new tenant has none until a profile is created or applied from a template.. They are how data-driven security works in practice: "this planner only sees jobs in the Northern region" is enforced by assigning them only the Northern filter valueFilter valueA single value inside a filter group, used as a qualification on a resource or a requirement on a task..
Choosing an account type
Every user account has a source: the system that holds the credentials and authenticates the sign-in. Dime.Scheduler supports two, and the choice is permanent for that account.
Microsoft Entra ID (Azure AD)
Shown as Azure AD in the type list. An account that already exists in Microsoft Entra ID (the service formerly known as Azure Active Directory). The user signs in through the Microsoft sign-in screen with their existing organizational credentials. This is the right choice when the organization already uses Microsoft 365 and wants Dime.Scheduler to live inside the same identity system: single sign-on, centralized offboarding, the works.
Required fields: e-mail, display name and time zone. The e-mail must be a real Entra ID address.
Users can individually grant consent, or the administrator can grant consent on behalf of the entire organization. For production, grant consent. To grant access to users on the sandboxSandboxThe separate Dime.Scheduler environment where upcoming features arrive before the production release. It has its own API host, sandbox.api.dimescheduler.com, so API clients target it explicitly., use the sandbox consent page.
Dime.Scheduler identity service (Forms)
A forms account is stored in Dime.Scheduler's own database. The user signs in with their e-mail and a password. Pick this when there is no central identity system to integrate with, or when the user does not have an Entra ID account.
A random password is generated on account creation and shown to you once. Pass it on to the user; they can change it afterwards from their preferences page.
Password policy:
- At least 6 characters
- At least one digit
- At least one lower-case letter
- At least one upper-case letter
- At least one special character
Required fields: e-mail, display name and time zone. Language is optional; if blank, the user picks it on first login.