Workspace settings, members, billing

The brief

Workspace settings holds the brief — the facts, voice, guardrails and banned terms every pitch is drafted against, plus what the studio has learned from your team's edits. The studio writes to the brief while it is still researching a new workspace; saving the brief yourself takes it over for good — the studio stops writing to it, and later research is dropped rather than merged over a human's corrections.

The allowedEmails block is the one part of the brief the editor does not own. Who can sign in is changed on the access list further down the same page, never by typing in the brief: an edit that changes those lines saves everything else and leaves the list where it was. That is deliberate — the brief is a text box every member of the workspace can reach, and who belongs here should not be one edit away from anybody who can type.

Appearance — light, dark, or your machine's

Where it is: click your workspace's name at the top of the sidebar — the same menu that holds your other workspaces and Sign out — and Appearance is at its foot. It is also on Workspace settings, near the bottom. Both are the same control; changing one moves the other.

The menu is the quicker one, and it stays open while you click, so you can try light against dark with the studio visible behind it.

Three settings:

• System — follow whatever this computer is set to, and keep following it. A machine that switches to dark at sunset switches the studio with it, with no reload. This is the setting you start on.
• Light — always light, whatever the machine says.
• Dark — always dark.

Two things worth knowing:

It is saved on the device you set it on, not on the workspace. Your colleagues are not affected, and neither are your other workspaces — switching between clients never changes the studio's colour. Set it again on your laptop and your desktop if you want it in both places. A browser in private mode forgets it when the window closes.

Deliverables stay on white paper in either theme. A deck, one-pager, proposal or email is what your client will be looking at, so it is rendered the same way in both — a white sheet inside the dark studio. Shared links are all deliverable, so a share page is always light, whatever the person reading it has their machine set to. Printing is light for the same reason.

Your account — how you sign in, and your recovery number

Workspace settings carries one block that is yours rather than this workspace's: it follows you into every workspace you belong to, and your colleagues each keep their own.

How you sign in. Every passkey on your account, what each one is, when it was added and when it was last used — with Add a passkey to make another and Remove to forget one. A passkey is Face ID, Touch ID, Windows Hello or a security key; the secret half never leaves your device and it only ever works on this site, which is what makes it impossible to phish. Add one per device you use. Removing one stops it opening the studio — you can still sign in with Google or an emailed link. Full explanation in Getting started.

Recovery phone number. So we can get you back in if you lose access to your email, and so there is a way to reach you about the account itself. Pick your country, then write the number the way you normally would. It is used for nothing else unless you allow it below — never sent to a model, never in a deliverable — and you can clear it here whenever you like.

How we may reach you. The four contact permissions, exactly as the first card asked them: product email, account texts, product texts, phone calls. Every one is off unless you turned it on, and unticking one here takes it back straight away. Account email — sign-in links, receipts, service notices — is not on the list, because it is part of having an account.

Neither of these is deleted when a workspace is: how you sign in to your other workspaces is not one workspace's to take away.

What this workspace is called

The name at the top of your brief goes on everything the workspace produces. If your workspace was created from a checkout, by an agency, or from an uploaded list, the first owner or admin to sign in is asked once to confirm it. Confirming rewrites the brief itself, so every pitch afterwards is composed under the name you agreed to.

Members and access

Access is the workspace's email allowlist, managed from Workspace settings by its owner or an admin — named addresses only. Removing an address takes effect immediately. Sign-in is Google SSO or an emailed magic link; there are no passwords to reset.

Who added whom, and when

Every entry on the access list carries a line saying who put it there and on what date. It is there because "there is an address on this list and I cannot tell whether I added it" is a question the product should never make you guess at.

Three things worth knowing about that line:

• It starts from when we built it. Anything that was already on your list says added before Prospektor recorded this, and nothing can fill it in after the fact. Inventing a plausible name would be worse than the gap.
• A whole-company entry — one that looks like @yourcompany.com — shows the door it came through and no person, because nobody chose it: buying with a company address puts that company's domain on the list, which is how your colleagues walk in without being invited one at a time. Once an owner has settled it (below) the line also says kept by them, and the date.
• Some entries name a door instead of a person: by Prospektor when we put an address on by hand, or by their agency when the agency that set the workspace up did. We do not show you an address belonging to somebody who is not on your own list.

Everyone at your company can sign in — keep it, or narrow it

If you bought with a company address, your access list carries an entry like @yourcompany.com as well as your own address, and the list now says in words what it means: everyone at that company can sign in, including addresses that do not exist yet. That is how it has always worked; what is new is that the product says so, and that you get to decide about it.

Two answers, and only an owner may give either:

• Keep — you are happy for the whole company to walk in. Nothing changes except that the list stops asking, and records that you decided it.
• Narrow — the grant comes off, and from then on only the named addresses on your list can sign in. Everyone else at your company is signed out immediately.

Narrowing cannot be undone from inside Prospektor. Nothing in the product grants a whole company again — not settings, not us. If you narrow and then want a colleague back, add their address by name. Keeping, on the other hand, is not a lock: you can narrow a grant you kept, later, whenever you like.

Somebody from another company needs the owner's yes

Adding a colleague — anybody at a company already on your access list — works the way it always has: type the address, press Add, done.

Adding somebody from a different company is different if you are an admin rather than the owner. It becomes a request: the address is not added, that person cannot sign in, and the owner sees it on their own access list with Approve and Decline beside it. You will see it on yours too, marked as waiting for them.

This exists because letting a fourth party read every pitch a workspace has run is the owner's call — most often it is the agency that administers a workspace asking the client who owns it. An owner adding somebody from another company just adds them; there is nobody for them to ask.

Approving lets that person in exactly as an ordinary add does, and the access list then shows both names: who asked, and who approved. Declining leaves nothing behind — the person was never able to sign in, and is never told they were asked about.

You are told when access changes

If you own or administer a workspace, you get an email whenever an address is added to it, removed from it, or given a role — saying what changed, who did it, and linking straight to the access list. A role change also emails the person whose role moved, which matters most when it moved down: losing a role is otherwise invisible until you try to use it.

You also get one when an admin asks to add somebody from another company — headed approval needed, because nobody has been let in — and the admin who asked is emailed if you decline. Keeping a whole-company grant emails nobody: nothing about who can sign in changed.

You are not emailed about your own clicks, and somebody you have just added gets the invite instead of this notice. If nobody is recorded as the workspace's owner — which is true of a few of the oldest workspaces — the notice has nobody to go to and none is sent; ask us and we will set an owner.

Telling somebody they have access

Adding an address lets somebody in; it does not tell them. Every named entry on the access list carries an invite link beside it — click it and that person gets the same email an agency's client contact gets: what the workspace is, who set it up, and a sign-in link with their address already filled in. Use it for anyone who was added quietly, for a workspace made before invites existed, and for a client who says the first one never arrived — sending it twice is fine. Whole-domain entries (@example.com) have no single inbox behind them, so they carry no invite link.

Roles: owner, admin, member

Every named address on the access list holds one of three roles, shown beside it on the list. Your role on that same page says which one is yours and lists what it lets you do — and what it does not, with the role that would.

The short version: the ladder is about who joins, who administers and who destroys. It is not a read/write split. A member runs pitches and call preps, reads every run in the workspace, edits any deliverable, edits the brief's prose, mints share links and imports their own network. None of that changes with your role.

• Member — everything in the paragraph above. This is what everybody is unless somebody says otherwise.
• Admin — a member, plus the workspace's configuration: adding and removing people on the access list, sending invites, uploading the deliverable stylesheet, accepting or dismissing a rescan of the brief, managing a run or a share link somebody else started, and (in an agency workspace) creating client workspaces.
• Owner — an admin, plus the things nobody else may do: delete the workspace, change roles, settle a whole-company grant (keep it, or take it off the list for good), and approve or decline somebody from another company that an admin has asked to add.

The account that created a workspace is its owner — with one deliberate exception, which is the whole of the next section: when an agency creates a workspace for a client and names the client's email address, that client is the owner and the agency is an admin.

Changing somebody's role

Only an owner can. On the access list, each named address has a small role picker under it; choosing a role applies it at once, and everybody who owns or administers the workspace is emailed about it — including the person whose role changed.

Handing the workspace over is the same picker: choose owner for somebody else and you step down to admin in the same act. You keep members and the stylesheet; you lose deletion and roles. It is one action rather than two, so the workspace is never briefly owned by two people or by none.

A workspace can never be left with no owner. Demoting the last one, removing them from the access list, or asking us to free their address is refused with a message saying so — because appointing an owner is itself an owner's job, so there would be no way back. Give somebody else the owner role first.

What an admin cannot do to an owner

An admin adds and removes members. They cannot remove an owner, and they cannot remove another admin — only somebody above a person can take their access away. Removing yourself always works, whatever your role.

If an agency set your workspace up

Some workspaces are created by an agency or consultancy that runs Prospektor for their clients. If yours is one of them, Workspace settings carries a section called The agency above this workspace: who they are, which addresses on your own access list are theirs, and how either side ends the arrangement.

The workspace is yours

When the agency named your email address as they created the workspace, you own it and they are an admin of it. In practice that means they keep doing everything they do for you — running pitches, adding your colleagues, uploading your deliverable stylesheet, settling a rescan of your brief — and there are exactly two things they cannot do:

• They cannot delete your workspace. Deletion is the owner's, and the owner is you.
• They cannot remove you from it. An admin removes members, never an owner.

You can also do everything an owner does anywhere else: change roles, approve somebody from another company, settle a whole-company grant, and hand the workspace to a colleague.

Two honest limits:

• A workspace created without your email address on the form belongs to the agency, because at the moment it was made there was nobody else to give it to. That includes every row of a portfolio upload. The agency hands it over when you are on the list — see below.
• Workspaces created before 23 August 2026 were not changed. Nobody's ownership moved because we shipped a release. If your agency owns your workspace and you would rather own it, ask them to hand it over — or ask us.

Hand over to the client

An agency that owns a client's workspace hands it over from the same settings section: Hand over to the client, which makes the named client address the owner and steps the agency down to admin in one action. Nothing is briefly owned by two people or by none, and nothing about the work changes.

If the client's own address is not on the access list yet, the section says so instead of offering a button that cannot work — add them, then hand over.

Detaching — either side, immediately

Either side can end the arrangement, at any time, without the other side's agreement and with no waiting period:

• The client's owner presses Detach from ⟨agency⟩, and the agency's addresses come off the access list.
• The agency presses Detach from this client from inside that workspace, and does the same to its own addresses.

Nothing is deleted, on either side. Every pitch, call prep, share link, saved edit, network import and outcome stays exactly where it is, in the workspace, with whoever keeps it. Detaching removes access and the connection between the two workspaces; it removes no work.

Three things worth knowing:

• It takes effect at once, and both sides are emailed. There is no window in which the other side can stop it. If somebody can veto your leaving, you have not really been able to leave — so nobody can.
• The agency cannot detach from a workspace it is the only way into. That would leave a workspace nobody can open. The message says the way out: hand it over to the client first, then detach.
• A client whose agency was paying will be asked to pay. If the agency's subscription stops covering the workspace it will pause, and the lock screen's Re-subscribe button reopens the same studio — everything kept — against your own card. Nothing is deleted while it is paused. A paused workspace cannot be detached from until it is reopened, because a paused workspace answers nothing: re-subscribe first, then detach.

If a detach happened in error, the two halves go back separately: the workspace's owner adds the addresses again from the access list, and we can re-seat the connection between the two workspaces. Ask support.

More than one workspace

An account can belong to several workspaces; the switcher at the sidebar's head — your workspace's name — lists them all and switches between them.

An agency workspace — one that can create workspaces for its clients — is marked (Agency) in that list, and the client workspaces it created are indented beneath it. With ten workspaces on one account, the one that runs the others is the one you can find at a glance.

Agency-flagged workspaces additionally get New client workspace in that menu, for the agency's owner or admins — name the client and a live, researched workspace exists before the next screen. A plain member of an agency workspace cannot create client workspaces: each one is a workspace that will be billed, with your agency's name on somebody else's screen.

Who owns what that form creates. Name the client contact's email and the workspace is theirs — that address is its owner and you are its admin, so you run it for them but cannot delete it or remove them. Leave the contact field empty and the workspace stays yours until you hand it over (Hand over to the client, on its settings screen). Either way you can end the arrangement later, and so can they: see If an agency set your workspace up above, which is written for the client and is worth reading before you explain it to one.

Name the client contact's email and they also get an invite email — it says your agency set the workspace up for them, names you, says in plain words that the workspace is theirs and what you can and cannot do with it, and links straight to sign-in with their address prefilled. The tick-box is on by default; untick it to set things up quietly and invite them later. Whether the invite was sent (or could not be) is shown the moment you land in the new workspace. That invite belongs to this one-at-a-time form; a portfolio upload mails nobody.

A whole portfolio at once

Below that form, Portfolio upload points the same act at a list. Paste one company per line — Company name, website, the website optional — or choose a CSV and it is read into the box. Extra columns are ignored, and a header row is recognised as the format rather than treated as a company. Every row becomes its own client workspace with the research already reading that company's site. A portfolio row names no contact, so each of those workspaces is owned by your agency until you hand it over — there is nobody else to give it to at the moment it is made.

• The agency's owner or an admin presses it, the same rule as the one-at-a-time form beside it. Anyone in the workspace can open the results screen and watch.
• Up to 50 companies per upload, three researched at a time. A longer list is refused with the number in the message rather than quietly cut short; split it and upload the rest as a second portfolio.
• Rows that cannot be used are named, one by one — a line that is neither a company name nor a website, the same company twice, or a company your agency already has a workspace for.
• You stay where you are. Creating one workspace moves you into it; creating forty cannot, so the switcher gains them and you stay in the agency. A results screen shows every row filling in, and it has an address: /portfolio reopens your newest upload and lists the ones before it. Leave it and come back — the upload keeps going with the tab closed.
• Nobody is emailed. Each new workspace starts nearly empty on the completeness bar in its own Workspace settings, and that bar is the list of what its company still needs to answer. Send them their workspace link when you are ready for them.

Creating client workspaces — one at a time or a portfolio at a time — is free during the beta. Per-workspace billing arrives later: at creation you will choose whether it bills your agency or your client pays to unlock their workspace.

The deliverable stylesheet

Workspace settings → Deliverable stylesheet (owner or admin): upload a CSS file and every deliverable — on screen, on shares, in print — is styled with it. The studio's own chrome never changes; the stylesheet reaches your work and nothing else.

What Prospektor can see about your workspace

Prospektor keeps an operator view of every workspace as a record, so accounts can be set up, paused and supported without anybody at Prospektor being added to your allowlist. It holds the workspace's name and id, who it was provisioned for, its plan, whether it is paused, the addresses on its access list — and, since 23 Aug 2026, how much it is used: when somebody was last signed in, how many sign-ins there have been, how many pitch runs, call preps and other research the workspace has run, and what those cost Prospektor to run.

Those are counts and dates only. Nothing records your navigation — no page views, no searches, no dwell time, no analytics and no session recording of any kind. And the operator view does not open your work: pitches, your brief's prose, share links and your voice examples still need to be on this workspace's own access list, which nobody at Prospektor is unless you put them there.

Two things are deliberately outside that rule and are named here because they are. Feature requests you send through the composer, and support chat conversations, are both read by the Prospektor team — the first is a message to them by definition, the second so that a question that keeps coming up becomes a fix. Each of those records the studio screen you were on when you wrote it, because "where were they when this went wrong" is most of what makes a bug report useful. That is the only place a screen is ever recorded, and only for something you deliberately sent.

Billing, pausing, deleting

• The subscription is $999/month per workspace, taken by Stripe through prospektor.ai — the studio itself holds no card details.
• A paused workspace means the subscription behind it lapsed; the lock screen's resubscribe button reopens the same studio with everything kept.
• Workspace deletion lives in Workspace settings' danger zone, and only an owner may use it — not an admin, deliberately: it is the one act in the product that cannot be undone. Deletion removes the workspace's records; there is no undo. A handful of workspaces are set up by Prospektor from the codebase rather than through the product; those say so and cannot be deleted from the danger zone at all — nothing is removed and support does it for you.
• What a deletion leaves behind: one unlinked row, and it names nobody. Prospektor keeps a single bookkeeping record per workspace so it can measure how many customers stay and how many leave. It holds no email address, no company name and nothing you or your team wrote — a signup date, whether the workspace was paid or comped, how it was created, when a deliverable was first saved in it, and the dates it was paused or closed. When a workspace is deleted, the identifier on that row is replaced with a one-way hash, so what remains cannot be linked back to you. Everything else — every pitch, prep, share, import, note and setting — is removed.
• Billing disputes and refunds are handled by a human over email — the support chat can gather the details but never touches money.