Managing Tags
Note
Role based access control is an Orkes Conductor Enterprise feature. Managing users, groups, and role assignments is available only to Admins.
Tags organize resources and make access control easier to manage at scale. A tag uses the key:value format and can be applied to workflows, tasks, user forms, event handlers, schedules, secrets, webhooks, prompts, environment variables, integrations, applications, decision rules, and API/MCP Gateway services.
Common tag patterns:
| Tag | Use |
|---|---|
team:payments |
Ownership and team-level access. |
env:prod |
Environment separation. |
app:checkout |
Application or domain grouping. |
data:pii |
Sensitive-data handling and review. |
tier:critical |
Operational priority. |
Assigning tags to resources
Add tags to resources that share ownership, environment, compliance requirements, or permission boundaries. Keep tag names stable and predictable so they can be used in automation and audits.
Guidelines:
- Use lowercase keys and values where possible.
- Prefer a controlled set of keys such as
team,env,app,data, andtier. - Avoid personal tags for production access control.
- Review tag membership before granting broad permissions to a tag.
You can add tags from the UI or through the API.
From the UI, go to the resource's page, select the Tag icon in the Actions column, enter tags in the key:value format, and select Save.
Use the corresponding API to add tags to a resource:
- Workflow
- Task
- User form
- Secret
- Webhook
- AI prompt
- Environment variable
- Application
- Decision rule
- Integration provider
- Integration
- Gateway service
- Gateway service routes
Tags dashboard
Available since
- v5.2.75 and later
The tags dashboard provides a complete overview of all tags in the cluster and the resources associated with each tag. Use it to audit whether tag-based permissions are still scoped correctly.
To view the tags dashboard from Conductor UI, go to Definitions > Tags Dashboard from the left navigation menu on your Conductor cluster.
The page displays the total number of tags in the cluster, along with the count of resources of each type associated with each tag. Use the Quick search box to find a tag, and select a count to see the resources.
Bulk-access to resources using tags
Tag-based permissions let you grant access to a set of resources without adding each resource individually to a group or application. This is useful when many workflows, tasks, secrets, schedules, or gateway routes belong to the same team or product area.
Use tag-based permissions when:
- A team owns many related resources.
- A deployment process creates resources that should inherit access automatically.
- You want permission reviews to focus on a tag membership list instead of hundreds of individual grants.
Do not use one broad tag as a shortcut for cluster-wide access. If a group or application needs cluster-wide power, use the appropriate role and review it as privileged access.
Granting tag permissions
You can grant tag permissions to both groups and applications.
| Target | Typical use |
|---|---|
| Group | Human teams that need read, update, execute, or delete access to tagged resources. |
| Application | Workers, services, CI/CD jobs, or gateways that need programmatic access to tagged resources. |
Permission levels are:
| Permission | Allows |
|---|---|
| Read | View all resources with the tag. |
| Update | Modify all resources with the tag. |
| Execute | Run workflows, poll/complete tasks, or use executable resources with the tag. |
| Delete | Delete resources with the tag. |
Before granting tag permissions, confirm that the resources already using the tag are intended to be included. Future resources that receive the same tag can inherit access through the existing permission grant, so tag assignment should be part of your release review process.
To add permissions to a group:
- Go to Access Control > Groups from the left navigation menu on your Conductor cluster.
- Select the group name or the Edit icon located next to the group name.
- In the Permissions section, select + Add Permission.
- Toggle to the Tag tab and select the tag to provide access to.
- Toggle the access levels for your selected resource:
- Read: Users will be able to view the resource.
- Update: Users will be able to update the resource.
- Execute: Users will be able to execute the resource.
- Delete: Users will be able to delete the resource.
- Select Add permissions.
All users in the group now have access to all resources associated with the tag.
To add permissions to an application:
- Go to Access Control > Applications from the left navigation menu on your Conductor cluster.
- Select the application name or the Edit icon located next to the application name.
- In the Permissions section, select + Add permission.
- Toggle to the Tag tab and select the tag to provide access to.
- Toggle the access levels for your selected resource:
- Read: The application will be able to view the resource.
- Update: The application will be able to update the resource.
- Execute: The application will be able to execute the resource.
- Delete: The application will be able to delete the resource.
- Select Add permissions.
The application now has access to all resources associated with the tag.
Access follows the tag. It applies when the tag is added to a resource and ends when the tag is removed. A user or application can access a resource if it has been granted the access on any one of the resource's tags, or on the resource itself.
APIs
Manage tags programmatically with the Tags API, including adding, listing, and removing tags on resources.