Role-Based Access Control and Artificial Intelligence Policies
Distinguish access to Policy from the runtime permissions expressed by an authored policy.
Policy combines guided authoring, review decisions, governed revisions, and delivery evidence. Refer to Understand Policy for the canonical conceptual references. Refer to Start here for an ordered learning path.
Policy supports the following responsibilities:
Supported authoring choices and available interface actions depend on your release and authority. Use the corresponding task guide rather than inferring support from a conceptual example. The API reference distinguishes operation contracts from interface presentation.
Refer to use cases for author, reviewer, operator, and integration journeys.
The deployment guides target Kubernetes with the required Protegrity platform integrations. They do not establish support for arbitrary standalone platform combinations.
Operators need the release’s platform, storage, gateway, identity, and integration prerequisites. PostgreSQL runs inside the Policy stack. Authors and reviewers need the capabilities for their assigned tasks. Refer to installation and access preparation.
Refer to Architecture for component responsibilities and delivery boundaries.
Use these references for shared definitions:
Distinguish access to Policy from the runtime permissions expressed by an authored policy.
Was this page helpful?