Workspaces

A workspace is a team space — it decides which features (and therefore which data) a group of people can reach. Add someone to a workspace and they can see everything that workspace has; that one rule drives most of “who can see what” in Ronja. A workspace grants access — it isn’t a folder your data lives in. The mechanics: users are members of workspaces, workspaces have features, and you can see a resource if you can reach the feature that owns it through one of your workspaces.

The Default workspace

Every organization starts with one workspace, badged “Default”. It has two conveniences switched on: every user is automatically a member, and it shares all organization features. It can’t be deleted. Many small teams never need another workspace — you create more when different groups should see different things.

Membership

Admins manage who belongs to a workspace. The Members tab lists everyone in the organization with a per-row Add/Remove toggle (you can’t remove yourself), and the Users & Access matrix handles bulk changes across all workspaces at once — see Manage users and roles.

Two workspace-level toggles change the rules, and both are admin-only:

• “EVERYONE IS A MEMBER” (the workspace’s All users flag) — every current and future user in the organization is automatically a member. While it’s on, individual Add/Remove is disabled; new hires get access without an invite step.
• “All-users admin workspace” — in the product’s words: “When enabled, all workspace members get admin privileges within this workspace. They can upload files, manage features, configure table access, and manage members.” Useful for a high-trust team space; the elevation applies inside that workspace only, and never extends to creating or deleting workspaces.

Features: what a workspace provisions

A workspace reaches features two ways: features that belong to the workspace itself (handed over by their creators), and organization-scope features attached to it. Attachment is managed on the Features × workspaces map on the Shared features page, where each cell shows Full, Partial, or None:

• Full — members see everything in the feature.
• Partial — a restricted attachment: only the specific resources an admin grants.
• None — not attached.

Each workspace also has a “SHARE ALL FEATURES” switch that attaches every organization feature automatically — including ones shared later.

Note

Promoting a feature to Organization scope does not broadcast it to everyone — it becomes attachable, and someone still has to wire it to workspaces (or a workspace with “share all features” picks it up). See Scopes and sharing.

Handover: features arriving in a workspace

When a member asks to hand a private feature over to a workspace, the request waits for a workspace admin. Requesters see an “Awaiting workspace admin” banner with a Withdraw action; admins see “Pending approvals” and review each request. Approving makes the feature visible to every member of the workspace.

What workspaces don’t own

Explorations do not belong to workspaces. A conversation connects to a team only when its owner shares it — with individual people or with a workspace, in which case everyone in that workspace can open it.

Deleting a workspace

Only Admins can delete a workspace. Deletion is a soft delete: the workspace moves to the trash for 30 days, but members lose access immediately and its automations pause. Restoring within the window brings it back and resumes the automations; after 30 days it’s purged permanently. See Restore from trash.

Still unsure when to reach for a workspace versus a feature? See What’s the difference?.