Members and access
Workspace membership, the permissions attached to each role, and the separate question of whether automated clients may access the workspace.
/w/ in the appThree roles
Section titled “Three roles”| Role | Can |
|---|---|
| Coordinator | Full control of the workspace |
| Partner | Submit contributions, view deliverables |
| Observer | Read only |
Partner is the operational role, and it is narrower than commonly assumed: a partner submits against deliverables rather than creating them. Where a partner organisation needs to shape the work as well as deliver it, Equal Partners mode applies — the mode determines the scope of the role.
Inviting people
Section titled “Inviting people”Members can be invited in bulk rather than individually.
An invitation does not require an existing account. A recipient can accept as a guest, which is a limited account scoped to workspaces and projects. A new partner therefore requires only an email address rather than a full registration.
Joining is deliberately available on the Free plan: the platform gates the creation of work rather than participation in it. See what your plan includes.
External agent access
Section titled “External agent access”A workspace carries an external agent access switch, set by the coordinator.
This is the only per-resource control of its kind on the platform. Personal and organisation wikis have no equivalent; for those, narrowing the token is the only available restriction. A workspace can deny access regardless of what a member’s token otherwise permits.
Coordinators are also shown the workspace’s exposure. The settings screen reports the number of members — not tokens — holding at least one active token that could reach the workspace. A member with three tokens is counted once, as the figure reports how many people have an agent able to reach the work rather than how many credentials exist.
This figure is visible to coordinators only.
Something wrong on this page? Report it