Back

How to share a project and manage access

Work in Sloc lives in a project, and so does access to it. Add a colleague to the project and they see its data versions, subsets, scenarios and plans - the same numbers you see, without anything being sent anywhere.

Open the access list

On the projects page, click the ... on a project card and choose Manage access.

The project card menu, with Manage access
Add someone

Pick them under Add users, choose a Role and click Add. They're notified that they now have access.

User access, adding someone to the project and showing who already has it
  • Editor - the working role. Import and edit data, build subsets, run scenarios and divestment plans, download results.

  • Owner - everything an editor can do, plus managing who else has access and deleting the project.

Users with access below lists everyone on the project with their role, so you can see at a glance who is on a case.

What access covers

Access is per project, not per piece of work. Someone added to a project sees everything in it, including data versions and scenarios created before they joined, and anything added afterwards. It does not extend to your other projects.

Confidential client data usually means keeping one case to one project, rather than building several cases in a shared one.

Pro tips
  • Add people when the case starts, not when they ask. Saved scenarios and plans only help a team that can open them.

  • Name scenarios and data versions as if someone else will read them, because on a shared project someone else will.

  • Review the list when a case ends. Access lasts until someone removes it.