Policy folders & visibility

Group policies into folders and control who sees each one.

Folders group policies on the Policies screen (an admin-only screen). Each folder card shows a live count of the policies inside and an optional description, shown on hover via the info icon. Create one with the New folder card; a folder’s + files ungrouped policies into it; its kebab menu offers rename, visibility, and delete.

A policy lives in at most one folder. Deleting a folder never deletes policies — they return to Ungrouped.

What folders change

By default the Policies screen shows the folder cards plus only the ungrouped policies; open a folder to see its contents. Members meet the same folders as section headers in the New request picker, so the grouping you design also organizes the requester’s menu.

Visibility (audience)

A policy can be visible to Everyone or to specific departments, roles, and/or people. The lists combine as a union — matching any one of them admits the person. Admins always see every policy.

Members see only policies whose audience includes them — in the picker, in lists, and at submission. The server enforces it: a direct link to an out-of-audience policy behaves as if the policy does not exist.

Folder audiences

Visibility can also be set per folder (kebab menu → Visibility). The rule is inheritance with override:

1. A policy with its own audience uses it.
2. A policy with no audience of its own inherits its folder’s audience.
3. Neither set — the policy is visible to everyone.

Setting a folder’s audience is the fast way to scope a whole category — e.g. a “Finance” folder visible only to the Finance department.