Roles

1. On senior X Platform, go to Access Control and Security Management > General registers > Roles;
2. Click on Add and fill in the role Name;
3. The select:
   • Receive visit: for the added role to be able to receive visits;
   • Temporary credential: so that the role may be assigned to a person during the issuance of temporary credentials. Usually for visitors;
   • Send email to the visited person: if this checkbox is checked, when a temporary credential associated with this role is issued, the selected visited person will receive an email notifying about the visitor's arrival. The preferential email address of the person will be used. This option is only available when the Temporary credential checkbox is checked;
   • Index photo of associated people: this option is shown to clients who have the facial recognition and the photo indexing enabled. Upon checking this checkbox, all people who have this role will have their photos indexed. Please note that this operation may generate additional costs (both when activating and deactivating photo indexing);
   • Integrated: This check box is read-only and indicates whether the role was created by the Ronda senior X integrator. If it is selected, the user will not be able to edit the role name or delete it.
   • Import integrator holds: this option will only be displayed if the client has integration with the Ronda Senior and/or People Management systems | HCM. If it is checked, any absence registered on the mentioned systems will suspend the role in question. Using this check box, the client informs in each role whether he would like the suspensions carried out in the roles of the mentioned systems to also apply in Ronda senior X. By default, all roles coming from the integrator already have this check box selected , and it cannot be deselected. However, if the role was created by Ronda senior X, it is possible to edit this selection.
4. Click on Save.

To delete roles, in Role consultation, click on List all or fill in the Search field to find the role, click on the desired role and, at the end of the screen that opens up, click on Delete.

After registering the role, define the validations that the people and vehicles associated with it will control. Click on Edit and set an item as Enabled for it to be controlled during the access validations of the person.

If a role has any items set as Not set, the system will consider their definitions from other roles that the person has and/or the settings defined for the location. After choosing the validation options, click on the Save button.

Validations:

• Check level: controls the access levels, checking whether the ID Card is carrying out an access according to the logic order between the locations, defined by their levels;

• Check antipassback: activates the AntipassbackAntipassback is the name given to a number of features in the access control system designed to prevent users from giving their credential to another person trying to obtain access authorization. Examples of the use of anti-doubling can be: in a parking lot, when the administrator wants to prevent unauthorized people from using free spaces; or as prevention in dangerous areas, where it is important to know exactly who is in the physical location at the time of an event or emergency. When using anti-double control, the concept of reader sense is introduced. This means that a configuration allows the reader to identify whether the event is an "input" or an "output" event. Therefore controlled areas must be registered, and both the person and the areas must be configured to enable this control. The respective readers must be configured so that they indicate to which controlled area they go in and go out. control, preventing the same ID card from accessing the same direction twice (entry or exit) in a short time interval. When activating this control, a window will be shown requesting the Antipassback expiration time, in minutes;
• Check access credits: when active, this validation determines that the role will control its access through credits;
• Controls the person's time slot: associates the person's time slots with the paper, which can come from the screenSlots,Release of the person's time slot and/or thetime slot control of the Senior Round). If it is active, validation is done based on the associated scale (which defines the time slots per day);

• Check location timeslot: associates a timeslot with a location. Then, if this control is active, the validation is done by the timeslot of the location that is being accessed;
• Check in-between workdays: controls the entry of workers obeying the in-between workdays rules and the access configurations of the physical locations. When Activated, the configuration of the following fields will be requested:

• Tolerance time (minutes), which corresponds to the tolerance time for pauses. If a worker takes a break longer than the value defined in this field, the system will block his/her access and consider the start of the in-between workdays period;
• In-between workdays duration time (hours), which refers to the minimum break time between the end of an in-betweek workdays period and the start of a new one.
Example:

Joseph has a tolerance time of 120 minutes configured for his Worker role. After taking a break of 180 minutes (3 hours), Joseph's access will be blocked and he will have to wait for the in-between workdays duration time configured on the system with the 12 hour value to have his access allowed again.

When Disabled, the in-between workdays is universally disabled for the worker, regardless of it having other roles for which this control is active.

Example:

Renato has the role of Contributor configured with interwork controlActivated and also has the role of Director, configured with inter-day control asDisabled. This way, Ronald will have his access released at any time, not obeying the in-between workdays rule, as the control is disabled in a universal manner by the Director role and overlaps the configuration of the Worker role.

When Not set, the in-between workdays is individually disabled for the role in question, not interfering in other roles that may have this control active.

• Check permission: if this control is active, the role may only access the authorized physical locations or locations which have devices that are associated with the role. Upon enabling this validation, you can define the physical locations and/or the device readers;

• Customized validation: enables the role for customized access validations.

After registering a role, manage its permissions.

Operations likeTo view,Include ,To edit It is Delete Certain types of information can be activated or deactivated for a registered role. This will determine what information can be accessed or changed by users who have this role in the system.

For a screen to be visible to the user, they must have permissionTo view corresponding to that screen. If he is only allowed toInclude a registration, for example, the screen for that registration will not be shown.

The total permission of the user for the system functionalities will be equal to the sum of the permissions from all of his/her roles.

After registering the role, add, edit or delete its ranges, limiting the registers that may be viewed by people associated with it. If the role needs to view only certain groups, locations, roles or organizational structures, make this restriction by filling in the fieldsAdd paper, Add location , Add group,Type of occurrence, Add company , Add branch , Add cost center , Add job title , Add org chart , Add other companies It is Add contract.

In General registers > Roles, in the People section, click on Manage people who have roles. Then, in the Add person field, find the person you want to add to the panel by name, click on him/her and the person will be associated with that role.

To delete a person, in the same location, click on Edit and then on the trash can icon in the row corresponding to the person that must be deleted.

1. Go to General registers > People and click on the register of the person from who you want to suspend a role;
2. In the register of this person, find the Roles section and then click on Edit;
3. In the role list, click on the role which must be suspended. This will show the suspensions already registered for it;
4. Click on the Add button in the Suspensions item;
5. In the window that opens, fill in the Start date of the suspension and the Note describing its reason, for example. If the start date of the suspension is earlier than or equal to the current date, the Start date field will be disabled;
6. The End date is optional. Fill it in if you want to define a date on which the suspension will end. If this field is not filled in, the suspension will last indefinitely;
7. To finish the registration, click on Save.

A physical location may or may not consider role suspensions, depending on its definitions. It may be defined, for each physical location, whether it will control suspensions for the people accessing them.

1. On senior X Platform, go to Access Control and Security Management > General registers > Physical locations;
2. Select the desired location and click on View;
3. In the Validations section, verify whether the Check role suspension (absences) item is enabled or disabled;
4. To modify this option, click on the Edit button of the Validations section and change the value of the Check role suspension (absences) item. Click on the Save button to confirm this change.