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 edit a security tag

Change a security tag’s name or its options. An options change reaches everything the tag is applied to, every tagged column and every tagged artifact for every role carrying it, so the effect is wider than editing a single record suggests.

Before you begin

You need the Account Admin role and the name of the tag.

Two kinds of change happen here, and they’re not comparable:

  1. Renaming is cosmetic. The tag keeps its assignments and keeps behaving the same way. The only cost is that anyone used to the old name has to learn the new one.
  2. Changing Secure Options or Report Access Options changes what users see, everywhere the tag is applied, for everyone whose role carries it, at once.

Before changing the options, find out where the tag is in use. That means three places:

  1. Which roles carry it, in Roles Management
  2. Which columns it’s applied to, in your custom scripts
  3. Which Charts and Reports it’s applied to, in Lens → Design — ask your Lens Designers, since this isn’t visible from Admin

A tag applied in several places will change in all of them, and the direction that matters is loosening: a change that reveals more than before exposes data to everyone holding those roles, silently and immediately.

Steps

Step 1. Open Security Tags

From the main navigation, click Admin, then open the Security Tags tab.

Step 2. Find the tag

Type the tag name into the search bar and click Search. Matching tags appear; clear the bar to restore the full list.

Step 3. Check where it’s in use

If you’re changing the options rather than just the name, do this first. Open Roles Management and note which roles carry the tag, then find everything it’s applied to like the tagged columns in your custom scripts, and tagged Charts and Reports in Lens. That list is who and what your change affects.

The Lens side isn’t visible from Admin, so this needs a conversation with whoever owns the Reports.

Step 4. Open it for editing

Click the settings icon for the tag. The edit dialog opens with its current configuration.

Step 5. Make the change

Update the Security Tag Name, Secure Options, or Report Access Options as needed.

Step 6. Save

Click Save. The change applies wherever the tag is used.

Result

The tag reflects your changes, and everything it’s applied to the columns and artifacts alike now behaves according to the new options for every role carrying it.

A rename changes nothing about behavior. The tag keeps its role pairings and its applications under the new name.

Common issues

  1. I changed the options and users see no difference. Ask them to reload the Dashboard. If it still hasn’t changed, confirm the tag is actually applied to something: the column in the custom script the Report is built on, or the Chart itself in Lens → Design.
  2. The change affected a Report I wasn’t thinking about. The tag was applied in more than one place. Options changes reach every application of the tag, so check all three places before editing.
  3. Data that was masked is now visible. The options change loosened the tag. Revert it, then verify with an affected user before trying again.
  4. Search returns nothing for a tag I know exists. Check spelling and case, then clear the search bar and look through the full list.