Boss’nX role: allow or deny a floor, a zone or a component

The specific overrides of a Boss’nX role allow or deny a precise item of the building (part, floor, zone or component), on top of the standing rules of the scope. A manual deny always wins, including over a grant set lower down the tree.

Intended for the administrator or installer authorized to edit roles. The standing rules grant components by criteria; the role’s capabilities separately define the allowed actions.

Find the item in the tree

1. Open Menu → Users, Roles tab, then Edit → Components & Building, and scroll down to Specific overrides.
2. Look for the Building part, Floor, Zone or Component chips: they show the level of each row.
3. Expand the parts, then the floors and the zones with their arrows. Expand all opens the tree; Collapse all closes it again.
4. Components attached directly to a floor appear under Direct on floor. An empty zone may show No components in this zone.

To go faster, type part of the name in Search floors, zones, components…. The search covers the names of items and parts; it ignores case but takes the accents of the displayed name into account. A match on a parent can reveal its child items: the number of results counts the matching names, not necessarily all the rows displayed.

During a search, the necessary branches stay expanded, even after Collapse all. Clear the search text to return to the general view. Filtering or collapsing removes no override.

Choose Allow, Deny or Auto

Act on the exact row to change:

Control	Effect
Allow	Adds an explicit grant for this item. On a part, a floor or a zone, it also covers the components attached to it, subject to denies.
Deny	Excludes this item. On a parent location, the deny also excludes the components that depend on it.
Auto	Removes this row’s own override. Access again depends on the rules and the other applicable overrides.

On a floor, a zone or a component, clicking an already active Allow or Deny again removes that decision. Auto explicitly returns the row to operation without an override of its own.

A manual deny always wins: allowing a component does not restore its access if its floor is denied. To restore access, check the component’s row, then its zone, its floor and its building part, and remove only the denies to lift.

Allowing a single component may make its parent locations visible so that it can be reached. This does not grant the right to create other items in those locations: creation also depends on the capabilities and on the scope granted to the container concerned.

The manual grant, manual deny, via rule or mixed chips help identify where each row’s access comes from.

Apply an override to a building part

Allow or Deny on a real building part applies to that part and to its future floors and zones. Check that this lasting scope matches the need.

A decision on the part keeps the overrides already set on its floors, zones or components. Auto on this part removes only its own override; the decisions on the children remain in place. For example, after allowing a part and denying its basement, setting the part back to Auto keeps the basement deny.

The No assigned building part group gathers items without a real part. Its controls act on the floors and the directly attached zones of the group; this bulk action can affect items hidden by the search. For a limited change, use the controls of the individual rows and review the list without a search.

Save the overrides

1. Clear the search and review the changed rows as well as their parents.
2. Check the standing rules: a rule covering all components does not remove manual denies.
3. Click Save in the editor’s bottom bar. Saving covers the whole role.
4. Wait for Role updated and the return to the list.

Discard restores all sections to their loaded state as long as the changes are not saved. To abandon them when leaving through Back to roles, confirm leaving; declining keeps the draft.

Check the result

1. Reopen the role and check the decisions kept, as well as the rules and the parents’ decisions.
2. Have an account concerned open a new session.
3. Check a component that must be accessible, a component that must remain inaccessible, then the necessary actions.

Troubleshooting

Symptom	Action
An expected row is missing	Check the supervision and the item’s organization in the building with the administrator or installer.
The controls are unavailable	Have your rights and whether the role is editable checked.
An allowed component remains inaccessible	Look for a deny on its zone, its floor or its building part.
Unexpected access or error after saving	Check the reloaded state of the role before trying again.

If the problem persists, contact support@can-nx.com with the role, the items concerned, the expected access and the checks performed, without any access secret.

French labels: Composants & Bâtiment, Exceptions spécifiques, Rechercher étages, zones, composants…, Tout déplier, Tout replier, Partie de bâtiment, Étage, Zone, Composant, Directement sur l’étage, Autoriser, Refuser, Auto, Sans partie associée, Enregistrer, Annuler les modifications, Rôle mis à jour.