Cloud Collaboration and Access

Cloud collaboration has two layers: Workspace roles control administration, while Project visibility controls access to knowledge.

Workspace roles

Every Workspace member is an owner, admin, or member. Owners and admins can invite people, change member roles, manage the Workspace, and create or manage Cloud Projects. Members can use Projects that are visible to them, but cannot administer the Workspace.

Ownership transfer and invitation revocation are currently managed in the desktop app. A member can leave a Workspace; deleting a Workspace is an owner-level decision. The Cloud app shows pending invitations but does not yet provide resend or revoke controls.

Project visibility

A Project is either visible to all Workspace members or to selected members. This is an access boundary, not a separate Project role system: a member who can open a Project can currently read and edit its Brain. There is no Project-level read-only role. Projects created in the Cloud app start with all members; choose selected-member visibility in the desktop app.

Before adding sensitive material, verify both the Workspace membership and the Project's selected-member list. In the current Cloud app, Archive removes a Project from normal work and has no restore screen, so treat it as a destructive action.

Usage and plans

Workspace settings show the current Project, storage, and member usage alongside the Workspace billing state. Limits belong to the Workspace plan, so a plan change affects the shared Workspace rather than only the person who made the purchase. See the current pricing page for plan details.