Identity & Access Integrations
Connect AMODIT to the identity services already used across your organization. Employees sign in with familiar accounts and access the business processes available to their roles.
Use the identity model already in place
AMODIT connects workflow access with established identity services. Teams use existing accounts, while administrators manage who can reach processes and information through assigned roles and permissions.
The setup supports cloud and on-premises environments and is configured around the organization’s identity provider and access policies.
Available options include:
- creating AMODIT accounts from Active Directory accounts,
- single sign-on with Microsoft Entra ID, formerly Azure Active Directory (Azure AD),
- sign-in through OAuth providers such as Google, Facebook, and Microsoft,
- OpenID and SAML configurations.
How identity access works with AMODIT
One clear path connects the organization’s identity source with the processes employees use in AMODIT.
1. Identity source
Use Active Directory, Microsoft Entra ID, or an external Google, Facebook, or Microsoft account as the identity source.
2. Sign-in configuration
Connect the identity source through directory integration, OAuth, OpenID, or SAML, based on the environment and provider.
3. Access to processes
After sign-in, users work in the AMODIT processes available through their assigned roles and permissions.
Identity and sign-in options
Select the option that matches the organization’s directory, cloud environment, and authentication policies.
Active Directory
Create AMODIT user accounts from existing directory accounts. Administrators manage access according to established policies and procedures.
Microsoft Entra ID
Use Microsoft Entra ID, formerly Azure Active Directory (Azure AD), for single sign-on and access based on assigned roles and permissions across cloud and on-premises environments.
OAuth, OpenID & SAML
Let users sign in with configured external accounts through OAuth providers such as Google, Facebook, and Microsoft, or through OpenID and SAML.
Identity integration brings AMODIT into the access model employees and administrators already know. A connected directory can supply users, groups, and organization structures, while SSO handles sign-in. An agreed setup can synchronize more than one domain.
Process access remains connected to assigned roles and permissions. External identity providers can also add multi-factor authentication as part of their sign-in flow.
Tell us which directory or identity provider you use and how employees should access AMODIT. We will discuss the appropriate sign-in and account setup.
Identity & Access FAQ
1Which identity services can connect with AMODIT?
AMODIT supports Active Directory, Microsoft Entra ID, external accounts through OAuth providers such as Google, Facebook, and Microsoft, as well as OpenID and SAML.
2Does AMODIT support single sign-on?
Yes. Microsoft Entra ID and configured external identity providers support single sign-on to AMODIT.
3How does Active Directory integration work with AMODIT?
Active Directory integration creates AMODIT user accounts from existing directory accounts. Administrators then manage access according to established policies and procedures.
4Can employees sign in with Google, Facebook, or Microsoft accounts?
Yes. AMODIT supports sign-in through configured OAuth providers such as Google, Facebook, and Microsoft.
5How is the integration method selected?
The configuration follows the organization’s environment, identity provider, account provisioning needs, and access policies. Active Directory, Microsoft Entra ID, OAuth, OpenID, and SAML cover different identity setups.
6Can an external identity provider add multi-factor authentication?
Yes. Configured external identity providers can add multi-factor authentication as part of their sign-in flow.