Create a workspace

Creating a workspace requires Solo plan. On the Free plan a member can be invited into a workspace and participate fully, but cannot create one.

WorkspacesWorkspaces in the sidebar

Your workspaces. Empty until you create or are invited to one.Open /w in the app

×

Selecting the mode

The mode determines how work progresses through the workspace and should be decided before members are invited.

The three modes, named for what they mean rather than what they are called in the API.Open /w/ in the app

×

Mode	What it means	Needs
Task Board	A kanban board with no contribution workflow	Solo plan
Equal Partners	All participants shape the work jointly	Org plan
Led by One	A single organisation sets direction	Org plan

The mode cannot be changed after creation. The settings screen states this: “Collaboration mode is set when the workspace is created and cannot be changed.” Every other workspace field is editable.

The modes are gated on different plans, which the create dialog does not indicate at the point of selection. Task Board is available on Solo; the two cross-organisation modes require Org, and this is enforced on submission rather than on selection.

Task Board also differs in operation. The other two modes run a contribution workflow in which deliverables are assigned, partners submit against them and a reviewer responds. Task Board provides a board without that workflow, and should not be selected where a review step is required.

1. Enter a title stating what the group is producing — for example “Wallacea grant application” rather than “Collaboration”.

2. Add a one-line description. Optional, and the first text an invited partner reads.

3. Select the mode. See above, and confirm the plan: cross-organisation modes are rejected on submission rather than disabled in the form.

4. Set start and end dates. Optional. A workspace is intended to be time-bounded and archived once its output is delivered.

5. Create it.

Workspace contents

Deliverables	The outputs being produced. Assign, submit, review.
Contributions	What partners have submitted against them.
Files	Shared files.
Wiki	Pages for the group.
Members	Who is in it, and their role.
Insights	Activity across the workspace.

Deliverables and contributions are documented separately, including the six deliverable states, the four possible responses to a contribution, and the two methods of generating suggested deliverables: Deliverables and contributions.

Roles, invitations, guest accounts and the switch controlling whether AI agents can reach the workspace are in Members and access.

Exporting the activity log

A workspace’s activity log exports as CSV over a date range defaulting to the previous 90 days. It is an audit trail of actions and timestamps rather than the deliverables themselves, and is intended for evidencing that a collaboration took place.

Workspace origins

Not all workspaces are created directly. A workspace can originate from a connection, an opportunity, a project — where a milestone generates the workspace that delivers it — or as a standalone. A workspace that was not created directly will have one of these origins.

A deliverable is an output, not a task

“Module 3: Conflict Resolution” is a deliverable; “Write section 3” is not. The submit-and-review pipeline handles completed outputs, which is why it contains no sub-task concept.

Settings

More → Settings has four tabs: General, Storage, Tags and Access.

General holds the title, the URL slug — workspaces receive a readable address such as /w/wallacea-grant-application rather than an identifier — a description, and start and end dates. All are editable at any time. The collaboration mode is not.

Archiving

Archiving is in the settings screen’s Danger Zone. Its effect is narrower than the term suggests: the workspace becomes read-only. Members retain access but can no longer make changes.

It is neither a deletion nor a removal from view: every member who could previously see the workspace can still see and read all of its contents. It can be unarchived to active, and no content is lost.

The same principle applies one level down, with one exception:

Deliverable	Archived — hidden from the default list, and restorable
Contribution	Deleted, and only a coordinator can
Attachment	Deleted

The reversible action therefore applies to the containers, and the irreversible one to submitted material. Deleting a partner’s contribution is not an archive operation and can be performed only by a coordinator.

Deliverables can also be reordered. The order determines how partners read the work.

Workspace or project?

A workspace is where work is produced; a project is the initiative. Neither contains the other, and a workspace can exist without a project.

The distinguishing test: work produced with members of other organisations is a workspace; work planning what a single organisation is trying to achieve is a project.

See Project or workspace?. Note that workspaces and spaces are distinct again, and scope in opposite directions: Workspaces and spaces.