Getting Started with DeskDirector
DeskDirector Portals
Browser Support
What is the DeskDirector Admin Portal?
What is the DeskDirector Tech Portal
What is the DeskDirector Client Portal?
Desktop Portal
Managing Your Account
Admin Essentials
DeskDirector Features Overview
Logging in to DeskDirector
User Profiles & Profile Pictures
Managing Tickets with DeskDirector
Office Hours
Getting Started with the Solution Library
How Searching Works
Embedding Help Page Media
Get started with the DeskDirector Power Automate Connector
Features
Portal Customization
Forms
Service Catalogue
Communication
Email Connectors
Notifications
Email Notifications
Actionable Messages for Emails
Real-Time Chats
Email Template Engine
Surveys
Broadcasts
Generative AI
DeskDirector with Generative AI
Ticket Summary for TECH Portal
Setting up AI Service Providers
Microsoft Foundry for DeskDirector
Knowledge Bases for AI Assistants
Custom Tools for AI Assistants
AI Assistants in DeskDirector
Advanced
Login & Authentication
Contact Groups
Custom Domains
File Storage
Dashboard
Accounts
Contacts
Approvals
Tags
Task Lists
The Learning Center
Portal Deep Linking
Auditing & Analytics
Microsoft Power Automate
Actions
Solutions
Featured Solution: Teams Ticket Discussion
Power Automate Template Gallery
Featured Solution: Ticket Briefing
Power Automate Administration
DeskDirector Power Platform Connector Reference
Power Automate Connector - Setting up your first flow
Microsoft Teams App
Introducing the DeskDirector for Microsoft Team App
Installing the Microsoft Teams App (Client Mode)
Installing the Microsoft Teams App (TECH Mode)
Setting up Tags for Teams Discussions (TECH Portal)
Branding the DeskDirector Teams App
DeskDirector Teams App Notifications
Contact Groups Integration with Microsoft Teams
Setting up Content Security Policy (CSP)
Advanced topic: Setting up Tech & Client Mode in the same tenancy
Integrating Microsoft Teams with DeskDirector Tech Portal
Smart Alerts for TECH Users
Integrations
Developer Resources
Getting Started
What is the Toki Iti API
API Versions & Routes
Roles & Scopes
Authorization Options
Querying the API
How to Change an Entity Through the API
API Key Authorization
OAuth Fundamentals
Understanding OAuth for Tokity Integrations: Key Concepts
OAuth Authorization Code Flow: How an App Gets Access to Tokity
OAuth App Registration
How to Register an OAuth App to Integrate with Tokity
Choosing an OAuth App Type: Confidential vs. Public Apps and Client Secrets
OAuth Personal Secrets: What They Are and When to Use Them
OAuth Administration
Configuring OAuth Settings in Tokity
Managing OAuth Authorized Sessions and User Consent
Granting OAuth Admin Consent at the Root Level
API Response Control
Uploading Attachments (Ticket API)
The Prefer Header — Overview
Controlling Returned Data (Ticket API)
Controlling Returned Data (Form Result API)
Controlling Returned Data (Workspace API)
Workspace Ordering
How Workspace Ordering Works
Creating and Reordering Workspace Groups
Adding and Reordering Tickets in a Workspace Group
Data Sync & Notifications
Delta API: Tracking Changes Over Time
Webhooks vs. Events — Differences, When to Use Which
Verifying Webhook and Event Payloads (HMAC Signature)
Ticket Widgets
Ticket Widget: Overview
How the Widget Is Requested
Ticket Widget Anatomy and Styling
Ticket Widget Actions: Leading, Secondary and Primary
Ticket Widget: Progress Type
Ticket Widget: List Type
Ticket Widget: Description Type
Ticket Widget: Form Type
Ticket Widget: Control When a Widget Refreshes
Ticket Widget: Form Results and State Across Steps
Ticket Widget: Error Responses and Debugging
Ticket Widget: Building a Multi-Step Request
Glossary
Security
Troubleshooting
Troubleshooting via Web Developer Tools
Permissions & Access - Common Issues
Contact DeskDirector Support
Troubleshooting DeskDirector Connection Issues
Desktop Portal - Common Issues
Contact Impersonation
Approvals - Common Issues
Microsoft Teams App - Common Issues
Email & Email Delivery - Common Issues
Login & Authentication - Common Issues
DeskDirector Desktop App - Installation Issues
Table of Contents
- Automatic Contact Creation
- Automatic Contact Creation Rules
- Match company domain SID (with contact creation)
- Match company domain SID (without contact creation)
- Match company domain SID and email domain (with contact creation)
- Match company domain SID and email domain (without contact creation)
- Match company domain SID for sign in, match company SID and email domain for contact creation
- Edge Cases
- Automatic Contact Creation Rules
- All Categories
- Getting Started with DeskDirector
- Admin Essentials
- Automatic Contact Creation
Automatic Contact Creation
Updated
by Niamh Ferns
- Automatic Contact Creation
- Automatic Contact Creation Rules
- Match company domain SID (with contact creation)
- Match company domain SID (without contact creation)
- Match company domain SID and email domain (with contact creation)
- Match company domain SID and email domain (without contact creation)
- Match company domain SID for sign in, match company SID and email domain for contact creation
- Edge Cases
- Automatic Contact Creation Rules
Automatic Contact Creation
System > Authentication > Contact Auto Creation.
To aid in onboarding and provide a smoother experience for DeskDirector end users, we have a system for automatically creating contacts on first login based on some pre-configured rules and criteria. To automatically create a contact, DeskDirector needs to first figure out which company the contact should be created under. We will use 1 of 2 methods for checking this:
Automatic Contact Creation Rules
System > Authentication > Active Directory
Match company domain SID (with contact creation)
Sign-in and creation both use Active Directory as the primary deciding factor. When signing in, if there are multiple contacts with the same email address, Active Directory will be used to find the contact with a matching company, then the most related contact will be used as the authorised user.
If a user does not exist, DeskDirector will create a contact under the company in DeskDirector with the appropriate SID set. If multiple companies match the SID, then we will find the most relevant one by using an email domain match.
Match company domain SID (without contact creation)
Sign-in will use Active Directory as the primary deciding factor, but will not create a contact if one doesn't already exist. When signing in, if there are multiple contacts with the same email address, Active Directory will be used to find the contact with a matching company, and then the most related contact will be used as the authorised user.
Match company domain SID and email domain (with contact creation)
DeskDirector will look for existing contacts with a matching SID and email domain. If one can't be found, a contact will be created in the most likely company. A contact's company that matches both SID and Email Domain is preferred over others.
If there no companies that match both the domain SID and email domain can be found (i.e. only one or none can be satisfied), a contact will not be created. When there are multiple contacts with the same email address on login, our system will rank each contact and select the highest rank for which contact to use.
Match company domain SID and email domain (without contact creation)
DeskDirector will look for existing contacts with a matching SID and email domain. If one can't be found, a contact will be created in the most likely company. A contact's company that matches both SID and Email Domain is preferred over others. If matching against a contact fails, a contact with not be created.
If there no companies that match both the domain SID and email domain can be found (i.e. only one or none can be satisfied), a contact will not be created. When there are multiple contacts with the same email address on login, our system will rank each contact and select the highest rank for which contact to use.
Match company domain SID for sign in, match company SID and email domain for contact creation
This will check for a company with a matching SID. If a contact exists under that company, the user will be logged in. If no contact exists, then DeskDirector will use both the SID and Email Domain for contact creation.
Edge Cases
Normally, Active Directory or an email domain is enough to easily identify the company, but there are scenarios where this alone isn't sufficient.
- Multiple companies in DeskDirector share the same account Active Directory SID
- Companies without an email domain (e.g. contacts using a generic
@hotmail.comdomain) - Multiple company branches
Some limitations and restrictions make it hard to achieve branch isolation within Autotask and ConnectWise. One recommended practice is to create different companies for each branch under a parent company. In this scenario, those branch companies share the same account security identifier and email domain. To be able to cover those scenarios, DeskDirector provided several rule sets to decide what to do when automatically generating a contact.
This is a special scenario; for this case, we can use Custom SIDs.