A workspace is a company. Everyone in it is an admin, a member or — when WayWiser writes bids for you — a WayWiser bid writer. WayWiser's own administrators are a separate platform role, described on Security and your data.
Admins and members
- Admins manage members, corpora, corpus access, API keys and company settings, and can delete the workspace. They can also sign off any question.
- Members work bids: everything on Find, Pipeline, the tender pages, the question workspace, Knowledge, Pricing and Activity.
The Company admin pages appear in the rail for admins only; a member who types the address gets a plain not-found page. A company always keeps at least one admin — demoting or removing the last one is refused; promote someone else first.
WayWiser bid writers
When WayWiser writes bids on your behalf, the writer works inside your workspace as a member of it with the role WayWiser bid writer. They can do everything a member does and set the workspace up for you — company settings, the logo, corpora and corpus access, and inviting your admins and members. They cannot change anyone's role, remove your people, export your data, mint API keys or delete the workspace; those stay with your own admins.
What they make is not shared until they share it. A document, fact or bid a bid writer creates carries one of two states, which only WayWiser staff see as a chip: Not shared or Shared with client. While it is not shared it does not appear on your pages at all — not in the pipeline, the corpus, the facts bank, Activity, search, the evidence panel or your data export — and it never grounds your drafts: what a bid's drafts and evidence may draw on follows the bid, so a shared bid is grounded in shared material only, whoever presses the button. The writer shares it with one click, and can take it back (confirmed first, because you may already have read it); sharing a document shares its text and the fact it carries, sharing a bid shares its questions with everything on them — drafts, reviews, comments, clarifications, the go/no-go — and the answers given about that bid in its interview, and a fact the writer typed by hand is shared on its own, as is an interview answer about the buyer or about your company (those outlive the bid and are reused on your other bids, so taking a bid back never takes them with it). Taking a document, a fact or a bid back also takes back what was drawn from it: any evidence panel that had quoted a passage from it (or every panel on that bid) is cleared and refilled the next time it opens. A document that is still being read cannot be shared or taken back until it finishes. Both directions are written to the audit log, and the per-bid action log names a change made by a bid writer. A draft of yours that cites a document they have since taken back keeps its words and shows the amber "unverified" flag.
On Team & access a bid writer appears with the fixed label, and Remove is the only control an admin has for them — their role cannot be changed, and a writer who joins your company for good gets an ordinary invitation. A bid writer can also remove a colleague, or leave the workspace themselves. Removing a bid writer takes effect at once; the page then says how many documents, tenders and facts they had not shared. Those stay in the workspace, invisible to you, and WayWiser can share or delete them on request. Company settings lists every bid writer currently in the workspace under WayWiser staff access, with who added them and when.
For WayWiser staff the rail also carries New client company: it creates a client's workspace, joins the creator as its bid writer and lands inside it, where the first step is inviting the client's admin. A bid writer can add a colleague from Team & access ("Add a bid writer", a fold above the member list: an existing WayWiser account, by e-mail, no invitation) and can preview exactly what the client sees with "View as client", which hides their not-shared work along with the platform tools.
Inviting people
On Team & access, Invite a teammate sits folded above the member list: open it from that line, or from the button of the same name at the top of the page. It is already open while the workspace has no admin of its own yet and while an invitation is pending. It sends an invitation by email through the sign-in provider, with the role the invitee will get and, optionally, which corpora they may read. The role applies when the invitation is accepted. Pending invitations are listed in the same fold until then. Invited teammates appear as assignable owners on every tender.
Membership comes only from invitations: someone who signs in without one sees "no company" until an invitation reaches them. That page explains itself.
Corpus access
By default every member can read every company corpus. Corpus access restricts a corpus to named members; no selection means open to all, and admins always have access. Restrictions apply to retrieval as well as browsing, so a draft for a restricted member never cites what they cannot see.
API keys
An API key is a credential for an agent or a script — Claude Code, an MCP client, a nightly report — that lets it use WayWiser as one member of this company. Admins mint them on the API keys page — Mint a key sits folded above the list of keys, open while there is no active key, and the button of the same name at the top of the page opens it; a key never does more than the member it acts as, and it can never manage members, keys or the company itself. What an agent can do with one, and how, is written up in the agent guide.
Minting a key asks for:
- Acts as — the member whose access the key borrows. When that person leaves the company the key stops working with them.
- Ceiling — member (work bids) or admin (company settings and corpora too). An admin ceiling needs an admin member.
- Read-only — reports and lookups only; anything that changes a record is refused.
- Expires in — 30 days, 90 days (the default) or a year.
The secret is shown once, on the page you land on after minting: copy it then, because WayWiser never shows it again. If it is lost, revoke the key and mint another. Revoking takes effect on the key's next request. Each key has its own rate limit, so an agent never eats its person's quota, and minting or revoking a key is written to the audit log.
Company settings
Admins set the per-bid cost used by the scorecard, the export branding (logo, accent colour and body face), and the email digest defaults. The page also shows:
- WayWiser staff access — the bid writers who are members of this workspace right now, and every time a WayWiser administrator who is not a member opened it, for the last 90 days.
- Export — a zip of your workspace records (tenders, questions, drafts, reviews, facts, documents and more) as JSON plus the original files. The download link is minted per click and lives 15 minutes; it is never stored.
- Delete workspace — type the company name to confirm. That starts a seven-day window you can cancel from the same page; after it, a nightly job erases the workspace's records and files.
Every one of these actions is written to the audit log.
Two companies
Someone who belongs to more than one company switches between them from the account block at the foot of the rail.