Help and recovery

Four steps, in this order: name the business and its timezone, connect one account you already use, let Rhea — your Chief of Staff — propose a first teammate, then run one job end to end with approvals on. Do not schedule anything until you have watched a job finish once.

Tell Rhea what the business does and what keeps slipping. It proposes a role, a name and the jobs that role would take. You confirm four things before it exists: the name, the model account it runs on, the connections it may use, and whether each of those is read-only or read-write.

Describe it the way you would brief a new hire — the outcome, where the information lives, and who has to say yes. Rhea writes it back as a numbered procedure. Edit that procedure like a document before you run it; the words in it are what the teammate follows.

Settings → Members. A member works on the board with you and can be given approval authority up to a limit you set. A viewer reads only what has been shared with them and can never approve, send or pay. Both are humans; a teammate is never a member.

Four columns: Backlog is written but not started, Needs you is waiting on a human decision, In progress is running now, Done is finished with its receipts attached. Needs you is your queue — nothing in it moves on its own.

Integrations → pick the provider → sign in on the provider's own page. You then choose which resources are in scope: which mailbox, which calendar, which spreadsheet, which folder. A provider is connected only after it answers a real read; a logo on the list is not a connection.

Grants are per teammate, per account, per resource. Read-only lets it look and draft; read-write lets it change something in the tool — and outbound acts still queue for approval unless you delegated a limit. Changing a grant takes effect on the next call, and the change itself is a receipt.

The provider revoked or expired the grant — usually a password change, a new device policy or a scope you removed on their side. The teammate stops rather than guessing, the job holds at its last checkpoint, and the account shows the state plainly. See the recovery paths below.

Sign in with a ChatGPT, Claude or Gemini plan through its own login, or paste an API key for a provider that offers one. The mechanism — plan sign-in or API key — is shown separately from the state, so “unverified key” never reads as “ready”. A blocked account never renders as connected.

Order the accounts a teammate may use. When the first hits its limit, the job pauses at its last checkpoint and continues on the next one — nothing already done is repeated, and the run shows which account did which part. If no fallback is set, the job waits for the limit to lift and tells you when that is.

Integrations → Custom → add the server address and pick the credential it should use from the vault. Its actions appear only after the server answers a real capability listing. Until then it shows as unverified, with the prerequisite it is missing spelled out.

The exact thing, never a summary of it: the recipient, the subject, the full body, the amount and currency, the account it would be sent or paid from, the resource it would change, and when the request expires. You are approving that text, that number and that account — nothing broader.

Then it is not approved. An approval is bound to the exact revision you read; any edit to the recipient, body, amount or account voids it and raises a fresh request showing what changed. Approving an older draft never authorises a newer one.

You can let a teammate act without asking, up to a boundary you write down: which kind of act, to which recipients or accounts, and up to which amount. Anything outside the boundary still comes to you. The limit is shown on the request itself, so you can see why something did or did not need a yes.

A per-teammate ceiling for a day — a number of outbound messages, or a total amount. When the cap is reached the teammate stops and asks instead of continuing quietly. The cap and how much of it is used are both visible on the teammate's profile.

Requests carry an expiry so a yes given days later cannot act on stale facts. An expired request is closed, not silently retried; the job holds and the thread says so. Reopen it from the job and the teammate rebuilds the draft against today's data before asking again.

An always-on machine that belongs to your workspace, where the browsing actually happens. Each teammate has its own browser profile on it: its own logins, cookies and downloads. Two teammates never share a session, and moving a file between them is a deliberate act.

Open a teammate's computer to watch what it is doing, live. Taking control pauses the teammate and hands you the keyboard — useful for a login it cannot pass or a page that needs a human. The mode you are in is stated on screen; the teammate resumes only when you hand it back.

Describe the task first — the Start button stays disabled until you do — then take control and do it once while the recorder watches. Recording pauses before a sign-in. The captured step list shows that gap explicitly and no password is ever stored in it; the credential comes from the vault at run time instead.

A recording becomes a numbered procedure in plain words, not a locked macro. Rewrite a step, delete one, add a check, mark a point where it must ask you. Save a revision and the next run follows the new text; older runs stay attached to the revision they actually followed.

A teammate can have its own address, so a client replies to it rather than to you. The workspace plan states how many inboxes are included and what each extra one costs — the pricing page reads both from the configured plan. A reply lands back in the thread of the job that started it, not in a separate pile.

Inbound mail from a sender the workspace does not recognise, or carrying an instruction that would change what a teammate does, is held rather than acted on. You see it, with the reason. Release it and it enters the thread as ordinary content; a quarantined message never steers a job while it waits.

Blocked is a real state with a named reason: the daily cap is spent, the recipient is outside a delegated limit, the inbox is not verified, or the provider rejected it. The draft is kept as it was written and the recovery step is on the block itself. Nothing is ever reported as sent when it was not.

A job has one thread, and that thread can be reached from any channel you connect. Answer from your phone in Telegram and the answer is on the job in the workspace. Approvals asked in a channel show the same exact draft you would see on the board.

Settings → Email domains. Until the domain's records verify, the inbox can receive but not send, and it says so rather than queueing silently. Signature and reply-to are per inbox, so a client care teammate and a billing teammate can sign differently.

One workspace: your teammates, the board, the approval queue, the vault, the computer, the integrations and the export. The price, the included inboxes and the monthly research allowance are whatever the configured plan states — the pricing page reads them live rather than repeating a number here. Your own AI plan is billed by its provider, exactly as it is today.

Built-in research tools draw on the plan's monthly allowance; beyond it, credits are charged at what the provider charges, with the balance shown before a tool that spends it runs. When the balance is empty the tool is blocked with its price on the block, never run at a surprise cost.

Settings → Billing. Inboxes beyond the ones the plan includes are charged at the plan's stated rate and prorate on the change. Removing an inbox stops new mail immediately; the threads it took part in stay on their jobs and in the export.

Settings → Billing opens the payment provider's own portal, where the card, the billing address and every past invoice live. A change there is reflected in the workspace only after the provider confirms it — the workspace never shows a plan as paid on optimism.

Cancel from Billing and you keep the workspace until the period you paid for ends. Before or after that, Settings → Exports produces the full history: procedures, runs, threads, documents, receipts and memory. Disconnecting your accounts revokes Crewvia's access at the provider; nothing of yours stays behind a login you no longer have.