Protect the workspace: members, invitations, mirror

These settings decide who gets into the workspace, with which role, and which rows each person sees.

1. Which settings protect the workspace?

Mechanism	What it protects
Member rights	The role (Owner, Admin, User), web and mobile access, API access, messages and the member list, person by person.
Invitations	Who has been invited, and who has not accepted yet. A pending invitation is still an open access.
Mirror view to a dedicated workspace	Gives a client or a contributor a workspace that contains only what concerns them, with no access to your production workspace. Prepare the view before sharing it → Create and use a mirror view, chapter 4
User ID as a default value	Limits each person to their own rows, through a view filtered on their identifier.
Workspace ID as default value	Limits a view to the rows of one workspace, through a filter on its ID.
Filter a view by user ID for a mirror workspace	Step by step: each technician or client reaches their own data, without the main database.

Go further

Security overview

Every protection setting, from the account to the API, on one page.