ClientManagerBlazor · How To · extracted from source, not guessed

Document Library Access Control

REYESCO's own internal reference/guide repository — not a per-tenant feature. For a tenant's own internal documents, see the Knowledge Base guide instead.

Who this is for

Side menu → Document Library. Limited to REYESCO's own internal site — any other tenant sees a plain notice instead of the library. It holds REYESCO-authored reference material for internal staff, distinct from a tenant's own Knowledge Base.

Reaching the library at all: the page-level grant

On Roles & Permissions, a Role needs the Document Library grant to see the nav item and open the page — the same ordinary grant mechanism as any other side-menu item.

Restricting one entry to a specific Role

When adding or editing an entry, set Restrict to Role to lock it to one Role. Leave it unset for anything everyone with library access should see.

Worth knowing: a restricted entry doesn't just gray out for someone outside that Role — it's filtered out of the list entirely, so they can't tell it exists. The same check re-runs on the actual download, so it can't be bypassed by a direct link either.

Granting full access across every restriction: Docs Reader

On Roles & Permissions, check Document Library Full Access on any Role. Members of that Role see every entry regardless of which specific Role it's restricted to — a full-access bypass scoped to just this one feature, not a general RBAC override. They still need the ordinary page-level grant from step 2 to open the library at all.

Example: a "Docs Reader" Role with Document Library Full Access checked, granted to someone who needs to reference every internal guide without being added to every individual restricting Role.