Skip to main content
Workspace admin

Setting visibility scope

Visibility scope decides who can open an orchestrator and the documents under it. Every kind has the same Visibility Scope tab — an administrator surface, since it needs permission to read your organisation's roles, departments and groups.

What you'll need
  • The IntelieDocs module visible in your left-hand navigation.
  • Permission to read roles, departments and groups — without it the tab shows a full-screen permission error, not empty pickers.

If IntelieDocs isn't in your navigation, your role doesn't have visibility for it — ask a workspace administrator, or see Permissions and module visibility.

Steps

  1. Open the orchestrator and select Visibility Scope in its tab list.

  2. Leave Unrestricted / all internal users on for everyone in your tenant. Turn it off to restrict, which reveals the pickers; turning it back on empties every list.

  3. Work through the Roles, Departments, Groups and Users dropdowns — each has a Search by name filter. Ticked entries appear as chips below, under Selected Roles and its counterparts.

  4. Take a chip out with the cross on it. There is no Save button — every tick and removal is written straight away.

What success looks like

  • A confirmation appears for each change, for example Role added to visibility scope.
  • Each panel lists exactly the entries you picked; an untouched one reads No roles added yet.

Who the Users list offers

Users is not your full user directory: it offers only people whose role already grants view permission for that kind of orchestrator. Eligibility is per kind, so someone offered on a Smart Extract can be absent on a Smart Redact.

If something goes wrong

SymptomLikely causeWhat to do
The tab is a permission error, not the pickers.Your role cannot read the roles, departments and groups directory.Ask an administrator to grant it — see Roles.
A colleague is missing from Users.Their role does not grant view permission for this kind of orchestrator.Give them a role that does, then reopen the tab.
Could not update visibility scopeThe change was rejected and rolled back.Reload the tab to see the real state, then try again.
An entry you added shows no chip.Very large directories load one page at a time; an unresolved entry is dropped.Confirm it still exists, then add it again.

Next

Steps verified against elie-tenant-ui 0.1.2 on . Something wrong with this page?