I want to update an existing space and make it restricted/shared

User Acceptance Criteria

• New spaces are created as restricted by default (only the person who created the space has access to it)
• Once I’m in a space, I can adjust the access to that space (using the ‘share’ button)
• I can switch a space between “full access” vs. “no access”
  • Switching between these just switches between their defaults (e.g. if I have a restricted space where I’ve also invited Priyanka, then I switch it to “shared”, then I switch it back to “restricted”, it would restrict the access to just me, it wouldn’t keep the old configurations and add Priyanka too)
• You’re either given access to a space, or you aren’t. There’s no option to add someone as an editor vs. viewer when you’re inviting an individual.
• Everyone inherits the permissions that they have at a project level. There’s no way to change these permissions in the spaces modal.
• if a space is restricted, I can only add individuals to the space (for now). I can’t add groups of individuals (e.g. editors).
• I can remove someone I’ve added to a restricted space

Frontend stuff User flow Components

[TuringLovesDeathMetal]

^Yes, I think so!

This feels like a really common pattern in a lot of tools and I can imagine people requesting this later on. We’re not building it now because we couldn’t agree on “can you increase someone’s permissions” (e.g. I’m a project viewer, but you make me a space editor). So we tried to reduce the scope and just use “full access” vs. “restricted”

[owlas]

Whoops that was a mistake. The is_private should live on the space table 🤦

In the spec permissions are inherited from their project role so we don’t need the access type on the space_share table. Although in future we’ll want to do that. So if it’s easier to add now rather than refactor, you could add an access to space_share and the space would return an access list like:

{
  "uuid": "810b43d0-fc0d-4199-8a79-25b471c880bf",
  "name": "Shared space",
  ...
  "isPrivate": true,
  "access": [
    { userUuid: "...", "access": "view"},
    { userUuid: "...", "access": "edit"}
    { userUuid: "..." },
  ],
}

access could be optional meaning that it inherits from the project? Or maybe that’s a bit confusing.

Simplest would be to not have any access on the space_share and inherit project perms