Learn · Running an organization · 3 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

Two layers, and they're independent.

At the organization, you're an admin or a plain member. Independently of that, members can hold organization-level abilities: who may create spaces, who may create teams, who may manage the organization itself.

At each space, access is its own thing (Read, Comment, or Write), granted per person, per team, or organization-wide, as covered in Sharing. A space can also have space admins: the people who configure it (its labels, completion states, cycles, milestones, and the rest of Space Settings) and who manage who's in it.

These don't imply each other. A space admin needn't be an organization admin, and an organization admin has no standing access to a space until they're granted it. The person who sets up a project usually isn't the one who runs the company on Wodo. So if a teammate can't open Space Settings, it's because they're not a space admin there, not a bug.

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 aims for transparency, that distinction matters.

Administrative actions land in an audit log: sign-ins, permission changes, exports, team changes. Boring by design, and 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.