People & permissions

A workspace usually has two kinds of people in it: the ones who run it, and the ones who just use it. Cobblr treats those differently, and lets you get as granular as you need in between.

1. In Configuration, open the People card and press + Invite someone.
2. Pick Join this workspace (your records, at a role you choose) or Start their own Cobblr (their own workspace on your instance).
3. Copy the link and send it however you already talk to them.

Managers and members

• Owner, admins, editors work in the full interface: every module, the configuration hub, the builder.
• Members and guests, the roles below that, start with almost nothing and see only what you've granted.

That split is what makes it safe to bring people in. A club volunteer or a shop worker doesn't need the workspace, they need their job's screen.

Granular grants

Below the broad roles, permissions are individual capabilities: adjust stock, create a part, run this action. Grant them two ways:

• Directly to a person, one capability at a time.
• As a custom role you define: bundle the capabilities a job needs ("counter staff" can look up parts and adjust stock, nothing else) and assign the role to whoever holds that job.

What someone can't do is also what they can't see. The interface hides what a person lacks the capability for, and the server withholds it either way. Both are resolved from the same source, so there's no gap between them.

Inviting someone

Inviting is for owners and admins.

1. The People card in Configuration carries + Invite someone, which opens the invite form with the email box already focused rather than dropping you on the members list. Or ask Cobb, which walks you to that form with the email and role already filled in. Pressing Send stays yours.
2. Mint the link, copy it, and send it however you already talk to the person.
3. Open invites are listed right above the form with a copy button beside each.

• An invite is a link. Nothing depends on the instance being able to send email. The link alone is what joins them (the same model as "anyone with the link can join").
• The email box is an optional hint that pre-fills their signup, not a requirement.
• Each link is single use, and you can revoke one before it is used.

What the recipient sees

Signed in already: the workspace's name, who invited them, the role they will get, and a one-click Join. No account yet: a signup form that creates their account and joins them in one step, and it works even when the instance has public signup closed, because the invite itself is the authorization. Signed out with an existing account: sign in, then join.

Two different invites

The form offers two kinds, and they answer different questions:

• Join this workspace brings someone into your records, at the role you pick. This is the one for a second pair of hands: family, a club volunteer, shop staff.
• Start their own Cobblr gives them their own account and their own brand-new workspace on your instance. This is for hosting a friend. Owners only, on instances where the operator has allowed self-serve invites.
• Seed from here (a tick box on the second kind) starts their workspace as a copy of yours: the same modules, fields, views and automations, with none of your data in it. That is the "arrives already set up" experience, built on blueprints.

The operator has a third door of their own, minted from the admin console, which serves the same start-their-own purpose without a workspace behind it.

Changing and removing people

The same People page lists every member with a role dropdown beside each.

• Promote or demote by picking a new value.
• Remove takes a person out of the workspace. Their account survives (accounts belong to the instance, not to a workspace), and anything they created stays, attributed to them.

Talking about a record

Every record's page has a Discussion tab in the right-hand rail: one conversation per record, flat and in order, so "which shelf did you mean?" happens next to the shelf rather than in a chat app where the context dies. Type @ and a name to bring someone in, and they hear about it through whatever channels they use. Mentions, replies, Cobb in a thread, settling, and the Discussion page are all on Discussion.

Your account

Everything that is yours rather than a workspace's lives under Your account, reachable from the user menu or the sidebar. It opens on four cards, the same shape as Configuration, each clicking through to a page that lists those settings with a line on what each one does:

• You: your display name and the address you sign in with, your password, light or dark, and which parts of the menu you want to see. Identity and password share one page.
• Notifications: whether Cobblr reaches you in-app, by Discord DM or by email, the per-workspace channels, and everything it has sent you.
• Connections: services of your own (an AI key, a parcel-tracking account) and your edge bridge, which follow you between workspaces rather than being re-added in each one.
• History: what you have done across every workspace, and the feedback you have sent.

Inside a locked single-purpose app the platform-level groups are hidden, so you see only your name, your password, and how you are reached.

Personal preferences

Not everything is a permission. Your light or dark theme is a personal choice.

• It follows your account across every workspace and device, and never changes what another member sees.
• A workspace with a branded theme is the exception: that theme shows to everyone, and your preference governs the ordinary, unbranded workspaces.
• Light and dark covers how the theme resolves.

The member portal

Members don't land in the admin interface at all.

• They sign in to a slimmed-down portal and go straight into the custom app you built for them. With several apps, they get a launcher.
• Combined with an app's read scope and their grants, a member's whole experience can be one focused tool: scan things in, check things off, see the list that matters to them, and nothing else.
• A workspace can run app-first for everyone, hiding the builder chrome behind a "grow door": the app feels like a standalone product until someone with the permission steps through into full Cobblr.