Home › Using OPSAVOR
Beta, demo and planned features
Know whether you are reading beta instructions, exploring sample data, or looking at a planned workflow.
Foundation is a closed, invite-only beta.
These guides are for invited restaurant users and the OPSAVOR staff supporting them. Use the workspace address in your invitation. Access and features depend on your restaurant's release; this is not a general launch announcement.
Three different experiences
On a narrow screen, scroll the comparison sideways. With a keyboard, focus the comparison and use the arrow keys.
| Experience | What it means | Where to go |
|---|---|---|
| Foundation beta | Your invited workspace, with records your team supplies and confirms. These guides describe document intake, review, reports, plugins and Savy. Check your release and role before relying on a feature. | Getting started · Platform release notes |
| Public demo | Fictional restaurants and sample records show the wider product direction. Demo Savy uses rules on sample records. Outside actions are simulated; it does not connect to your business or move money. | Explore the sample-data demo |
| Planned workflows | Live system connections and broader connected workflows are not promised by this documentation. A sample walkthrough does not establish availability in your beta workspace. | Product roadmap · Sales-to-prep example |
Before you follow a guide
- Check the restaurant. Use your own invited workspace, not the public demo.
- Check the release and your role. A missing page may depend on either. Ask your account owner or support to confirm what is enabled; do not assume a marketing screenshot is your current interface.
- Check the records. Missing or unconfirmed data stays incomplete. A setup checklist is not proof that every report or connection is ready.
Plugins depend on your release
Insight such as the daily Brief comes from plugins, and which ones you have depends on your platform release and on what OPSAVOR has turned on for you.
| Release | What it adds |
|---|---|
| v0.11.0 | The built-in Pulse, Brief, insight cards, alerts and restaurant metrics are removed. They return as plugins. |
| v0.12.0 | Plugins, and the Business Intelligence plugin with its daily Brief. |
| v0.13.0 | Savy skills, and building a plugin with Savy. v0.13.1 tunes the builder. |
| v0.14.0 | Mark reviewed and Undo on plugin lists, and the Missing bills, Supplier price watch and Statement check plugins. |
| v0.15.0 | Flows (plugins that message your team and call web hooks), your Inbox, and the Plugin maker. |
| v0.22.0 | Passkeys for sign-in, and plugin approvals that run an effect once. |
| v0.23.0 | Recovery codes and a two-factor policy for owners and admins; month-end checks, a balance sheet and a bank-balance check; PDF plugin reports, cross-plugin reads and outbound documents. |
| v0.24.0 | Changing the email you sign in with; cash-basis ledger views, manual journal drafts, and a tamper-evident audit history. |
| v0.24.1 | Stronger account, team and API-key protections; cleaner sales and ledger figures; safer plugin inputs and outbound calls. |
| v0.25.0 | The in-app App Store and plugin suites; more store integrations; organisation trees and staff profile pages; paging through inbound email. |
| v0.26.0 | Plugin values for workspace names and tokens, with secrets kept write-only and sealed; the platform's own secrets are sealed too. |
| v0.27.0 | Plugin apps with their own screens, memory and code; agents a plugin can offer; Daily Pulse and the shorter menu; owner-set email notices; book safeguards and sign-in branding. |
| v0.28.0 | Two-page invoices and multi-invoice photos; threaded comments and mentions; statement matching, exceptions and bank tie-out; document-date sorting and "Not an invoice"; plans and notification allowances; the Books and Cash-basis plugins; review policy and vendor watch; account sessions, sign-in methods and connected apps; sensitive:view and people:view on documents; safer migrations, sources on every row and soft delete. |
The version in this documentation's footer identifies the docs, not your restaurant's platform version. What's new records platform changes. Platform terms explain beta access.