Skip to main content

Workspaces

Everything you build in Cobblr lives in a workspace. A workspace is a self-contained space with its own data, its own modules turned on, and its own people. Think of it as an app you shape to fit whatever you put in it, from a workshop to a yarn stash to a lego club.

One instance, many workspaces​

A Cobblr instance is a running copy of Cobblr that you self-host on your own machine. A single instance can hold many workspaces at once, fully isolated from each other. This is what people mean by multi-tenant: one install, many separate spaces. A workspace for your garage and a workspace for a friend's side project share the server and nothing else.

The isolation is real. Each workspace keeps its own separate database, so data from one never mixes with another, and a single self-hosted box can safely run spaces for different people or different projects.

Your account holds your workspaces​

You sign in once, with one account, and that account can hold several workspaces at the same time: the ones you create yourself and the ones you're invited into. A switcher moves you between them without signing out, and you can carry a different role in each. One login might cover your own garage inventory, a makerspace you share, and a club you help run, each a separate workspace under the same account.

Divide them however you like​

There's no right number of workspaces. Keep things apart when the separation is the point, like a personal workspace and a work one so the two never mix. Or put everything in a single workspace when you'd rather see it all together: your whole home in one place, with the cars, the machines, the yarn, and the groceries side by side. It's whatever fits how you think about your stuff.

People and roles​

People join a workspace as users, and each user has a role that decides what they can do. From most access to least:

  • Owner runs the workspace and is the only one inside it who can delete it.
  • Admin manages the workspace and the people in it.
  • Editor creates and edits records, but doesn't manage people.
  • Member and Guest start with limited access and can be granted the specific abilities a workspace wants to hand them.

The higher roles include what the lower ones can do. For the finer grain, individual capabilities and custom roles, see People & permissions.

One tier sits above all of this: the instance operator, a super-admin who runs the server itself. They're outside any single workspace and can manage or remove any workspace on the instance. On a self-hosted box, that operator is you.

Where this shows up​

  • Modules are turned on per workspace, so two workspaces on the same instance can look and behave completely differently.
  • A bundle sets up a workspace with a starting set of modules, fields, and views.
  • Self-hosting is about standing up the instance itself; everything you do inside it happens in a workspace. See Self-hosting.