Shared workspaces

Bring a small team into one workspace so everyone works in the same Objects, Types, and Views together, with roles and a membership list — instead of sharing individual Objects one at a time. See Sharing an Object if you only want to give one other account access to a single Object.

Create a shared workspace

Converting is permanent: a shared workspace can’t go back to being personal-only.

Switch to the workspace you want to share, or choose Create workspace first if you want to start from an empty one.
Open the workspace switcher and choose Create shared workspace.
Read the disclosure: everything already in the workspace, including its full history, is included, and the change can’t be undone.
Check I understand this includes all existing content and can’t be undone, then choose Create shared workspace.

You become the workspace’s owner. If conversion is interrupted (for example, by a crash), reopening the dialog resumes it automatically instead of asking again.

Roles

Role	Can do
Owner	Everything below, plus promote someone to Admin, transfer ownership, and delete the workspace for everyone. Exactly one per workspace; the owner can’t leave without transferring ownership first.
Admin	Create invites (except ones that grant Admin), approve or reject join requests, change roles and remove members up to Can edit — but not other Admins.
Can edit	Read and write Objects, Types, and Views.
Can view	Read-only access.
Guest	The most limited role. A Guest is not invited directly — it appears automatically for someone you’ve given access to a single Object through Sharing an Object without making them a full member.

Invite people

Admins and owners can invite; only the owner can create an invite that grants Admin.

Open Settings → Invites.
Under Create an invite, choose an Access level (Admin, Can edit, or Can view), how long it Expires in (7 or 30 days), and its Number of uses (1–25).
Choose Create invite, then copy the token and send it through a channel you trust.

Join a shared workspace

Open Settings → Invites and choose Continue under Join a workspace.
Paste the invite token and choose Continue to preview it: the workspace’s name, who invited you, and the role you’d join as.
Set the name admins will see for you, then choose Send join request.

Redeeming a token doesn’t grant access right away — it sends a join request. An admin or owner needs to approve it before you can open the workspace.

Approve or reject a join request

Open Settings → Invites. Pending requests appear under Pending join requests with the requester’s name and when they asked.
Choose Approve to open the confirmation dialog. Pick the access level to grant (it can be lower than the invite’s cap, but never higher), then read the safety words — a short phrase derived from the request. This is a moment to double-check the request, not a verified identity check.
Check I’ve confirmed the safety words, then choose Approve and add.

If two pending requests use the same display name, a warning badge flags it — double-check these aren’t the same person applying twice before approving either. Choose Reject to decline a request instead; the requester can ask for a new invite.

Manage members

Open Settings → Members to see everyone with access: their role, how many devices they’ve registered, and their join order. A badge flags devices still pending verification. Each member may also show a custody badge (Secure enclave, Device-managed key, or Passphrase) describing how their device protects its key — this is self-reported by the device, not independently verified, so treat it as a hint.

An admin or owner can, for anyone below Admin standing:

Change role — lowering someone’s access asks for confirmation first; raising it doesn’t.
Remove — the member keeps whatever already synced to their device, but loses all further access. This can’t be undone.

Only the owner can change or remove an Admin.

Transfer ownership

The owner can choose Transfer ownership next to any member. The offer is pending until that member accepts or declines — the owner can cancel it in the meantime. Once accepted, the recipient becomes the owner and the previous owner becomes an Admin.

Leave or delete a workspace

Any member other than the owner can choose Leave workspace: the live connection ends immediately, and you keep whatever already synced to this device, but an admin or owner still needs to remove you from the member list before your access is fully revoked. The owner can’t leave without transferring ownership first.

The owner can choose Delete workspace to end it for every member at once. Nobody can write to it again afterward, and there’s no restore for members — though each member’s own local copy stays on their device.

Activity log

Settings → Members → Activity is a read-only, newest-first record of the workspace’s own membership changes: joins, role changes, removals, leaves, and ownership transfers.

If you lose access

If you’re removed, you leave, the owner deletes the workspace, or you delete it from another device, Lar moves your local copy on this device to Trash rather than erasing it silently, with an option to export it first. Rejoining needs a new invite.

Limits

A server enforces limits on how many members, guests, and open invites a shared workspace can have. If you hit one, ask the workspace’s owner or administrator, or see Self-hosting Lar if you run your own server.

Use a shared workspace when a group should jointly own a whole workspace — its Objects, Types, and Views — with roles and a membership list. Use Sharing an Object when you want to give one other account ongoing access to a single Object without making them a member of your workspace.

For the encryption model and what a server can see, read Local-first & encryption.