Indyco explorer - enterprise edition lets you manage all users, groups and permissions from the administration console.

Users can be local, internal to indyco or integrated in the company infrastructure.

Groups are used to grant permissions to individual users. A users can be included in multiple groups. To better understand how the permission system works please refer to the Permission documentation.


When a new user is created it automatically belongs to the Default Group, which is a special group that can be used to grant default permissions to all users. Users can still be removed manually from the default group if necessary.


Login Type

With Indyco - explorer enterprise edition the supported Login Types are:

  • Indyco
  • LDAP
  • Active Directory
  • Microsoft Entra

Indyco

The Indyco login type is a user account internal to indyco: the username and password are saved in the application and the account is not integrated with the company infrastructure.

Note: On installation, a default admin users is created.


LDAP

LDAP login allows for integration with the existing company infrastructure. Users, on configuring the system correctly, can access indyco using their domain credentials.

This login type is compatible with both Active directory and OpenLDAP. 

Note: For a correct association, the user must be recorded as domainname\username


ActiveDirectory

With ActiveDirectory login, you can configure single sign on, so that the users can log in automatically rather than having to to enter their username and password.

ActiveDirectory users, after configuring the system correctly, will be authenticated automatically. We suggest this configuration only if most PCs are in the windows domain.

For a correct association, the user must be recorded as domainname\username


Microsoft Entra

The Microsoft Entra integration leverages OpenID Connect standard to authenticate user within the tenant. Using Microsoft Entra for authentication integrates indyco with the corporate security policies (included MFA if required).


For the detailed configuration steps for each authentication type please refer to the specific documentation page.