About working together

In short: everyone works on the same records, each in their own session. Your saves are stored at once; your colleagues’ saves reach your list when you click Refresh; and the bell tells you when there is something to refresh for.

One session each, one set of records

Each engineer who opens a structure gets their own cloud computer, so one person’s work never slows another’s. All of them read and write the same project records.

AerTwin runs a limited number of sessions at the same time. When all are in use, the next person waits in a queue and is connected as soon as one frees up. When you leave a structure, its session is freed for a colleague within about two minutes — so leave when you have finished rather than keeping the tab open.

When changes arrive

Change	When others see it
Your save	Stored at once, for everyone
A colleague’s save, in your Observations list	When you click Refresh. The list never changes by itself, so it never moves under your cursor
A colleague’s save, in Team activity	Usually within about a minute, with the bell’s count

When a colleague has saved a newer version of a finding than the one you see, the Observations panel says that your list may be behind, with its own Refresh button.

No silent overwrites

If two people edit the same finding, the second Save is refused rather than overwriting the first. The second person keeps their typing, compares it with the saved version and decides what to keep. See Resolve a conflicting edit.

Roles

Each person has a role on each project — Viewer, Inspector or Admin — that decides what they can change. Roles are checked each time something is saved, so a changed role takes effect at once. See Roles and permissions.