Knowledgebase business article search

Create a permission set in ESET Remote Administrator (6.4 and later)


  • Create permissions for users to view, use and edit objects, tasks and licenses in ESET Remote Administrator. Permissions are an important part of Access Rights in ESET Remote Administrator. 
  • In this example, we will create a permission set for a small office scenario where all users can access all tasks and objects except for server settings. You can make changes to this example to create more specific permission sets according to your needs. 


A permission set defines the objects and tasks a user can access in ERA Web Console. Native users have their own permissions while domain users inherrit permissions from their mapped security group.

When you create a permission set, it is associated with a home group, which is a static group of objects, tasks and users that permissions from that set apply to. When you create a new permissions set, the permissions you select in the icon_section Functionality section will apply to all objects from the Static Groups that you select for that permission set. If a user has access to a Static Group, they will also have access to any subgroups of that Static Group.


End of support for version 6.4 and 6.5 of ESET Remote Administrator / MDM

ESET Remote Administrator version 6.5 is currently in Limited Support status and will soon be in Basic Support status. It is expected to reach End of Life status in December 2020.

ESET Remote Administrator version 6.4 is currently in basic support status and is expected to reach End of Life status in December 2019.

The MDM functionality in ESET Remote Administrator version 6 is in Basic Support status as of April 11, 2019. After this date, MDM version 6 will no longer be available for download.

  1. Open ESET Remote Administrator Web Console (ERA Web Console) in your web browser and log in.

  2. Click Admin Access RightsPermission Sets → New.

Figure 1-1
Click the image to view larger in new window

  1. Type a name for your new permission set, the Description field is optional.
  1. Expand Static Groups and click Add Static Group.

Figure 1-2
Click the image to view larger in new window

  1. Select the check box next to each static group this permission set will apply to.

    We have selected the All Static Group in this example, to apply these permissions for all users. Click OK when you are finished.

Figure 1-3
Click the image to view larger in new window

  1. Expand Functionality to view a table of objects and tasks. Use the check boxes next to each object and task to define permissions:
  • Read: Users can view, but cannot carry out the task or assign tasks to an object. Users cannot edit the task or object.
  • Use: Users can carry out a task or assign tasks to the object, but cannot edit the task or object.
  • Write: Users can read, use and make changes to the task or object.

Figure 1-4
Click the image to view larger in new window

  1. In this example, click Grant All Functionality Full Access. Deselect the check boxes next to tasks and objects for which you do not want to allow permissions. In this example, Server Settings are not allowed. 

    Allowing full permissions for all tasks and objects except for server settings will allow all users to perform all necessary actions without the risk of accidental changes to core system settings. 

    You can create more restrictive permissions sets and apply them to specific groups to customize the permissions tructure to your company environment.  

Figure 1-5

  1. The User Groups and Users sections can be used to apply permissions to specific user groups or individual users. Skip these sections if you are not creating permissions sets customized by user. 
  2. Click Finish to save your changes.

Figure 1-6
Click the image to view larger in new window


Was this information helpful?