# Mission Control > Mission Control is a human-in-the-loop inbox for finance workflows. It reads finance email, drafts the Slack, Drive, Sheets and email actions each case needs, and runs nothing until a reviewer approves the exact payload. --- # Every agent action, under Mission Control Mission Control reads your finance inbox, drafts the follow-up each email needs, and waits. Nothing is posted, filed or sent until a person approves the exact payload. ## This is the whole job. One case, three drafted actions, one decision. Approve and they run. Reject and nothing does. ## Steps 1. **Mail comes in** — A Gmail watch drops incoming invoices and requests into the review queue as soon as they arrive. 2. **Codex drafts** — Slack, Drive, Sheets and email payloads are prepared for review. Payment stays off. 3. **You decide** — Open each case, check every drafted action, then approve the exact payload — or reject it. ## Runs on your own access, not ours. - **Gmail, Drive, Sheets** — Watch the mailbox, file the attachment, append the row. - **Slack** — Notify the finance channel with the exact text you approved. - **Povio Dashboard** — Read timesheets and project tools when a workflow needs them. ## Built for the finance work that arrives by email Supplier invoices, statements, payment reminders, requests for the monthly hours report. Most of it follows the same few steps every time: tell the right channel, file the document, log a row, reply to the sender. The steps are simple. Getting them right every time, without anyone checking, is the hard part. Mission Control lets an AI do the repetitive part — reading the email and drafting each step — while a person keeps the decision. You write the workflow once, in your own words. Every case then lands in a reviewer inbox with its drafted actions laid out next to the source email. Approve, and the app carries them out. Reject, and nothing happens. ## What stays true on every case - Nothing runs without an explicit approval from a person. - Actions execute with the approver's own Google and Slack access, so existing permissions keep applying. - Payment execution is switched off. - Every decision is recorded: who approved or rejected, when, and what ran. [Book a demo](/contact) Source: https://mission-control.povio.dev/ --- # One email, five stages, one human decision. Mission Control splits finance automation into the part a model is good at — reading and drafting — and the part a person should own: deciding what actually happens. ## Steps 1. **Inbox** — A connected Gmail mailbox receives an invoice or request. Mission Control opens a case with the email and its attachments. 2. **Drafted actions** — Codex matches the case to one of your workflows and drafts the payload for every step. 3. **Approval** — A reviewer checks each drafted action against the source email, then approves or rejects the case. 4. **Execution** — Approved steps run in order with the approver's own Google and Slack access. 5. **Audit** — The decision, the approved payload and each step's result are recorded on the case. ## 1. Inbox You connect the Gmail mailboxes that receive finance mail — an accounts-payable address, an office inbox, your own. Mission Control watches them through Gmail's push notifications. When a message arrives, it opens a case in the reviewer inbox with the original email, sender and attachments attached. ## 2. Drafted actions Workflows are written by your team, in plain language: what kind of email this is, and what should happen next. A typical one says: when a supplier invoice for the Ljubljana office arrives, post it to the finance channel, upload the PDF to the invoices folder, and add a row to the invoice register. Codex — the AI model running inside Mission Control — reads the case, picks the matching workflow and drafts the exact payload for every step: the Slack channel and message text, the Drive folder and file name, the spreadsheet and row values, the reply's recipients and body. It reads through the connections of the mailbox owner. It drafts; it cannot execute anything. ## 3. Approval The reviewer sees each case with its drafted actions listed next to the source email. They check the payloads — is that the right amount, the right folder, the right channel — and make one decision for the case. Approve, and the exact payloads shown are queued for execution. Reject, and nothing runs. There is no "auto-approve after a while" and no background path that skips the reviewer. ## 4. Execution Approved steps run in order using the approver's own connections. The Slack message is posted by them. The file is uploaded to a Drive folder they can access. The row is appended to a sheet they can edit. If the approver doesn't have access to something, the step fails instead of quietly using broader credentials. Payment execution is switched off. Mission Control can file an invoice and tell people about it; it does not pay it. ## 5. Audit Each decision is recorded on the case: who approved or rejected it, when, the payload that was approved, and what each step returned. When someone asks next quarter why a file is in that folder, the answer is on the case. [See it on your own workflow](/contact) Source: https://mission-control.povio.dev/how-it-works --- # The repetitive finance work that starts with an email. If a task begins in an inbox and ends in Slack, Drive, Sheets or a reply, it is a good fit. Each of these runs as a workflow your team writes and a reviewer approves. ## Common workflows - **Supplier invoice intake** — An invoice arrives by email. Mission Control drafts a post to the finance channel, uploads the PDF to the right Drive folder and appends a row to the invoice register. - **Monthly billable hours** — At month end, read logged hours per project from Povio Dashboard and draft the billable-hours rows and summary for the office lead to approve. - **Filing to Drive and Sheets** — Statements, receipts and contracts land in consistently named folders, with a matching row in the tracking sheet. - **Slack notifications** — Tell the right channel what arrived and what needs attention, using the exact wording the reviewer approved. - **Routine email replies** — Acknowledge receipt, ask a supplier for a missing purchase order number, or forward a document to the accountant. - **Your own workflow** — Describe the steps in plain language. Mission Control drafts them on every matching case; you approve each one. ## Supplier invoice intake Invoices addressed to an office arrive at a shared mailbox. Today someone opens each one, saves the PDF, types the supplier, number, amount and due date into a sheet, and lets the finance channel know. With Mission Control, each invoice becomes a case with those three steps already drafted. The reviewer checks the numbers against the PDF and approves. ## Monthly billable hours Every month someone compiles billable hours per project and client. Mission Control can read logged hours from Povio Dashboard through the reviewer's own connection, draft the rows for the monthly report in Google Sheets, and draft a Slack summary for the people who need it. Nothing is written until the report is approved. ## Filing to Drive and Sheets Documents that need to be kept — bank statements, signed contracts, receipts — get filed to a predictable place with a predictable name, and logged where your team already looks. The reviewer sees the target folder and file name before anything is uploaded. ## Slack notifications A drafted Slack message shows the channel and the full text. The reviewer approves the exact wording that will be posted, through their own Slack connection. ## Routine email replies Short, repetitive replies are drafted with recipients and body visible. Approve to send from the connected mailbox. ## What Mission Control will not do - Pay invoices. Payment execution is switched off. - Act on a case nobody approved. - Use someone else's access to get around a missing permission. [Talk through your workflow](/contact) Source: https://mission-control.povio.dev/use-cases --- # The tools your finance work already lives in. Mission Control connects to six services. Each person connects their own accounts, and every approved action runs with the approver's access — not a shared service account. ## Six connections, each with a clear job. - **Gmail** — Watches connected mailboxes for new mail, reads messages and attachments for each case, and sends approved replies. - **Google Drive** — Uploads approved attachments to the folder and file name shown in the draft. - **Google Sheets** — Appends approved rows to registers and reports, column by column as drafted. - **Slack** — Posts the approved message to the approved channel through the approver's Slack connection — as the Mission Control app, or as the approver when the workflow is set up that way. - **Povio Dashboard** — Reads timesheets and project data when a workflow needs them, such as the monthly billable-hours report. - **tl;dv** — Reads recent meeting recordings when a workflow uses them as context, and imports a recording once the import is approved. ## Connections are per person There is no organisation-wide service account. Each user connects their own Google, Slack, Povio Dashboard and tl;dv accounts on the Connections page, and can disconnect at any time. What Mission Control can do on someone's behalf is limited to what that person can already do. ## Whose access is used, and when - **Reading a case** — Codex reads the email, attachments and any lookups it needs through the connections of the mailbox owner. - **Executing an approved step** — the step runs with the approver's connection. The Slack post goes out through their Slack connection (under their own name if the workflow asks for it); the Drive upload and Sheets row are written with their permissions. If the approver lacks access to a folder, sheet or channel, the step fails and the failure is recorded on the case. ## Not on the list Payment providers and banking connections are not supported, and payment execution is switched off. If you need a connection that isn't here, tell us what the workflow is. [Ask about an integration](/contact) Source: https://mission-control.povio.dev/integrations --- # Automation that cannot act on its own. Mission Control is built so the AI can only propose. A person approves every action, the action runs with that person's own access, and the decision is recorded. ## The guarantees - **Nothing runs without approval** — Every drafted action waits in the reviewer inbox. Rejecting a case means nothing executes. - **The approver's own tokens** — Approved steps run with the approver's Google and Slack access, so existing permissions keep applying. - **Per-user connections** — Each person connects and disconnects their own accounts. There is no shared service account. - **Payment is off** — Mission Control files and reports invoices. It does not pay them. - **Audit trail on every case** — Who decided, when, the approved payload and each step's result are recorded. - **The model only drafts** — Codex reads cases and proposes payloads. It has no path to execute anything itself. ## Approval is the only way to execute Drafting and execution are separate. Codex produces a proposed payload for each step; it is stored on the case and shown to a reviewer. Only an explicit approval from a signed-in person queues those exact payloads for execution. There is no timeout that approves on its own and no setting that skips review. ## Execution uses the approver's access When a case is approved, each step runs with the approver's own OAuth connection. That has two effects. Actions are attributable — a Slack post shows who approved it. And permissions you already manage in Google Workspace and Slack keep applying: if the approver cannot write to a folder, neither can Mission Control on their behalf. ## Reads use the mailbox owner's access To draft a case, Codex reads the email and any context it needs through the connections of the person who owns the mailbox. It does not borrow anyone else's access. ## Connections belong to people Google, Slack and Povio Dashboard connections are created by each user for themselves and can be removed at any time from the Connections page. ## Payment stays disabled Mission Control does not execute payments. Invoice workflows end at notification, filing and logging. ## Every decision is recorded Each case keeps its history: the source email, the drafted payloads, who approved or rejected the case and when, and the result returned by every executed step. [Ask a security question](/contact) Source: https://mission-control.povio.dev/security --- # Same discipline, different inboxes. Every business gets invoices, statements and requests by email. What differs is what has to happen next. Here is how Mission Control fits three kinds of teams. ## Industries - [Professional services](/industries/professional-services) — Agencies and consultancies juggling supplier invoices across offices and billable hours across projects. - [Accounting](/industries/accounting) (example scenario) — Practices receiving a constant flow of client invoices, receipts and statements that must be filed correctly. - [SaaS](/industries/saas) (example scenario) — Lean finance teams tracking a long tail of vendor and infrastructure invoices across tools. The professional services page tells the story of Povio, the software agency that builds and uses Mission Control. The accounting and SaaS pages are example scenarios: illustrations of how the same workflows apply, not customer stories. [Book a demo](/contact) Source: https://mission-control.povio.dev/industries --- # Invoices across offices. Hours across projects. Agencies and consultancies run on two streams of finance work: supplier invoices arriving at each office, and billable hours that have to become accurate client reports every month. ## Where the time goes - Supplier invoices arrive at a shared office mailbox and wait for someone to save, log and announce them. - Each office has its own folder structure and register, and getting both right depends on who is on duty. - Monthly billable hours have to be pulled per project from the time-tracking tool and reshaped into a report by hand. - When a number is wrong, nobody can easily see who entered it or where it came from. ## Relevant workflows - **Office invoice intake** — Post each supplier invoice to the finance Slack channel, upload the PDF to the office's invoices folder in Drive, and append it to the office invoice register in Sheets. - **Monthly billable hours** — Read logged hours per project from Povio Dashboard and draft the monthly billable-hours rows and summary for approval. - **Client and supplier replies** — Draft short acknowledgements and requests for missing details, sent from the connected mailbox once approved. ## How we use it: Povio Povio is a software agency and the team that builds Mission Control. We built it for our own finance work first, starting with these two workflows. Like most agencies, Povio's finance work is a steady stream of email: supplier invoices addressed to the Slovenian office, and a monthly report of billable hours for the Ljubljana office. **Invoices to the Slovenian office.** Supplier invoices arrive at the office mailbox. For each one, Mission Control drafts three actions: a post to the finance Slack channel, an upload of the PDF to the office's invoices folder in Google Drive, and a new row in the office invoice register in Google Sheets. A reviewer checks the supplier, number and amount against the PDF and approves. The actions run with the reviewer's own Google and Slack access. **Monthly billable hours for Ljubljana.** At the end of each month, Mission Control reads logged hours from Povio Dashboard and drafts the billable-hours report for the Ljubljana office. The office lead reviews the figures before anything is written. In both workflows, payment stays off: invoices are filed, logged and announced, and paying them remains a separate, human task. ## Results - Supplier invoices handled per month: 60+ - From invoice email to filed and logged: Under 5 min - Monthly billable-hours report, down from half a day: ~15 min [Book a demo](/contact) Source: https://mission-control.povio.dev/industries/professional-services --- # Client documents, filed right the first time. An accounting practice receives documents from dozens of clients by email. Each one has to land in the right client folder, be logged, and sometimes be acknowledged — every time, without mix-ups. > Example scenario: an illustration of how Mission Control could be used, not a customer story. ## Where the time goes - Clients email invoices, receipts and bank statements to a shared address, in every possible format and naming scheme. - Filing a document into the wrong client's folder is a real confidentiality problem, not just an inconvenience. - Staff spend the start of every month chasing missing documents and confirming what has arrived. ## Relevant workflows - **Client document intake** — Upload each attachment to the client's folder in Drive with a consistent name, and append a row to that client's document log in Sheets. - **Missing-document requests** — Draft a short reply asking the client for anything the workflow expects but didn't find, such as a missing statement page. - **Team notifications** — Post a summary to the client's Slack channel so the responsible accountant knows what arrived. ## Example scenario: a small practice at month end This is an illustration of how the workflows could run, not a customer story. Imagine a practice of a few accountants serving small businesses. At the start of each month, clients send their invoices, receipts and statements to one shared address. With Mission Control, each incoming email becomes a case. Codex identifies the client from the sender and content, then drafts the actions: upload the attachments to that client's Drive folder under a consistent name, add a row to the client's document log, and post a note in the client's Slack channel. If a statement seems to be missing pages, it also drafts a polite reply asking for them. The accountant on duty reviews each case. The target folder is shown explicitly, so a document heading for the wrong client is caught before it is filed. Approved actions run with that accountant's own Google and Slack access, and every decision is recorded on the case. [Book a demo](/contact) Source: https://mission-control.povio.dev/industries/accounting --- # A long tail of vendor invoices, kept in order. A SaaS company pays for dozens of tools and cloud services. Invoices and receipts arrive by email from all of them, and someone has to keep the spend tracker and the budget owners up to date. > Example scenario: an illustration of how Mission Control could be used, not a customer story. ## Where the time goes - Vendor invoices and renewal notices arrive at different inboxes, often addressed to whoever signed up for the tool. - The spend tracker falls behind, so budget owners find out about renewals after they've been charged. - Receipts needed for the accountant are scattered across mailboxes at quarter end. ## Relevant workflows - **Vendor invoice intake** — File each vendor invoice to the right Drive folder and append vendor, amount, period and owner to the spend tracker in Sheets. - **Budget owner notifications** — Post a Slack message to the owning team's channel when an invoice or renewal notice for their tool arrives. - **Receipt collection for the accountant** — Draft an email forwarding the month's receipts to the external accountant once they are filed. ## Example scenario: a lean finance function This is an illustration of how the workflows could run, not a customer story. Imagine a SaaS company with a one- or two-person finance function. Engineering, sales and marketing each sign up for their own tools, and the invoices go wherever the account was created. Each team connects the mailbox that receives those invoices. When one arrives, Mission Control drafts the follow-up: upload the PDF to the vendor's folder in Drive, add a row to the spend tracker with the vendor, amount and billing period, and post a short note to the owning team's Slack channel. The finance lead reviews each case and approves. Actions run with their own access, so the spend tracker stays under the permissions finance already controls. At month end, a drafted email collects the filed receipts for the external accountant — sent only once approved. [Book a demo](/contact) Source: https://mission-control.povio.dev/industries/saas --- # Plans that grow with your reviewers. We agree pricing with you based on the mailboxes you connect and the people who review. Every plan includes approval on every action, per-user connections and the full audit trail. ## Starter One finance owner, one inbox. For a founder, office manager or single bookkeeper who handles finance mail alone. Features: - Every connection: Gmail, Drive, Sheets, Slack, Povio Dashboard and tl;dv - Drafted actions on every matching email - Approval on every action - Audit trail on every case Price: [Talk to us](/contact) ## Team A finance team sharing the queue. For finance and operations teams where several people review and approve. Features: - Everything in Starter - Several reviewers working the same inbox - Help writing your first workflows - Priority support Price: [Talk to us](/contact) ## Enterprise Your own review, your own terms. For organisations that need a security review, custom integrations or dedicated support. Features: - Everything in Team - Security review and documentation support - Integration requests scoped with our team - Dedicated onboarding and support contact Price: [Talk to us](/contact) ## Included in every plan - Human approval on every action, with no way to skip review. - Execution with each approver's own Google and Slack access. - Per-user connections to Gmail, Google Drive, Google Sheets, Slack, Povio Dashboard and tl;dv. - An audit trail on every case. - Payment execution switched off. ## Not sure which plan fits? Tell us which mailboxes you want to connect and what should happen to the email that arrives there. We'll suggest a plan and show you the workflow running. [Talk to us](/contact) Source: https://mission-control.povio.dev/pricing --- # Show us what lands in your finance inbox. Tell us a little about your team and the email you'd like to stop handling by hand. We'll reply to set up a demo on a workflow like yours. ## What happens next 1. We read your message and reply by email. 2. We set up a short call to walk through your workflow. 3. We show you Mission Control drafting and executing that workflow, with you approving each case. Source: https://mission-control.povio.dev/contact