October 2026

6 October

sanda

• becca is now sanda. The name, the logo (three salmon circles) and the colours have changed across the website, the console, the reports portal, emails and these docs. Nothing else has: your workspace, warehouse, connections and credentials stay exactly as they were.
• sanda has new addresses, on sanda-os.com.au: the website is sanda-os.com.au, the console is console.sanda-os.com.au, and the MCP endpoint and OData feeds are under https://console.sanda-os.com.au/api/. The reports portal and these docs moved the same way. Every old becca-os.com address, and the same names on sanda-os.com, takes you to its new home, so bookmarks and links in old emails still work. A Claude connection or OData feed you set up on console.becca-os.com keeps working where it is; point it at the new address when you next touch it. You sign in again once, on the new console. Email moved too: sign-in links and reports now come from noreply@sanda-os.com.au, so if your IT team allows senders by name, add that one. Write to us at hello@sanda-os.com.au. See connect Claude and OData.
• Text is darker and easier to read everywhere, small print and labels most of all, and the dark panels are now a warm charcoal.
• sanda is now run by Sanda Technologies Pty Ltd (ABN 63 702 995 015, ACN 702 995 015). The terms and the privacy policy name the company from 6 October 2026, and the footer shows both numbers. The next time you open the console it asks you to read and accept the privacy policy again. Account holders are told by email before the updated terms apply to a workspace that signed up earlier. See privacy.
• Report colours have a new default, salmon, to match. A workspace that never picked its colours now draws reports in salmon. If you chose cherry before, it is still there and still yours. See workspace settings.
• An authenticator app set up from today lists your two-step code under sanda. One you set up earlier keeps the label it had, and its codes still work.

Semantic fluid

• Numbers measured on different tables sit in one answer everywhere sanda reads the semantic fluid, the OData feed and pushes included. Put revenue, summed over order lines, beside order count, counted over orders, and each order is counted once however many lines it has. A table counted this way needs its key columns set. See query the fluid.
• A metric built from metrics on other tables runs wherever a relationship joins the tables. Each part is worked out on its own table, so {revenue} / nullif({order count}, 0) is revenue per order. See metrics.
• A metric's own condition applies to that number alone. Two metrics whose conditions disagree sit side by side instead of being refused, and a metric that counts only paid invoices no longer narrows the invoice count beside it. A metric built from others keeps each part's own condition. See metrics.
• A row whose relationship finds no match is kept, with null on the other side, rather than left out, so a breakdown still adds up to its total.
• Every question now goes straight to your warehouse. One asked again within a few seconds is answered from the first answer, and a report with many blocks fills in from the top. See blocks.

1 to 3 October

Push

• Push is in the console, under Activate · Push, once it is switched on for your console. Until then it isn't listed. Connect a Salesforce org by signing in to Salesforce as the user sanda writes as, then create a push: the object, how each record is found, and the sanda value for each field. Each run sends only the records whose values changed, and a run where nothing changed makes no Salesforce call. See Push.
• A new push opens with Preview the next run: how many records a run would send, the first twenty, and the rows that can't be sent as they stand. Saving sends nothing, so you can check the preview before the first run. Anyone who can open the console can preview, read-only members included.
• A push's Runs says what each run did. Open one to see the records it couldn't deliver, with Salesforce's own reason and sanda's hint beside it. See runs and refusals.
• Push to Salesforce is included on Standard and Enterprise, and in a trial. A workspace holds up to 1 on Standard and any number on Enterprise. The editions table, Settings · Plan & budget and the pricing page list it. See editions.

Workspace and security

• Settings is now six tabs across the top of the page instead of one long page: Workspace, Plan & budget, Team, cherry, Security and Integrations. Report colours have moved into Workspace, and closing or deleting the workspace is at the foot of that tab. The tab you are on is kept in the address, so a link or a reload opens the same one. See workspace settings.
• Signup asks where your data is held. Under Data region, you choose the region a new workspace lives in: its warehouse is created there, and loading and modelling run there. Workspaces can be created in Australia (Sydney). See quickstart.
• A workspace stays in the region it was created in. Settings · Workspace now shows its Data region rather than offering a choice. See workspace settings.
• The global data plane, which was announced and never opened, is no longer listed on the pricing page or in Settings.
• Codes tried when turning off two-step sign-in now count toward the same hourly limit as codes tried at sign-in. See two-step verification.
• Connecting an assistant to a workspace that requires two-step sign-in now asks you to have it set up, even when you are signed in to a different workspace. See Connect Claude.
• A portal handoff link opened from another website no longer signs anyone in. See the reports portal.
• A closed workspace narrows every credential to the reading it already had. A credential that could only add rows or send reports can no longer do either. See permissions and approvals.
• Fixed: the SQL shell could be made to run a second statement after the first, so a read-only statement could commit a change. It now runs exactly one statement, as it says.
• Fixed: duplicating a private report, or saving it as a template, made a copy everyone in the workspace could open. The copy is now private. See share a report.
• Fixed: the Report schedules page listed the schedules of private reports to people who could not open them.
• Fixed: a report's shared conversation could be reached from cherry's thread list by the person who typed first in it, after they lost access to the report.

cherry

• Only owners and admins add to or remove the workspace's memory. Everyone else keeps personal notes. See memory and conversations.
• cherry no longer runs SQL of its own when the sql switch is off under Settings · cherry, even when a model asks to.