...
The platform does not let one person hand over their own workspace. Instead, your project gets a separate shared workspace for collaboration.
| Your own workspace | The shared session | |
|---|---|---|
| Who can enter | Only you | Every member of the project |
| Whose files | Yours | The project's |
| Runs as | You | A shared project account |
Why it is built this way. If a colleague joined your workspace, they would get your private files, your data access, and the right to run code as you. The shared session avoids all of that. Nobody enters your private space. Nobody acts as you.
...
In your Launcher, under Collaboration, you see a tile named "Start <project> Collaboration" — where <project> is the project you chose on the launch screen.
...
The Collaboration tile in the Launcher, before the session starts.
If you do not see it, your project does not have collaboration yet. See Getting it turned on.
...
Click the tile again. It now reads "Stop <your project> Collaboration". Confirm, and the shared machine stops.
...
While the session runs, the Launcher shows two tiles: Join, and Stop.
What it costs
The shared session is charged to the whole project, not to the person who opened it. That is why turning collaboration on is a project decision.
...
Your project admin enables collaboration in the RPAdmin console. It is their decision, because the shared session spends the project's money, not one person's.
...
The Real-Time Collaboration panel on the project's page in RPAdmin.
| Warning |
|---|
Being rolled out. Collaboration is being switched on project by project, and the goal is to have it available to every project soon. If the tile is missing, or it appears but the session will not start, ask the platform team: |
...