Process map
Processes > Process map holds the tree of your organization's business processes, from macroprocesses down to subprocesses. Each process has an owner, a responsible area, a criticality and the people involved, and automations say which process they serve. This lets Proton show, for each process, what is automated, how the runs are going and what is missing.
It works on any plan, with or without the Quality and Operation modules.
The tree
The tree sits on the left, with the Search process... search (which ignores accents and also shows the processes above the one found). Each process in the tree shows:
- a dot in the criticality color: Critical (red), High (orange), Medium (blue), Low (green) or gray, with no criticality;
- the name;
- how many automations point directly to it (only the ones you can see).
Clicking a process opens its details on the right. When you open the screen, it shows the first macroprocess.
Create and edit a process
New process, above the tree, creates a process; New subprocess, in the details, creates a process right inside the one that is open.
| Field | What it is |
|---|---|
| Name | Required, up to 150 characters. It cannot repeat the name of another process at the same level. |
| Criticality | Not provided, Low, Medium, High or Critical. |
| Description | Up to 5,000 characters. |
| Parent process | The process above. When empty, the process is top level (a macroprocess). A process cannot sit under itself or under one of its own subprocesses. |
| Owner | The person who answers for the process. |
| Responsible area | The business area that answers for the process. Type a new name to create the area on the spot. |
| People involved | Add person adds a person, with their Role in the process (up to 100 characters). |
| Areas involved | Other areas that take part in the process. |
The owner, people and area fields list the records from People and Business areas, and they only load for users who can see those records.
Link an automation to the process
The link lives in the automation: in Automations > Automations, edit the automation and pick the process in the Business Process field. An automation serves one process. See Automations.
Process details
The header shows the path (for example, "Finance / Billing"), the name, the criticality, the Macroprocess badge when the process is top level, and the description. The actions are Edit, New subprocess, History and the trash can.
Below, in this order:
| Section | What it shows |
|---|---|
| Indicators of the last 30 days | Coverage, automations, success rate and documentation, counting the process and its subprocesses. See below. |
| Process diagram | The BPMN drawing, with the status of each task. See Process diagram. |
| People and areas | The owner (with job title and e-mail), the responsible area, the people involved with their role, and the areas involved. |
| Subprocesses | The processes below, with the number of automations in each one. Clicking opens the subprocess. |
| Automations | The automations that point directly to the process. The name opens the datasets, and Document opens the automation document. |
Process indicators
| Indicator | What it counts |
|---|---|
| Covered processes | How many of the processes (this one and the ones below) have an automation. Green at 100%, yellow from 50%, red below that. |
| Automations | The automations of the process and its subprocesses, with the datasets and how many have never run. |
| Success rate | The runs that passed divided by the runs that passed or failed, over the last 30 days. Green from 90%, yellow from 70%, red below that. |
| Documentation | How many components of the automations are documented, that is, have an objective or an expected result. |
Open in traceability opens Traceability already filtered by this process.
:::note Direct numbers and numbers with subprocesses The count in the tree and the Automations list in the details show only what points directly to the process. The indicators and the diagram also add up the subprocesses. For a macroprocess, the numbers may differ. :::
Delete a process
The trash can deletes the process after a confirmation. Delete or move its subprocesses first: a process with subprocesses is not deleted.
When you delete it:
- the automations linked to the process are left without a process (they still exist);
- the people and areas involved are removed;
- the diagram is removed, with all its versions and task links.
History
History shows each change to the process: when, who, the action (Created, Changed or Deleted), the source (In the app, Through the API or By AI) and each field with its value before and after, including diagram version changes and the components linked to each task. The window shows the last 100 changes.
Permissions
| Action | Permission (Processes domain, Process map entity) |
|---|---|
| See the tree, the details, the diagram and the history | View |
| New process and New subprocess | Create |
| Edit, import and replace the diagram, link components to tasks | Edit |
| Delete | Delete |
The automations and the diagram colors follow the team rule: each person only counts the automations they can see.
On mobile
The screen is designed for a computer: on a phone, the item does not show up in the menu, and the link warns that the screen works best on a computer, with Open anyway. When opened this way, the tree sits above the details, and the diagram is view only.
The AI assistant and Proton MCP can also look up and register processes, people and areas, with the same permissions.