The dashboard

Workspaces & projects

A workspace is the boundary around everything: it holds the Members, owns every Project, and is what gets billed. One login can run as many as it needs — a personal one, a client's, an employer's — and switch between them from the sidebar.

Creating and switching

Your first workspace is the first step of onboarding: name it, and Fixback reserves an address for it. After that, New workspace in the sidebar switcher creates another. The switcher remembers which one you were last in, per account, so a reload lands you back where you were.

The handle is the address

Every workspace has a unique handle — the wemuda in app.fixback.dev/wemuda. Opening that address makes the workspace active and lands you in the app, so it is a link you can bookmark or paste to a teammate.

Handles are 2–40 lowercase letters, digits and inner hyphens, and are unique across the whole platform.
Created from the name, de-duplicated with a numeric suffix when it is taken. If you type one yourself and it is taken, Fixback refuses it and offers the next free one rather than quietly changing it.
Renaming a workspace never rewrites its handle, so existing links keep working. An Owner can change it deliberately in Settings.

A handle and a Project key are different things: the handle addresses the workspace, and the Project key (the FIX in FIX-140) prefixes one Project's Issue keys.

Members and roles

There are two roles, deliberately:

Owner — everything a Collaborator can do, plus inviting and removing Members, changing Roles, editing the name and handle, choosing the analysis model, deleting the workspace, and (later) billing.
Collaborator — full product access: the queue, triage, Projects, Handoff.

Inviting someone sends an email naming who invited them and which workspace, and lands them directly in it once they sign in. Any Member can leave a workspace; the last Owner cannot, so a workspace is never left without one.

Deleting is soft: the workspace is recoverable for 30 days and keeps its handle for that window, then the purge frees it.

Projects

A Project is one deployed site or app. It owns its SDK keys, its Gate, its Project key, its connected repository, and every Session, Feedback and Issue filed against it. A Project belongs to its workspace permanently and is never moved between them; run staging and production as separate Projects if you want their Issues kept apart.

Each Project's settings hold:

Keys — the publishable key that ships in the page, and the secret key your server and CI use. The publishable key is an identifier; the secret key is a credential.
Allowed origins — the sites the web SDK may boot on. A mobile or backend install needs no entry.
Gate — Open, Invited or Internal.
Reporter invites and the Reporters list, with per-person removal.
Capture — which Trace streams and replay are on for this Project.
Analysis — whether the annotated screenshot is sent to the model.
Alerts — this Project's alert mode.
Repository — the connected GitHub repo, if any.
Project key — editable, and re-labels the Project's Issues when changed.

The analysis model

Which model writes your Briefs is a workspace choice, in Settings → Automation: pick from a curated catalog, or leave it on the platform default. It is Owner-only, because it is a spend decision.

Models that can't read images simply skip the annotated screenshot and write the Brief from the rest of the Evidence. That is why the per-Project screenshot toggle and the workspace model choice are separate settings: the Project says what may be sent, the workspace says what can read it.

Where everything lives

Settings section	What it holds
Organization	The workspace name, its handle, deleting it, and restoring one you deleted.
Members	Invite people, change a Role, remove someone, resend an invitation, or leave yourself.
Reporters & tiers	What each trust tier means here, and how far automation goes for it.
Automation	The analysis model that writes every Brief, and the automation defaults.
Billing	The workspace is the billing subject.
Notifications	Yours, not the workspace's: your alert address and your opt-out.
Account	Your display name, and the Reporter sessions you hold on other people's sites.

The split is deliberate: the first five belong to the workspace and are shared by everyone in it; the last two belong to you and follow your account into every workspace you join.