Skip to main content

Workspaces and isolation

Personal and organisation workspaces are strictly separated, and the separation is enforced at the database level rather than in the interface.

Who this is for: Anyone in more than one workspace, and anyone assessing Byteflare's data separation.

Switching workspace

Use the workspace switcher in the top navigation to move between Personal and each organisation you belong to. Your selection is stored in a cookie in that browser. It does not follow you to another device.

What each workspace can see

  • A personal project belongs to you alone. No admin or owner of any organisation can open it.
  • An organisation project is visible to every active member of that organisation, regardless of who created it.
  • Templates follow the same rule.
  • Trash follows the same rule, except that owners and admins additionally see other members' trashed projects.

Isolation between organisations

Membership of one organisation gives you nothing in another. The access rules are enforced by row-level security policies in the database and re-checked in application code, and the behaviour is covered by an automated isolation test suite. The specific guarantees that suite asserts are:

SituationResult
A member of organisation A requests a project belonging to organisation B by its exact idDenied
A member with the member role tries to change organisation settings or manage membersDenied
A user with no organisation reads their own personal rowsAllowed
A user with no organisation requests any organisation rowDenied
A suspended member of an organisation requests that organisation's rowsDenied
An invited person who has not yet accepted requests the organisation's rowsDenied until the invite is accepted