Working together in a shared item
Everyone with access opens the same item, not a copy of it. This page describes what that looks like on screen: who is shown as present, what refreshes on its own, what a viewer cannot touch, and how Judicio stops two people from overwriting the same draft.
Nothing here needs to be turned on. It is how a shared item behaves once a second person has access.
The avatar stack
The stack sits immediately to the left of Share in the item's header, in every one of the seven workspaces. It shows the owner first, then each collaborator, up to four faces before the rest collapse into an overflow count.
| Control | Where | What it does |
|---|---|---|
| Avatar stack | Header, left of Share | One face per person with access, owner first. Hovering a face names them. |
| Green status dot | On an avatar | That person has the item open right now. Its label reads Viewing now. |
| Share | Header | Opens the share dialog. See Sharing a work item. |
| Transfer control | Header, right of Share, owner only | Opens Transfer ownership. See Transferring ownership. |
The whole cluster is absent until the item is shared with you or by you. An item nobody else can open shows no avatars and no Share button.
Presence is drawn from live connections, so a face gains its green dot when a colleague opens the item and loses it when they close the tab. Someone with access who is not reading the item right now still appears in the stack, just without the dot.
What refreshes on its own
You do not reload the page to see a colleague's work. While the item is open, Judicio pushes changes into it as they land:
- A follow-up question and its answer.
- A saved draft edit, an edited matrix cell, a renamed item.
- A re-run's progress, as it streams.
- A change to who has access, so the avatar stack stays honest.
If your access is removed while you have the item open, Judicio tells you Your access was removed and returns you to that workspace's home rather than leaving you on a screen you can no longer load.
The draft edit lock
Drafting and the draft surface inside Research take a soft lock while somebody is editing.
One person starts editing
The first person to edit holds the lock. For them nothing changes.
Everyone else goes read-only
The editor turns read-only for every other collaborator and a notice above it names the holder. The notice is the person's name followed by is editing, with no other wording.
The lock releases
When the holder finishes, the editor unlocks and the notice disappears. If the holder simply closes the item, their lock is dropped rather than left stuck.
Review Matrix cells are not locked. Each cell is independent, so collaborators can work different cells at once and every grid refreshes as edits land.
Judicio does not do simultaneous same-document typing. Two people cannot type into one draft at the same moment, by design. Updates are pushed into open sessions instead, and the lock hands the draft over cleanly.
What a viewer cannot do
Viewer is a complete, live, read-only seat. A viewer reads every result, follows progress live, opens the item's source files, and exports. What is withheld is anything that changes the item.
| Surface | What a viewer loses |
|---|---|
| Session composer | Disabled. No follow-up questions, no chat turns. |
| Item title | Not editable, so a viewer cannot rename the item. |
| Drafting editor | Permanently read-only, marked View-only access. |
| Assistant Draft tab | Withheld in Timeline, Review Matrix, Case Strategy and Research, because generating a draft changes the run. |
| Review Matrix | Add question, add documents and remove document are disabled, each explaining View-only access. Bulk actions that change the matrix are off. |
| Document Review | The accept and flag controls on findings are disabled. |
| Case Strategy | The follow-up chips are disabled. |
Export stays available to viewers everywhere. So does search, filtering and switching views.
Attribution
Every contribution records who made it, so an item is the record of the team's reasoning rather than the owner's alone. Follow-up turns, thread messages, draft edits and cell edits all carry the person who made them, and they stay attached to the item if that person later loses access.
Whose credits are spent
A collaborator who runs something billable, a follow-up or a re-run, spends from the same balance as the owner and the usage is recorded against them. See Credits explained.
Next steps
- Sharing a work item - the share dialog and the full permission matrix.
- Transferring ownership - hand the item over entirely.
- Shared with me - where a colleague's item lands for you.