Workflow catalog and ownership

Every workflow in Port is automatically represented as an entity based on the _workflow system blueprint. This lets you assign team ownership to workflows and control access using Port's standard blueprint permissions model.

The _workflow blueprint

When the workflow catalog feature is enabled for your organization, Port provisions a _workflow system blueprint and syncs all of your workflows to it as entities. The catalog entry for each workflow stays in sync automatically: when you create, update, or delete a workflow, its catalog entity is updated accordingly.

The _workflow blueprint is read-only from the entity API perspective. You manage workflows through the Workflows API or the Port UI - the catalog entities reflect the current state of each workflow but cannot be edited directly.

Blueprint properties

Each workflow entity in the _workflow blueprint carries the following properties:

Property	Type	Description
triggerTypes	string[]	The trigger types configured on the workflow (e.g. SELF_SERVE_TRIGGER, EVENT_TRIGGER)
nodes	object[]	The full list of nodes that make up the workflow
connections	object[]	The connections between workflow nodes
category	string	An optional category label used to group the workflow
description	string	An optional description of what the workflow does
versionIdentifier	string	The identifier of the latest workflow version (e.g. wfv_abc123)

These properties are system-managed. Attempts to modify them via the entities API will return an error.

Team ownership

The _workflow blueprint supports direct team ownership. You can assign one or more owning teams to a workflow by updating its entity's teams in the catalog.

Assigning ownership gives a team visibility into and, depending on your permissions configuration, control over the workflow. This follows the same ownership model used across the rest of Port's catalog.

To assign owning teams:

1. Navigate to the catalog and open the Workflow catalog page.
2. Find the workflow entity you want to update.
3. Edit the entity and set the Owning Teams field.

Admins always have access

Admins can always read and modify any workflow, regardless of ownership or permissions configuration.

Catalog-level permissions

The _workflow blueprint's permissions model controls read and write access to workflows:

• Read permissions - determine which users can view a workflow (see it in the UI or fetch it via the API).
• Write permissions - determine which users can create, update, or delete a workflow.

These are distinct from execute permissions, which control who can trigger a workflow run from the self-service hub.

Configuring permissions

Permissions on the _workflow blueprint follow the same structure as permissions on any other blueprint. You can restrict access by role, by team, or using a policy expression.

To configure permissions:

1. Navigate to Data model in your portal.
2. Find the _workflow blueprint and open its Permissions panel.
3. Set read and update permissions as needed.

Protected system blueprint

The _workflow blueprint cannot be deleted, and its schema cannot be modified. You can configure its permissions and set owning teams on individual workflow entities.

Related pages

• Dynamic permissions (execute) - control who can trigger a workflow run.
• Default blueprints - full reference for Port system blueprints.
• Manage users and teams - set up teams for ownership assignment.