Home / Edit BPMN together – Process Studio Team

Edit BPMN together – Process Studio Team

Process Studio Team

One process.
Several minds.
At the same time.

Several people edit the same BPMN diagram at the same time. The colour shows you who is working on what – not the version that turns up in your inbox at the end of the day.

BPMN 2.0Presence in real timeSeparated by tenantSearch inside the diagramFull screenDE/EN/FR/ES
TAOM PROCESS STUDIO · TEAM TEAMGoods receipt DATAMA Warehouse operator Receive goodsTask ×Quantity correct? Put awayTask Daniela Thomas Marco ANAndrea would like to join.Come inLater One diagram. Everyone at once. The colour shows who is working where – not the version that lands in your inbox at the end of the day.

At the same time, in different places

Two cities. One diagram.

Nine in the morning in New York is three in the afternoon in Zurich. Both are at their desks, both in the same diagram – nobody hands anything over, nobody waits for the next morning.

NEW YORK09:14 — Sarah is in the model ZÜRICH15:14 — Daniela too, the same minute ONE WORKSPACE · GOODS RECEIPT NYZH Receive goods Put away Sarah Daniela Six hours apart. One shared window of time. Not one after the other, but together: what one changes, the other sees at once.
1file – not one per person
0versions to merge afterwards
3 sec.until someone else\u2019s change is visible
4languages: DE, EN, FR, ES

What is different here

Three things happening at once.

No sequence, no steps – that is the point. It all happens at the same time, in the same diagram.

DA

See who is there

Everyone has a colour. It sits on the element they are editing and appears as their initials in the toolbar. One glance tells you where someone is.

AN

Knock instead of barging in

Anyone who wants to join knocks first. The person inside the diagram decides and lets them in. Nobody turns up unannounced in a model someone is still thinking about.

MA

Nobody overwrites anyone else

The element someone is editing is briefly locked for the others. The same label cannot be written twice – there is nothing to reconcile.

Two people, one diagram

So that you are talking about the same thing.

Modelling together rarely fails because of the model. It fails because two people are looking at different places and do not notice.

🔍

Search: look where the other person is looking

“Take a look at the approval step” – type the word, press Enter, the hit is highlighted. The search covers the label, the description, the TAOM identifier and ERP functions. With fifty steps across six lanes, that is the difference between pointing and scrolling.

Full screen: room for the whole process

One click and the canvas takes over the whole page – no header, no panels. Made for shared screens and the projector in the meeting room, where every centimetre counts. Esc brings everything back.

Both belong to the Webuser Pro tier – the same one Team requires.

Honestly

What does not happen here.

Most of the time spent modelling together does not go into the modelling itself, but into everything around it. That is exactly what disappears.

  • No file by email, no “final_v3_commented.bpmn”.
  • No merging two versions afterwards.
  • No question about which version is the current one.
  • No waiting until someone else is finished and releases the file.
  • No guessing who made a change – origin and history are held in the file itself.
  • No other companies’ diagrams in the list: tenants are separated, including the documents.

When several people look inside

Together does not mean open to everyone.

Collaboration stops at the company boundary. That is not a setting somebody can forget – it is the foundation the list is built on. What the belonging rests on and how it is checked is described in the Trust Center; what the team licence covers is on prices and packages.

Separated by tenant

A company’s workspaces stay among themselves. Anyone outside sees them neither in the list nor through the identifier – and neither the documents attached to the elements.

Deleting stays with the owner

Colleagues may open and edit. Only the owner may remove a workspace for good – and administrators.

Traceable in the file

Origin, workspace and change history are held in the BPMN file itself, not in a database beside it. Years later it is still clear where a model came from.

Frequently asked questions

Answered briefly.

Can several people work on one BPMN diagram at the same time?
Yes. Everyone opens the same workspace. Who is working on which element is shown by their colour and initials. The element someone is editing is briefly locked for the others, so the same label cannot be written twice.
Do changes have to be merged afterwards?
No. There is only one file. When someone saves, the others follow. No second versions appear that would have to be reconciled later, and no file is sent by email.
How do you find a particular element in a large diagram?
With the search in the toolbar. It covers the label, the description, the TAOM identifier and ERP functions; Enter jumps from hit to hit. Search, like full screen, belongs to the Webuser Pro tier.
Can one customer see another customer’s diagrams?
No. Workspaces are separated by tenant. Anyone from a different company sees neither the diagrams in the list nor through the identifier. The same applies to the documents attached to elements.
What does Process Studio Team cost and what is required?
Team is an additional licence and requires at least the Webuser Pro tier. The team window is visible on every tier; without a licence it shows example data together with a note.

Try it before you buy.

The team window is built into every edition of Process Studio. Without a licence it shows an example – so you can see how it looks before you decide.

Request a live demo