For whom, and for what
Most teams come to us with one concrete job: put MFA in front of the VPN, roll MFA out to every login, or run single sign-on on the Active Directory they already have. This page starts there, then shows how each identity class grows from it.
Four jobs we see most often
The situations that bring teams to DTS Identity, and what changes once it is in place. Each card links to the product section behind it.
Start with your workforce, add customers and devices when you need them
Three identity classes on one tenant, one policy engine and one audit log. Each story below follows one identity through the platform, from the moment it appears to the moment it leaves.
One employee, from the first day to the last
Employees, contractors and admins with one login for everything, and IT with one place where access is granted, checked and taken away.
Base plans: Essential up to 2,000 employees, Advanced up to 10,000. Approval flows, certifications and Windows SSO from Advanced.
How it runs
- 1
Day one
The account arrives from Active Directory through the sync, or by invitation for a contractor. Group membership assigns the applications, and SCIM creates the downstream accounts before the first login.
- 2
First login
MFA is required, so the user enrolls a passkey or an authenticator app on the spot. On a domain-joined PC, Kerberos signs them in without a prompt; from outside, the policy asks for the second factor.
- 3
Every day after
One sign-in reaches the VPN, cloud applications and internal tools over SAML and OIDC. Requests for new access go through an approval flow instead of a ticket.
- 4
Review and leave
Quarterly access certifications confirm or revoke what the person holds. On departure, deprovisioning deactivates the account and SCIM switches off the downstream accounts with it.
Partners and consumers, without building login yourself
B2B organizations with their own administrators and consumer sign-up with social login, on the same tenant as your workforce and billed per active user.
CIAM add-on, billed per external monthly active user. Organizations and enterprise brokering from Advanced.
How it runs
- 1
A partner company joins
You create the organization and invite one administrator. In the organization portal they invite their colleagues themselves and see which applications the organization may use.
- 2
They sign in with what they have
Home realm discovery routes the partner's email domain to their own identity provider, Microsoft Entra or Okta for instance, over an enterprise connection. Accounts are created just in time and linked on a stable identifier.
- 3
A consumer signs up
Self-service registration with email verification, or social login with Google, Apple, Microsoft and others. Bot detection and a disposable-address filter keep the form clean.
- 4
They stay in control
Users manage profile, factors, sessions and connected applications themselves, and revoke consent for an application whenever they want. Your login page carries your domain and design.
Trust the device, not only the password
Managed endpoints with a known state, and that state part of the access decision. Built into the same platform, not bought as a separate product.
DIAM add-on, billed per enrolled device, from Essential. Compliance policies, device-based authentication and vulnerability tracking from Advanced.
How it runs
- 1
Enrollment
The per-instance client enrolls the endpoint with a registration certificate. It appears in the inventory with owner, platform, software, patches and known vulnerabilities.
- 2
Compliance
A policy checks disk encryption, firewall, OS version, patch level and required or forbidden software, per platform. Violations are tracked fleet-wide.
- 3
At sign-in
An authentication policy takes compliance into account: inform the user, or enforce and let only compliant devices with their pinned user through. MFA can also be required at the Windows logon itself.
- 4
When something is wrong
A CVE view links every affected device. Isolate it remotely, pin the user or reset MFA enrollment; commands queue for offline devices and run on reconnect.
Three steps, none of them a leap
The trial environment runs on the same single-tenant architecture as every plan, so what you test is what you roll out.
Try it in a trial environment
A trial environment is free, runs for 30 days (longer on request) and opens the features of the higher tiers. Connect one application, enroll a passkey, watch the audit log.
Request a trial environmentProve it in your environment
A proof of concept on Essential or Advanced, with setup assistance if you want it: connect Active Directory through an agent, put SAML in front of the VPN, roll MFA out to a pilot group. The console's first-steps checklist walks through it.
First steps in the documentationRoll out with people who answer
Standard support from Essential, setup assistance included in Pro, and a named sales contact who speaks German and English. Add CIAM or DIAM later on the same tenant; entitlements apply live, without a migration.
Contact the teamBefore you start, answered
The questions teams ask when they map their situation onto the platform: the VPN, existing MFA, plans, and the path after go-live.
Can DTS Identity provide MFA for a VPN such as Palo Alto GlobalProtect?
Yes. DTS Identity is a SAML 2.0 identity provider, and a VPN gateway that supports SAML sign-in, such as Palo Alto GlobalProtect, hands authentication to it. The MFA requirement is set per directory or per application, so the VPN can demand a second factor always or only from outside trusted network zones, with passkeys, authenticator apps or SMS codes as the factor.
We already use Cisco Duo or privacyIDEA. Do we have to replace them?
No. From the Advanced plan, DTS Identity delegates the second factor for employees to Cisco Duo or privacyIDEA, so existing enrollments keep working while sign-in, policies and the audit log move to the platform. Passkeys and the built-in factors can be added alongside or later.
Can we start with workforce identity and add customers or devices later?
Yes. Customer identity (CIAM) and device identity (DIAM) are add-ons to the same DTS Identity tenant, not separate products. Switching one on unlocks the features live, on the same database and instances; nothing is migrated, and the base plan stays as it is.
Which DTS Identity plan fits which identity class?
Workforce identity runs on the DTS Identity base plans: Essential up to 2,000 employees, Advanced up to 10,000 and Pro for individually sized deployments. Customer identity needs the CIAM add-on, billed per external monthly active user; organizations and enterprise brokering start at Advanced. Device identity needs the DIAM add-on from Essential, billed per enrolled device, with compliance policies from Advanced.
Is there a proof of concept, and who helps with setup?
A DTS Identity proof of concept is available on the Essential and Advanced plans, and setup assistance can be added to both; on Pro it is included. Before that, you can try the platform in a free trial environment: it runs for 30 days, longer on request, on the same single-tenant architecture and opens the features of the higher tiers.
Who supports us after go-live?
Standard support for DTS Identity is part of every paid plan from Essential, reachable through the DTS service desk around the clock, and the sales contact stays available in German and English. Recurring background problems such as a failing directory sync surface in the console as issues, and from Advanced, alarms can email you on chosen audit events.
Ready to bring every identity into one platform?
Request a free trial environment or talk to our team about workforce, customer and device identity: standards-based and operated in the EU.