Learn · Running an organization · 2 min read

Organizations, spaces, and permissions

The admin path starts with the shape of things.

The containers

• An organization is the outer container: members, teams, billing, settings. Roughly "your company on Wodo".
• A space is where work lives: items, documents, views, labels. A project, a team, a client.
• A team is a named group of people, used wherever a person can be used: permissions, assignees, document owners.

Roles and permissions

Organization members are admins or plain members. Independently of that, members can hold organization-level abilities: who may create spaces, who may create teams, who may manage the organization itself.

Space access is its own layer — Read, Comment, or Write, plus space managers — granted per person, per team, or organization-wide, as covered in Sharing.

What admins can't silently do

Worth stating plainly: organization admins do not automatically read every space. Spaces are private by default, for admins too. Admins have authority — they can see that spaces exist and can grant themselves access — but doing so is an explicit, recorded act, not a standing backdoor. In a tool that hosts candid completion notes ("why was this cancelled?"), that distinction matters.

Administrative actions land in an audit log: sign-ins, permission changes, exports, team changes. Boring by design, there when you need it.

Housekeeping

• Archiving a space hides it from everyday navigation while keeping it searchable (with the "include archived" toggle) and restorable. The end of a project shouldn't mean the end of its memory.
• Deleting a space is the one true delete in Wodo — individual items can only ever be archived. It's permanent, admin-only, deliberately confirmed, and the way to actually free storage. Export first if in doubt.
• Closing the organization is the real exit: a typed confirmation, a final pro-rated invoice, a 30-day read-only window for exports, then deletion. No retention tricks on the way out.