---
title: "Boss’nX role: limit visible datapoints with “Show only”"
description: "Hide datapoints from a Boss’nX role: restrict a component or a component type by tags, choose the whitelist mode and check which datapoints stay visible."
canonical: https://wiki.can-nx.com/en/guides/boss-role-show-only/
language: en
product: Boss’nX
audience:
  - administrateur
  - installateur
context: "Boss’nX supervision: Users → Roles → Datapoint rules, “Show only” restrictions section"
---

# Boss’nX role: limit visible datapoints with “Show only”

Context: Boss’nX supervision: Users → Roles → Datapoint rules, “Show only” restrictions section

The “Show only” restrictions of a Boss’nX role limit the datapoints offered for a specific component or for a whole component type. A global mode also decides whether unlisted components stay visible or disappear for this role.

Intended for the administrator or installer authorized to edit roles. Components remain subject to the [role’s scope](https://wiki.can-nx.com/en/guides/boss-role-scope-rules/). The right to send commands depends on the [capabilities](https://wiki.can-nx.com/en/guides/boss-role-capabilities/) and the [tag rules](https://wiki.can-nx.com/en/guides/boss-role-datapoint-tags/): adding a datapoint to a visibility list does not grant it a command.

## Choose how unlisted components are handled

Open **Menu → Users**, **Roles** tab, then **Edit → Datapoint rules**. Scroll down to **"Show only" restrictions**, then choose the mode.

| Mode | Scope |
| --- | --- |
| **Unlisted components stay visible** | The restrictions target the listed components or types. The others remain subject to the tag rules and the general scope. |
| **Hide any unlisted component** | Only components covered by a restriction and having at least one matching datapoint can remain visible in the role’s scope. |

The second mode shows a summary of the hidden components, including those covered by a restriction but without a matching datapoint. A component that does not yet have any datapoint is kept in the first mode; in the second, it does not meet the condition of at least one visible datapoint. In both modes, a component whose datapoints are all hidden may disappear from lists, plans, searches and alarms: check the targets and selections carefully.

**Hide any unlisted component** without any restriction shows a warning and blocks **Save** in the bottom bar. Add at least one restriction with the necessary datapoints or go back to the first mode. Also check each rule’s selection: an existing rule may leave no datapoint visible.

## Restrict a specific component

1. Click **Restrict a component**.
2. Use **Search components…**. The results show the name and, when available, the floor, the zone and the number of datapoints; the search covers this information.
3. Click the component concerned. A target marked **already restricted** is unavailable: edit its existing rule.
4. Tick the datapoints to keep. Their tag may appear next to the name to help identify them.
5. Click **Add rule**, available after at least one choice. The restriction joins the role draft.
6. The **Component** card shows the chosen datapoints and the number of selected datapoints compared with the total.

Datapoints added to the component later are not automatically included in this list. Reopen the rule to select the new datapoints you need.

## Restrict a component type

1. Click **Restrict a component type**, then search for and choose the type in **Search types…**.
2. The list offers the tags present on the datapoints of this type, as well as their parent tags.
3. Tick the tags to keep, then click **Add rule**.
4. The **Type** card shows the selected tags. Subtags covered by a parent may appear with **included via…**.

A type rule relies on tags: a parent tag covers its descendants, including those of future datapoints of this type. Untagged datapoints and those whose tags do not match remain excluded from the restriction.

There is only one restriction per type and only one per component. When a component has its own rule in addition to its type’s rule, its rule shows **overrides the type rule**: select there all the datapoints this component needs, because the type’s choices are not added to it.

## Edit a selection

Target menus may open above the button if there is not enough room below. In their search field, **Escape** first clears a non-empty search, then closes the menu when the field is empty. Clicking outside the menu also closes it.

1. On an existing card, click the **Edit rule** pencil. Cards normally show the items already selected; expand them to review them.
2. Tick or untick the datapoints or tags. The list may scroll; **Filter…** appears when it contains more than six items.
3. The filter finds the displayed names and information, without changing the hidden choices. Clear it and review the full selection before confirming.
4. Click **Save selection** to apply these choices to the role draft, which you then save with **Save** in the bottom bar.

**Cancel**, another click on the pencil or collapsing the card abandons the current selection. Starting to edit another card also replaces this pending input.

You can remove all the choices of an existing rule and then click **Save selection**: the card then shows **all hidden**. Check that this result is intended; to restore datapoints, edit the card again and select them.

## Remove a restriction

The **Remove rule** trash icon immediately removes the restriction from the draft, without confirmation. Check the effect of the chosen mode and the other rules before saving: in **Hide any unlisted component** mode, the target may be left without an applicable rule.

As long as you have not saved, **Discard** restores the whole role to its loaded state, including a restriction removed by mistake.

## Save the role

1. Review the mode, each target, the datapoints or tags kept and the tag rules in the same section.
2. Click **Save** in the bottom bar and wait for **Role updated**, then the return to the list.

## Check the result

1. Reopen the role to check the saved values.
2. Have an account concerned open a new session.
3. Check the expected components and datapoints, those that must remain hidden, and the necessary commands.

## Troubleshooting

| Message or symptom | Action |
| --- | --- |
| **Whitelist mode with no rule would hide every component. Add at least one rule below, or switch back to visible.** | Add a restriction with the necessary datapoints, or choose **Unlisted components stay visible**. |
| **No tagged datapoints on this type yet — tag them first, then pick the tags to keep.** | Have the installer check the tags of this type’s datapoints, then return to the editor. For a few untagged datapoints, a component restriction lets you choose them directly. |
| **component no longer exists** | The rule’s pencil is unavailable. Have the component checked; remove this rule that is no longer useful if removing it matches the need. |
| An expected datapoint is still missing | Check its selection, its tag, whether the component has its own rule and the general scope. For a datapoint that must be viewable, also have the applicable tag decisions checked. |
| Save error | Check the reloaded state before a new attempt. |

If the result remains unexpected after these checks, contact support@can-nx.com with the supervision, the role, the component, the datapoints concerned and the expected result.

French labels: **Règles de datapoints**, **Restrictions « Afficher seulement »**, **Les composants non listés restent visibles**, **Masquer tout composant non listé**, **Restreindre un composant**, **Restreindre un type de composant**, **déjà restreint**, **Modifier la règle**, **Enregistrer la sélection**, **tous masqués**, **remplace la règle de type**, **le composant n'existe plus**, **Supprimer la règle**, **Enregistrer**, **Annuler les modifications**.