Build a Process Automation

Persona: Developer

Summary

The Developer joins a workspace, builds process automations within projects, and deploys to scoped clusters.

Receive notification about workspace access — Developer is notified that they’ve been added to a workspace with the Editor role.
Open Workspace — Logs into Hub. Sees only the workspace(s) they are a member of. Opens the workspace.
Workspace Overview — Sees:
- List of projects in the workspace.
- Team members and their roles.
- Available clusters (only clusters that are assigned to the workspace).
Open project — Opens the project. Sees:
- File hierarchy.
- Connected Git repository (if any).
Build a process — Creates or edits a process within the project. Uses available Catalog assets when needed.
Test the process — Tests the implemented process solution on the Canvas and by using Camunda’s SDKs for testing.
Push project updates to Git — Pushes the updates to the connected Git repo.
Deploy the project:
- For Non-Production, deploys the project to the scoped clusters via the Hub UI or API. Only clusters assigned to the workspace can be used as deployment target.
- For Production, deploys via CI/CD pipeline according to the organisation policy.
Iterate — Continues development, deploying iteratively.

Navigate to the workspace — Open a workspace. Get an overview of workspace projects.
Switch Between Projects — Navigates within different projects of the workspace when needed.
Consistent context — All projects share the same workspace members, roles, and cluster visibility.
Distinct Git connections — Each project has its own connection to Git repo.
Independent deployment — Each project can be deployed independently to the same or different clusters within the workspace scope.

A newly onboarded developer who is an Organization Member but not yet assigned to any workspace:

Log In — After log in, the user is navigated to the organisation view, since they are not members of any workspace.
Scoped access to organisation view — On the organisation level the user has basic access according to the Member role.
Navigate to workspaces — On the workspaces page the user sees an empty state communicating that they’re not members of any workspace.
Request new workspace — The user has an option to request a new workspace.
Review Catalog — The user can navigate to the Catalog and review available catalog assets.