Working with Service#
User roles and permissions#
In LUNA CLEMENTINE 2.0, access rights are assigned according to the role model. The Service supports two user roles: “user” and “administrator”. Service user roles and a description of their permissions are presented in Table 1.
Table 1. List of roles and permissions
Role | Section | Permission |
---|---|---|
Administrator | Working with Domains | View the list of global domains; |
Edit names of the domains; | ||
Search by name of domains; | ||
Add new domains | ||
Last events | View list of last events; | |
View event details; | ||
Filter events | ||
Events archive | View archived events; | |
View event details; | ||
Filter archived events | ||
Search | Search by face and body image, face ID, face event ID, external face ID; | |
Filter events | ||
Lists | View lists; | |
Add, edit, and delete lists | ||
Handling policies | View handling policies; | |
Add, edit, and delete handling policies | ||
Verification | Create verifiers; | |
View verifiers list; | ||
Test verifiers; View verification result; | ||
Configure parameters of verifiers | ||
Event sources | View event source list; | |
Search in an event source list; | ||
Add, edit, and delete event source; | ||
Configure event source settings; | ||
View video streams | ||
Tasks | Create tasks; | |
View tasks list; View task result; | ||
Cancel tasks; | ||
Configure parameters of tasks Time tracking: | ||
- View reports; | ||
- Create reports | ||
Users | Add, edit, and delete accounts; | |
Change and recover account passwords | ||
View accounts of all global domains; | ||
Add accounts to the created global domains; | ||
Assign / change a rule's set to accounts in the created global domains; | ||
Detach accounts from created global domains | ||
Rule' set | View the list of preconfigured and added rules (Table 2); | |
Add and edit new rule's set; | ||
Notifications | View notifications; | |
Add, edit, and delete notifications | ||
Monitoring | View information and status of connected services, components, and systems | |
User | Last events | View list of last events; |
View event details; | ||
Filter events | ||
Events archive | View archived events; | |
View event details; | ||
Filter archived events | ||
Search | Search by face and body image, face ID, face event ID, external face ID; | |
Filter events | ||
Lists | View lists | |
Verification | View verifiers list; | |
Test verifiers; | ||
View verification result | ||
Event sources | View event source list; | |
View video streams | ||
Tasks | Create tasks; | |
View tasks list; | ||
View task result; | ||
Cancel tasks; | ||
Configure parameters of tasks Time tracking: | ||
- View reports; | ||
- Create reports | ||
Notifications | View notifications; | |
Add, edit, and delete notifications |
Registering a new user account#
All user accounts are created by the administrator of the Service. It is also possible to create a user account without sending a link to his email address, with an explicit password in the Service.
The ability to set passwords in the web interface of the Service is configured through Luna Configurator.
For more information about the LUNA CONFIGURATOR, see “VisionLabs LUNA PLATFORM 5. Administrator Manual”.
The administrator adds a new Service user, specifies the data of this user (full name, email, position, role). The user receives an email containing a link to activate the account. An example of an email is shown in Figure 1.
Authorization in Service#
The Service is accessed by logging in to the website in a web browser. An administrator in Clementine 2.0 version 2.12.0-rolemodel-alpha
can create any type of user, both administrators and users.
For authorization in the Service, enter your credentials (email and password) in the appropriate fields and click the “Login” button. Authorization form is launched when the user logs first time into LUNA CLEMENTINE 2.0 (Figure 1).

When logged in, the user is taken to the “Last events” section (Figure 2).

Sign out of account#
To log out of your account, click the arrow
on the right of the user’s avatar. Click the “Exit” button (Figure 3).

After clicking on the “Exit” button, the user is moved to the authorization form (Figure 1).