Help center Get started Knowledge center Product documentation API documentation
Account Admin
Getting started
How to navigate the Admin tab How to set up a new workspace How to work out why a user can’t see something
User Management
How to create a user How to assign a role to an existing user How to edit a user’s profile How to reset a user’s password How to deactivate or reactivate a user How to delete a user How to give a user access to more than one organization
Roles Management
How to create a role How to edit a role How to assign a security tag to a role How to delete a role
Group Management
How to create a group How to create a subgroup How to edit a group How to delete a group
Organization Management
How to create an organization How to configure organization filter parameters How to edit an organization How to delete an organization
Security Tags
How to create a security tag How to edit a security tag

How to assign a security tag to a role

Assign a security tag to a role, then apply that tag to a column in a custom script. Together these control how the column’s values are presented to people holding the role.

Before you begin

You need:

  1. The Account Admin role for the role assignment in Step 1
  2. The tag already created in Admin → Security Tags, with its options set. See How to create a security tag
  3. Access to the custom script containing the column, and the Designer role to edit it. If that’s someone else, they do Steps 2 through 5.

A security tag operates on a column, not on a Report. Applying one doesn’t hide a Report or remove it from anyone’s Dashboard. The Report still opens, and every column is still there. What changes is how the values in the tagged column are presented to people holding the role.

That makes one Report serve audiences with different data entitlements. The same Report shows raw values to a role without the tag and deidentified values to a role with it, and nobody needs a second copy.

The tag has to be in two places to do anything:

  1. On the role, which is what Step 1 covers
  2. On the column, in the custom script, which is Steps 2 through 5

Configured in one place only, the tag has no effect and produces no error. It simply doesn’t apply.

Steps

Step 1. Assign the tag to the role

From the main navigation, click Admin, then open the Roles Management tab. Search for the role and click the Security icon in its Settings column.

In the Security Tag pop-up, check every tag this role should carry. A role can hold multiple tags. Click Save.

Step 2. Open the custom script

Open the custom script containing the column you want to tag.

Work out which one first if you’re not sure. The tag has to go on the column in the custom script the Report is actually built on. Tagging the same column name in a different source does nothing for this Report.

Step 3. Open the column

Double-click the column you want the tag to apply to.

Step 4. Add the tag

Add the security tag to the column.

Step 5. Save

Save the custom script. The tag is now live on that column.

Result

Users holding a role carrying the tag see the tagged column according to the tag’s configuration, deidentified, for instance everywhere that column appears. Users whose roles don’t carry the tag see the column as it normally is.

The Report itself is unchanged for everyone. It opens for anyone with access to it, with all its columns present. Only the treatment of the tagged column differs by role.

Common issues

  1. I applied the tag and nothing changed for the user. The tag has to be on both the role and the column. Check the role’s Security pop-up and the column in the custom script, one without the other has no effect.
  2. The tag isn’t in the Security pop-up. It hasn’t been created yet. Create it in Admin → Security Tags.
  3. The column looks right in one Report and wrong in another. The second Report is built on a different custom script. The tag applies to the column in the script you tagged, not to every column with that name.
  4. The user can’t see the Report at all. That’s not the tag. Tags govern how a column is presented, not whether a Report opens. Check Reports Access on their roles.