Your Plexus account · Plexus Docs

A Plexus account is an optional, free sign-in with us that lets you create organizations, manage the machines you sign in on and turn on cross-device sync — the app works exactly the same without one.

There is one thing you can buy on top of an account — a plan, for yourself or for an organization. It is optional in exactly the same way: the account costs nothing, and everything on this page works the same whether or not you hold a plan. A plan unlocks seven things — cross-device sync, saving a prompt template to your account, receiving the workspaces an organization shares, receiving the settings it manages, receiving the prompts it publishes, listing the open issues of a project's tracker, and stacks with ordered merging — and nothing else in the app changes when you have one.

There are two ways in from the app:

The avatar button at the right end of the app bar → Sign in to Plexus.
Settings → My account, which has the same action on the page.

Either way Plexus opens your browser, because signing in happens on the web. If you don't have an account yet, use Create an account — sign up with an email address and a password, and confirm the address from the mail we send you.

Once you're signed in there, the browser shows a consent screen naming this machine and asks whether it may be signed in. Approve it and you're returned to Plexus, signed in; the avatar fills in with your name. Decline, or close the tab, and no device is added and the app stays signed out.

You can also go straight to the account panel — the Sign in link in this site's header — and create or manage an account without opening Plexus at all. The app only needs to be signed in on machines you actually use it on.

Your profile picture

The circle at the right end of the app bar is your account: your initials on a colour derived from your address, or, once you have added one, a picture. On Settings → My account, next to your name:

Add a picture opens your file chooser. Pick any image — a photo, a logo, a screenshot. Plexus crops it to a centred square, scales it to 128 × 128 pixels on your own machine, and only then stores it with your account, so what leaves your computer is that small square and nothing else. The circle in the app bar changes as soon as it is stored, and the same picture appears on every machine you sign in on.
Change picture replaces it; Remove picture goes back to your initials.

A picture that Plexus cannot read, or that the account service refuses, is reported where you clicked and nothing changes. The picture is kept for as long as you keep the account, and is deleted with it — see the Privacy Policy.

What an account is for, and what it isn't

The work you do in Plexus is not behind a sign-in wall. Sessions, worktrees, the agent terminal, review, the explorer, the git client, hooks, pull requests, the dashboard — none of it checks whether you have an account, none of it is unlocked by having one, and none of it stops working if you sign out or if a plan lapses. That is the part we do not intend to change.

Two things do need an account, and they are the reason it exists:

Organizations — a named account you own, with members, roles and invitations. Free.
Cross-device sync — your settings, workspaces and projects following you to every machine you sign in on. This one also needs a plan, as do the other five things a plan unlocks: saving a prompt template to your account, the workspaces an organization shares, the settings an organization manages, the prompts it publishes, and the open issues of a project's tracker.

Those six are deliberately all a plan adds, and the core of the app stays free. Nothing you have already made — a session, a branch, a worktree, a hook, a review — is ever taken away by a plan ending or a device signing out; the machine you are sitting at keeps everything it has and keeps working exactly as it does now. What a lapse costs you is that your machines stop keeping each other up to date, and that an organization's shared workspaces and managed settings stop arriving — what already arrived stays.

Organizations

An organization is a named account that you own. You can have as many as you like, and you can create them from either surface:

In the app — Settings → Organizations. Pick an organization from the organization picker at the top, which also has New organization, and the page below is about that one; its Name row has Rename and Delete. Create, rename and delete them without leaving Plexus.
On the web — the same list, in the account panel.

The two are the same list. Plexus holds nothing about your organizations on your machine, so it reads them fresh from the account service each time you open the page; a change you make in one place shows up in the other as soon as it refreshes.

Deleting an organization is permanent and asks you to confirm. You are the owner of every organization you create.

An organization is also where other people come in. Its members, their roles, the invitations you have sent them, and — if it has a paid plan — its seats, are all in the Plan, seats and people row of that same page; the payment side of it is not, and neither is composing the roles themselves. Plans, seats and billing is that whole story, including which parts open your browser and why, and Roles and permissions is what a role means and how to write your own.

An organization can also hand its people workspaces. One person sets a workspace up once — a name, a description, a rule about who may join, and the repositories that belong in it — and everybody who joins it gets the same one in their sidebar. That is the Shared workspaces row of the same page, below the plan; see Shared workspaces. An organization can also manage settings for its people — a value it recommends, or one it enforces and locks on every member's machine; that is the Managed settings row, see Managed settings. And it can publish prompt templates to them, as numbered revisions that land in every member's template list badged with the organization's name — the Published prompts row, see Prompts your organization publishes. All three need a seat on the organization's plan, and they are the three capabilities a seat carries inside the organization rather than on the seat-holder's own machines. Each row is about the organization you have picked at the top of the page, so a feature one organization's plan lacks is said so in that organization's row and nowhere else.

What happens on the web

Some things are simply better in a browser, so the app doesn't pretend otherwise — it opens the account panel instead:

On the web	Why
Creating an account	It ends in "check your email", which a desktop app can only make longer.
Changing your password	Same.
Changing your email address	The new address has to be confirmed before it takes effect.
Two-factor authentication	Enrolment is a QR code and a set of recovery codes to keep. Optional; it protects the panel, not the app.
Deleting your account	Below.
Buying a plan, paying for it, and reading its invoices	The payment page and the invoice archive belong to the service we bill through, and live on their domain; your billing details and an invitation you are accepting are on the panel. Everything else about a plan — its seats, and who is in the organization — is in the app. See Plans, seats and billing.
Composing roles, and deciding who holds which	A role is a name with 37 permissions ticked behind it, and that matrix is a screen rather than a dialog. The app shows you who is in an organization and sums each person up in a word; the panel is where roles are written and handed out. See Roles and permissions.

Settings → My account has a button for most of them. While you are signed in: Change password, Change email and Two-factor authentication each open that page of the panel directly, and Manage on the web opens the panel itself — which is where deleting your account lives. Create an account is on the same page while you are signed out.

Signed-in devices

Each machine you sign in from gets its own entry in a Signed-in devices list, named after that machine. You can see the list — and sign any entry out — in Settings → My account or in the account panel.

Each row shows the machine name, its platform, the Plexus version it signed in from, and when it was last used; the panel's table adds when the sign-in was created and when it expires. Revoking a device takes effect immediately: the next thing that machine asks the account service for is refused, and it signs itself out.

A sign-in also expires on its own if it goes unused for long enough. Using Plexus keeps it alive, so in practice this only catches a machine you stopped using — which is the point.

This list is also the off-switch for cross-device sync on a machine you are not sitting at. A revoked device stops sending and receiving on the spot. What it doesn't do is delete anything: everything that device synced stays on your account, and the sync version history keeps naming it, so a snapshot written by "MacBook Pro" still reads "MacBook Pro" after that laptop is gone. Revoking a stolen machine is a security action taken in a hurry, and it must not quietly take your configuration history with it. To remove the data itself, use Stop syncing and forget what we hold under Settings → Sync.

Signing out

Sign out is in the avatar menu and in Settings → My account. It removes the sign-in from this machine's keychain and ends that device's session on our side. Your organizations are not affected — sign back in and they are all still there. Neither is anything sync holds: this machine simply stops sending and receiving, its own settings, workspaces and projects untouched, until you sign in again.

Plexus can also sign you out on its own, and only ever for one reason: the account service refused the session. That happens if you revoked this device, deleted your account, or the sign-in expired. You get one notice saying so, and you can sign in again from the same place.

Deleting your account

You can delete your Plexus account yourself, from the account panel. It is a hard delete: the account, every device sign-in, and everything sync held for you — the current values, every workspace and project name, and all twenty retained versions — go with it, and we do not keep a copy. Every machine keeps its own settings, workspaces and projects exactly as they are.

One thing has to happen first — an organization cannot be left without an owner, so delete any organization you still own before deleting the account. The panel says so up front rather than letting you press a button that would fail.

Deleting your account does not affect your use of Plexus. The app does not require an account, so it keeps working exactly as it did.

What leaves your device

Signing in happens in your browser and sends your email address and password to the account service — that is what an account is — plus the machine name shown to you on the consent screen before it is stored. After that, the app sends only the sign-in it was given back, and only on the requests that make up the account: reading who you are when you open Settings → My account, reading or changing your organizations and your devices, reading a plan and the members, seats and invitations of the organization you have picked on Settings → Organizations, and ending the session when you sign out. Nothing else, and nothing on a schedule — no request goes out unless you opened one of those pages or pressed something. The one addition is that while either page is open, coming back to the Plexus window re-reads what it is showing, because a purchase or a seat change made in a browser tab has no way to announce itself.

Cross-device sync is the one thing that changes that, and only after you switch it on and approve a list of exactly what would go. From then on the app checks your account for changes on its own schedule and sends the settings, workspace names and project names you approved. It is off on every machine until somebody sitting at that machine turns it on there, and What leaves your device is the full enumeration.

Your code, your prompts and your agents' output are not part of any of this. They stay on your machine, signed in or not — and so do your sessions, your worktrees, every path on your disk and every branch a session works on, which not even sync carries. What sync does carry about a repository is its host/owner/name slug, its clone URL with any password stripped, and the base branch you configured for the project; What leaves your device is the whole list.

Next: Cross-device sync to make your settings follow you, Plans, seats and billing if you want to put people in an organization, Git providers if you also want Plexus to open pull requests, or Settings for everything else.