Defining Permissions

Defining Permissions

You need to setup Permissions in order to define what type of resources your Targets will be allowed/denied to access.

Currently, only the resource Dashboard, Device and Run User are available.

You can add more resources as wished. 

An operation OR is applied. Therefore, as you add more permissions, more resources will be included for verification.

If you use one permission with Deny, it will override any options using an Allow that contains the same condition. 

Type of Fields

Target matching is performed on one of these ways:

  1. ID =  select a specific dashboard from your account (Only the dashboards that you own are listed) 
  2. Tag =  the permission is based on the tags from the users (you can edit these tags in the USER section)
    • Tags are composed by two fields: 'Tag key' and 'Tag value'
    • You can manually edit the tags for each dashboard, or run scripts for that. 
    • For example, Joe Doe contains the 'Tag key = user_level', and 'Tag value = supervisor'. If you create a policy with a Target using the same tag, the permission will be granted for Joe.
  3. Tag Match=  the match is automatically by searching for those tags presented in the Dashboard and USERS.  The Tag Match option reduces the number of policies as you can create a single Policy that would grant access to all users that match the same tags of the dashboards.
  4. ANY = make all your dashboards to the selected Targets. Dashboards shared by others with you will not be included.

    • Related Articles

    • Defining Targets

      You should define Targets in each policy that are used inside the Access Management module (AM). Targets can be users or things (scripts).  Targets are to whom or to what you are giving the permissions. Currently, you can only select RunUser as ...
    • Creating a Policy

      You can create individual policies to securely grant access to certain resources in your account for pre-defined targets.  You create Targets (e.g. users) and determine which type of resource Permissions (e.g. dashboards) they will have.  You can ...
    • Access Management

      Access Management (AM) is a module that helps you securely grant access to certain resources in your account. You create Targets (users or things) and determine which type of Permissions for the resources they will have.  Some examples of how AM can ...
        Take a look at our updated roadmap here!
          What would you like to see on TagoIO?

            Future and past Webinars