What is attribute-based access control for documents?
Attribute-based access control evaluates trusted user, document, and request attributes to decide whether an operation is allowed. FormKiQ integrates Open Policy Agent for supported document authorization paths. A policy might compare the user's department with controlled document metadata. Configure and test the actual enforcement points; an attribute or policy file alone does not protect every API or derived copy.
Define trusted policy inputs
Decide which identity claims and document fields are authoritative. A user-editable department field cannot safely grant its editor broader access. Protect policy-driving attributes and decide which roles may change them.
Write an explicit allow/deny policy for the intended operation and install it through the documented OPA configuration. Keep site membership, policy evaluation, folder controls, and governance permissions distinct; they solve different authorization questions.
Test coverage and failure behavior
Use positive and negative tests for a known document, search result, metadata request, content download, and any supported derived output. Test missing attributes, conflicting grants, policy errors, and policy-service failure. Confirm the intended failure behavior rather than relying on an untested fallback.
A retrieval index, external integration, exported report, or previously issued presigned URL can have its own access boundary. Apply equivalent controls where those copies are served. Preserve policy versions and test cases during upgrades.
Edition and configuration
OPA is documented as a commercial access-control capability. Confirm its edition, deployment resources, supported API coverage, and policy administration permissions during onboarding.