> For the complete documentation index, see llms.txt.
Skip to main content

Check out Port for yourself ➜ 

Governance across pillars


Port's governance model spans multiple product areas. Rather than centralizing all controls in one place, each pillar provides its own access controls and guardrails. This page links to the relevant documentation for each governance dimension.

Entity & catalog permissions

Control which users and teams can view, create, edit, or delete entities in your context lake. You can apply permissions at the blueprint level to restrict access by role or team membership.

For full documentation, see the Govern data access page.

Workflow permissions

Control who can build a workflow and who can see and trigger it. Permissions can be based on Port roles, specific users, team membership, or dynamic policies evaluated at runtime.

For full documentation, see the Manage a workflow page.

Agent scope & controls

Configure which LLM providers power Port AI, set data access boundaries for AI agents, and enforce security policies across AI-driven workflows.

For full documentation, see the AI security and data controls page.

Port interface page permissions

Control which users and teams can view or edit catalog and dashboard pages in the platform interface.

For full documentation, see the Page permissions page.

Scope building permissions across teams and users

See how the same team-based and dynamic policy model that governs your catalog extends to who can build and run workflows, scorecards, and other resources in Port.

For full documentation, see the Scope building permissions across teams and users page.