Setting up user accounts

When you install ETA an administrator account is automatically created. You can use any of the following methods for identity and access management (IAM) to create user accounts:

Each of these methods support additional attributes that decide on the data access of each user. Some, like PKI, are quite limited in the attributes they can provide, but an administrator can always provide/override all access attributes.

If external user repositories are configured, any login attempt by a user is first checked against the internal ETA user list. If the user is not found, all configured external databases are checked, in the same order as their configuration, until one confirms or rejects a user's password.

When user access permission is granted, the user's role is configured by the ‘role’ attribute of that element. User roles are listed in Table 1.

Note: If the role attribute is missing, the user is assigned the ‘Configure‘ role (for backward compatibility).

Table 1: User roles


Privilege level




Users to whom this role is assigned can access and modify documents, networks and configurations.



Users to whom this role is assigned can access and modify documents, networks. They cannot modify configurations.



Users to whom this role is assigned can access and modify documents. They cannot modify configurations or access the Network tab.

Note: The Investigator role should not be used as a substitute for user security. When importing a project, for example, Investigators can see the names of any networks in the project but cannot open the networks. To prevent Investigators from seeing networks when importing projects, apply security settings (see Setting up security).

No user access


Use this option to render a user account inactive and prevent the user from logging in to Sintelix .

For more information about setting up user accounts see: