How do I control who can see which documents?
Use site membership and role permissions as the primary FormKiQ access boundary, then add supported folder restrictions, shares, or OPA policies where needed. Test content and metadata operations separately. In v1.19.2, folder restrictions do not hide all metadata-by-ID access from a site reader, so use separate sites when that metadata must also be isolated.
Start with the site boundary
Map users and services to only the sites they need. Automatic Sites derive grants from groups; commercial Defined Sites use explicit site/group permission assignments. Keep administrators and broad integration identities out of ordinary-user acceptance tests.
Folder permission entries accept READ, WRITE, and DELETE. GOVERN is a site/governance permission, not a folder entry value. When entries are present, ordinary unlisted roles lose folder content access; a dialog's contrary helper text does not change backend authorization.
Verify each access path
Test lists, search, known document IDs, metadata, file URLs, artifacts, and shared-folder access. The v1.19.2 metadata-by-ID caveat matters for confidential document names and attributes even where file content is restricted.
Use OPA for supported attribute-based decisions after defining trusted attributes and policy behavior. Review issued presigned URLs separately: revoking a group or share does not necessarily revoke an already issued, unexpired transfer URL.
Edition and configuration
Core supports site-based access. Defined Sites and advanced folder/governance capabilities require the commercial deployment; OPA availability and enforcement coverage must be confirmed for the installed configuration.