The section contains all issued and revoked permissions.
The permission profile displays the following data:
Search is carried out in the Permissions section.
Enter in the search box in whole or in part # (Permission number), User, Account, Resource or Description.
Click Extended search and enter one or more criteria in whole or in part # (Permission number) or Comment, select User, Account or Resource.
Select permission state:
Permissions give the right to open RDP, SSH or web-sessions. Permission can be issued both from the section Permissions, and form the User, Resource or Account profile.
Select a user directory.
To search, enter the Name, Surname, Phone number or Email in whole or in part.
Select resource.
To search, enter the resource Name or Address (DNS address / IP address) in full or in part.
If more than one resource is selected, then only domain accounts will be used to access them. If one resource is selected, then both local accounts and domain will be used to access it. |
If you select Continue using user account (it will become available if no account is selected), a user account will be used to connect to the resource. In the case of an ssh connection, you will need to enter user authentication data when entering the resource.
Under the calendar, a time selection tool is available. You can also manually enter dates and times. |
Configure Access Schedule - access restriction time during the day.
If the Active time does not contain the marked parameters, then the resolution will be considered unlimited. |
Configure View account credentials.
If the user for whom permission is created must have the right to view the password or SSH key of the access account on behalf of which the session will be opened, then check the option Allow user to view account credentials.
Viewing account credentials is performed in the Self Service. |
Review the permission details and click Create.
If you need to change the permission settings, then you can return to any step by clicking Back. |
Bulk Revoke of Permissions
Revoke of permission from its profile