Authentication Settings
Choose how people sign in to Incident Tracker: built-in passwords, Microsoft SSO (SAML), Google Sign-in or LDAP, and set up automatic account provisioning.
The Authentication Settings page lets you choose how people sign in to Incident Tracker. You can also have user accounts created and updated automatically from your organization's directory.
- Single Sign-onSign in with Microsoft work accounts
- Google Sign-inSign in with Google accounts
- Account ProvisioningCreate and update accounts automatically (Microsoft Graph or SCIM)
Which Sign-in Method Should I Use?#
| Method | How people sign in | A good fit when | Setup guide |
|---|---|---|---|
| Incident Tracker Authentication | With a username and password created in Incident Tracker | You don't use a central sign-in system, or you only have a few users | Create New User |
| Single Sign-On (SAML) | With their Microsoft work account (Microsoft Entra ID, formerly Azure AD) | Your organization uses Microsoft 365 and you want one sign-in for everything | Single Sign-on |
| Sign in with Google | With their Google account, using a Sign in with Google button | Your organization uses Google Workspace | Google Sign-in |
| LDAP Query | With their Active Directory credentials, checked through LDAP | Your organization signs in through its own Active Directory server | Contact Support |
Creating Accounts Automatically#
If you use Microsoft Entra ID, Incident Tracker can create, update, and disable user accounts for you, so you don't have to manage them by hand.
| Option | What it does | Requires |
|---|---|---|
| Microsoft Graph Sync | Incident Tracker pulls users from Microsoft groups on a schedule and places them into matching Incident Tracker user groups | Single Sign-On set up first |
| SCIM Provisioning | Microsoft Entra ID sends new users, changes, and deactivations to Incident Tracker automatically | A SCIM token from Incident Tracker Support |
See Account Provisioning to compare the two options in more detail.