Workspace owner or tracker admin
Move between teams without losing where the work belongs
Each workspace keeps its owner-defined rules; each Space keeps the project context every member joins and works inside
This is the real workspace and Space switcher over sample data. Choose a context, close it, or add a workspace; nothing here changes your account
One workspace-level decision,then every Space knows what to inherit
A workspace is the team, authority and defaults; a Space is one selected project inside it. The owner or admin binds both to the tracker, then sets where work lands, how much confidence may move it automatically, and who may enter. Joiners inherit that structure instead of configuring it again
1 / 8Choose your role
Owners define the workspace; members inherit it
Create is the workspace-owner or tracker-admin path: it chooses projects, delivery, confidence and access for the team. Join is the workspace-member path: it proves which team you belong to and opens what an owner already prepared. They are different responsibilities, not two labels for the same setup flow.
An owner or admin of your tracker makes it
Unifies does not invent an organization for you, and it does not let just anyone bind one: creating a workspace takes an owner or admin in Linear, because that is the permission the tracker itself asks for. They pick which of its workspaces this one is made from, and that binding is permanent. A different tracker is a different workspace, which is why nothing later offers to swap it.
Everyone else is one request away
Not being an admin is the ordinary case, and it is not a dead end. Unifies records the request against the workspace, names the Linear admins who can approve it, and sends it, without ever showing you their addresses. When one of them connects, you are already in the workspace they made.
Your projects arrive as they are
The tracker brings its structure with it: the projects your team already runs, and the people in them. You choose which projects come across, and each one becomes a Space: where its work is delivered, and where its record comes back.
The workspace sets one safe automation boundary
Confidence controls motion, not whether a promise exists. Every commitment is drafted with its source evidence; below 0.70 is held for review, from 0.70 to the workspace threshold waits for one-click confirmation, and work at or above the threshold can create a task automatically only after an admin has set its destination. The default is 0.85, and raising it makes automation more conservative without losing the work.
Access is a workspace rule, not an invitation accident
An owner decides what happens after the first invitations are gone: open lets teammates already in the same Linear workspace walk in, approval makes every new arrival a decision, and invite only keeps the door targeted. A joiner sees that rule before they can enter, so there is no second, accidental workspace and no hidden permission model to discover later.
Invite the whole roster in one press
The people arrived with the projects, so nobody retypes an address the tracker already holds: one press invites every teammate Linear gave one for. The ones it names without an address are neither counted nor offered. They join by signing in with the same Linear, which claims the row already waiting for them.
Everyone after that arrives to work already waiting
The second person does not repeat authorization, project selection, routing or the confidence decision. They prove which team they belong to through an invite or the same tracker, then land in the existing workspace with its Spaces ready and its rules already visible. Joining inherits context; it does not create a second copy of the team.
Before you set anything up
Questions worth asking first.
Do I need to be an admin of our tracker?
To connect a workspace, yes: the tracker requires an owner or admin to authorize it. If that is not you, Unifies records the request and sends it to the people who can approve it, and you can keep evaluating in the meantime
We run two trackers. Do we get two workspaces?
Yes, and that is the model rather than a limitation. A workspace is provisioned from one tracker workspace, so a second tracker is a second workspace with its own Spaces, its own people and its own record. There is no way to point one workspace at two trackers, which is why the surface shows the tracker locked instead of offering a swap it would then have to refuse
Does connecting copy our projects into Unifies?
No. Connecting reads the structure: the projects and the people in them. You choose from that. Only the projects you keep become Spaces, and a project you leave behind is not mirrored at all: nothing arrives from it, and nothing about it is stored here
What if we skip a project and want it later?
Add it whenever you like, without redoing the connection. The same authorization is still there, so a project you left behind becomes a Space the day you decide it should be one
Does confidence decide which commitments Unifies keeps?
No. Confidence controls what may move automatically, not whether the commitment exists. Every commitment is drafted with its source evidence. Below 0.70 is held for review; from 0.70 to the workspace threshold waits for one-click confirmation; at or above the threshold can auto-deliver only when an admin has configured a destination. The workspace starts at 0.85 and can choose a more conservative threshold
Does connecting email everyone in our tracker?
Nothing is sent until somebody presses Send. Setup offers the roster in one step with everyone selected, because inviting the team is what setting up a workspace is for. It is still a screen you can change or skip, and the same invitations are in Settings afterwards, one row at a time or the whole register at once. Teammates the tracker names without giving us an address are never counted and never offered: no product can email an address it does not have, and those people join by signing in with the same tracker
Who can join a workspace once it exists?
Whoever the workspace decides. A workspace is open, approval required, or invite only, and an owner changes that in settings. The second person to arrive either walks in, waits for a decision, or needs an invite. Everyone who joins lands in the workspace their tracker already made, which is why nobody ends up with a second copy of the same team
What does it cost, and what happens when the free hours run out?
Free is one person, forever: 5 capture hours a month, no card and no expiry date. When the hours run out, capture pauses and every receipt you already have stays readable. Paid plans are flat per workspace. The full ladder is on the pricing page
Start with one workspace
Bring the tracker your team already runs, choose the projects that should become Spaces, and set one safe rule for what may move. Free will be one person, forever, with 5 capture hours a month and no card