Users
Each user has the following base parameters:
| Parameter | Description |
|---|---|
| Username | The username |
| E-Mail Address | The E-Mail address |
| Authentication Type | The way the user can login into the system |
| Description | An additional description |
| Active | Indicates if it is active |
| LDAP Distinguished Name | The LDAP Distinguished Name if AuthenticationType Ldap is used |
| User Type | The type of the user |
| Password | The user password |
The following Authentication Types are currently supported:
- System
- LDAP
User Type
The user type defines what purpose a user has and what users with this type can do.
Each user has one of the following user types:
| User Type | Login allowed | Modification allowed |
|---|---|---|
| System | ||
| Frontend | ✔️ | ✔️ |
| Node | ✔️ | ✔️ |
| Connection | ||
| Panel | ✔️ |
System
The system user type belongs exclusively to the internal system user.
This user is used to perform all internal database changes when there is no logged-in user.
Frontend
The frontend user type belongs to all manually created users who can log in via the GUI or the API.
Node
The node user type belongs to the users that are automatically created when two nodes are paired together.
The node users are required for the sync between different nodes.
Connection
The connection user type belongs to the internal connection users.
A connection user is used to establish communication between different projects.
Connection users cannot log in via the GUI or the API, and can also not be modified.
Panel
The panel user type belongs to the panel users.
When a panel user is assigned to a web panel, this web panel can be accessed without requiring a user to log in.
This is necessary in scenarios such as displaying a panel on a TV.
Some components on a panel require elevated permissions (e.g. Select-a-Line or a dropdown with placeholders).
These permissions can be granted specifically to the panel user.
Panel users cannot log in via the GUI or the API.
Default Users
The following users are created automatically:
| Name | Description | User Type | Login allowed | Modification allowed |
|---|---|---|---|---|
| system | Internal user that performs all database changes. | System | ||
| admin | Administrator user that has all permissions. | Frontend | ✔️ | Password reset only |
| public | Allows viewing pages without requiring a login. Permissions must be granted to view the pages. | Frontend | ✔️ | ✔️ |
| connection_user | Internal user that establishes connections between the projects. | Connection | ||
| panel_viewer | Can be assigned to web panels to allow viewing it without requiring a login. Permissions must be granted to view the web panels. | Panel | ✔️ |
Permissions
The user gets permissions from all its groups. If one of its groups has an access permission, the user gets this permission too. If one of its groups has a never permission, the never overrides the access permission from all other groups.
The permissions can be set or overridden individually on the user level. A user can also exist without any groups assigned. If the user gets a never permission from one of its groups, the permission cannot be overridden.