Table of Contents

Logging in to DeskDirector

Niamh Ferns Updated by Niamh Ferns

DeskDirector Login Steps

This article walks through the features and behaviour of the DeskDirector sign-in page.

  1. Enter email address

The user will need to enter the email address for the account they want to sign in to:

If the email address isn't associated with an existing contact, the user will have the opportunity to create a contact in Step 4. The user can only create a new contact if their email domain has been registered against an account on the associated account profile page inside the Admin Portal. If their domain is not registered against an account, they will see this message instead:

Your email address hasn't been registered and we're not able to automatically create an account for you. Send us an email at user@yourdomain.tld so we can create an account for you.
  1. Select platform

There are 3 platforms that a user may sign in to. They are the Admin Portal, Tech Portal, and Client Portal. These options will only display if the user's email address is associated with the corresponding entity. For example, if your email is associated with both a contact and a member/resource, then you will see all three platforms:

If your email address is only associated with a single entity type, this step will be skipped altogether. This means that most contacts will never see this page; they will skip straight to step 3.

  1. Select sign-in method

There are 3 possible sign-in methods to choose from, depending on which features you have configured, and which platform the user has selected. These are:

  • Microsoft OAuth
  • Email token
  • Password
  1. Create contact (Client Portal platform only)

Depending on your Automatic Contact Creation configuration, if a contact doesn't already exist, the user will be able to create one as they sign in. Only Microsoft OAuth and the email token sign-in methods can be used in this situation. When using email token login, the user will have the option to enter some details about themselves:

If the user chose Microsoft OAuth, then all their information will be sourced from their Microsoft account.
  1. Optionally, stay signed in

After the user has successfully signed in, they will be asked whether they want to stay signed in. If they choose "yes", a persistent cookie will be saved to their machine. If they select "no", a session cookie will be saved instead.

  1. Select account (Client Portal Only)

If the user has more than one account associated with their email address, they will have the chance to select which one to sign in to:

How did we do?

DeskDirector Features Overview

User Profiles & Profile Pictures

Contact