Working on a proposal with other people
What a workspace actually is on this platform, how to bring in a colleague, and the firewall that means they cannot see your evidence.
What a workspace is here
There is no screen on this platform called a workspace. The thing that plays that part is a tracker entry: one entry per opportunity per person, created by pressing Track this application on a record.
That entry is what carries the shared state. It holds a status, a reminder date, notes and a checklist, and it keeps an activity trail of what changed. It is also the only thing on this platform that can be shared with another person.
| What lives on the entry | Who can change it |
|---|---|
| Status | The owner and an editor. |
| Reminder date | The owner and an editor. |
| Notes | The owner and an editor. |
| Checklist ticks | The owner and an editor. |
| The people on it | The owner only. An editor cannot invite anybody and cannot remove anybody. |
Inviting a colleague
- Open the entry on your tracker.
- Find
Invite by email. - Choose a role: "Viewer, reads only" or "Editor, may change things".
- Press
Invite.
The firewall: what an invited colleague cannot see
That is friction, and it is the correct friction. If your colleague needs to know your turnover, you can type it into the notes, which is you choosing to tell them. What you cannot do is press one button that hands over the certificate itself.
It matters most in the case it was designed for: two firms bidding on the same tender on the same afternoon, one of whom has been invited onto the other's entry.
Removing somebody
The owner can change a person's role or remove them from the entry. Removing somebody takes their access away; it does not delete anything they wrote into the notes, because those are part of the entry rather than theirs.
What is coming, and what to expect meanwhile
| What you probably want | Where it stands |
|---|---|
| Start a proposal, come back tomorrow, carry on | Half built, and not yet usable. The server can now store and reload a draft. No screen calls it, so you cannot. |
| A revision history on a draft | Same. The server can list revisions and restore one. No screen calls it. |
| Change one section without regenerating | Not built. The revise endpoint exists and no screen calls it. |
| Invite a colleague into a draft document | Not built. Collaboration is on the tracker entry, not on the document. |
| Invite a colleague onto a tracker entry | Built, Insider only, never used. |
| A colleague seeing your uploaded evidence | Deliberately refused, and it will stay refused. |
Checked against this platform on 7 September 2026. If this page disagrees with your screen, your screen is right: this is how the page gets corrected.