Learn Β· Working together Β· 2 min read

Sharing your work

Wodo's sharing model has one rule worth internalizing: spaces are private by default. Being a member of the organization grants access to nothing by itself β€” every person sees exactly the spaces they've been given, and that's all. Even organization admins don't silently read content; if they grant themselves access, it's explicit and recorded.

Inviting people

Invite by email β€” whether or not the person has a Wodo account yet. You can invite someone to:

  • The organization β€” they become a member (and still need per-space access).
  • A single space β€” for most collaboration.
  • A single document β€” the narrowest grant there is.

Invitations can carry a personal message, expire after seven days, and can be revoked. If the person already has access, Wodo tells you before sending rather than letting redundant invitations pile up.

Permission levels

Three levels, in plain words:

LevelWhat it allows
ReadSee everything in the space.
CommentRead everything, write comments only.
WriteEdit everything: items, documents, labels.

On top of these, a space can have managers β€” people who can invite, remove, and change others' permissions.

Permissions can be granted to a single person, to a team (a named group in your organization β€” grant once, membership follows), or to the whole organization at once. When grants overlap, the most generous one wins.

Guests

People outside your organization β€” a client, a freelancer, an auditor β€” can be invited straight into a space or document as guests. They sign in with Google, Microsoft, or a passkey if they have neither. A guest sees a simple "shared with me" list of exactly what they've been given, and nothing of your organization beyond it.

Guests are also priced like what they are: €1 per space instead of a member seat.

Going further
  • Teams have their own admins, and can be used anywhere a person can: space permissions, item assignees, document owners.
  • For organizations that want to manage identities rather than invite them β€” verified domains, enforced SSO, authoritative offboarding β€” see Members and domains in the admin path.