- Scope: Organization level
- Purpose: Internal catalog for discovering, managing, and governing reusable automation assets.
- Relevant Personas: CoE Admin, CoE Developer, Developer
Overview
The organization-level Catalog page is where the Center of Excellence (CoE) manages the master library of reusable automation assets. It lists all Catalog Assets across all statuses, and provides tools for submitting, reviewing, and governing resources that will be made available to teams.
The catalog supports six resource types: Connectors, Element Templates, Forms, DMN, RPA, and Process Templates.
Approval Workflow
Every resource submitted to the catalog goes through an approval process. Each item has one of three statuses: Approved, Pending, or Rejected. Admins and catalog managers can approve or reject pending items via overflow menu actions. Developers only see approved items plus their own pending submissions, and can cancel their own pending requests.
Role-Based Visibility
| User Role | Visibility | Actions |
|---|---|---|
| Developer | Approved items + own pending submissions | Submit new, cancel own pending |
| Catalog Manager | All items (approved, pending, rejected) | Approve, reject |
| Organization Admin | All items | Approve, reject, full management |
Catalog Asset Detail
Clicking an asset opens its detail page with full context for evaluation:
| Section | Description |
|---|---|
| Header | Large icon, title, status tag, short description |
| Preview Image | Visual preview of the resource (SVG fallback) |
| Features and Benefits | Long-form description of what the resource does |
| Documentation | Technical documentation for the resource |
| Tags | Associated tags for categorization |
| Details Sidebar | Type, category, version, last updated, version compatibility, submitted by, approved by |
| Support Links | Knowledge Base, API Documentation, Website |
| Install to Workspace | Button to install the resource into a Workspace |
Admins see additional Approve/Reject buttons for pending items.
Persona-Specific Behavior
- CoE Admin / Catalog Manager: This is a core governance page. Use it to curate the catalog — review submitted resources in detail, approve or reject them, and control what’s available to delivery teams.
- CoE Developer: Submit new assets for approval and track their status.
- Developer: Discover approved resources, evaluate suitability by reviewing documentation and compatibility, then install into a workspace.
See Also
- Catalog — entity definition (dual-level concept)
- Catalog Asset — individual resource properties and lifecycle
- Workspace Catalog — the workspace-level counterpart