Release notes: 3 November 2026

This update follows the 30 October release. Each item links to the page that explains how it works.

#Free plan

• Free is a working plan: the CRM for one user. A workspace lands on Free when its 14 day trial ends unpaid, its paid plan ends, a failed payment passes the 7 day grace period, or its subscription is in another state that is not paying. A Super Admin can also choose it with Switch to Free on the Free card in Settings → Plan and Billing.
• One person makes changes. The seat holder, the earliest created active Super Admin, keeps working in Leads, Contacts, Opportunities, Scheduling, and Events, and in Dashboard, Settings, Store, and Users and Roles. Everyone else can view but not change anything.
• Everything else stays visible and read only. Nothing is deleted. The API, MCP, AI agents, and automations make no change, and Free has no AI credits, App Builder, connectors, payroll, or marketing email. Booking pages and website lead forms keep writing into the CRM.
• Upgrading restores everything at once. A banner offers Upgrade. See The Free plan. The billing pages now describe a lapsed workspace as being on Free instead of read only. See Manage a subscription and paid add ons.

#Studio

• The top bar matches App Builder. It has Back to app, Studio home, and Projects. There is no New module button. Projects has one Create action, and it opens Studio, where New module is the first choice in the Module picker. See Studio: change modules and build your own.
• A workspace can delete a custom module it built. Choose Delete module from the project menu on Projects, or in the module's builder. The confirmation shows how many records go to the Trash, which scheduled automations pause, and any required relation that blocks the delete. The module's Studio chats and drafts are deleted too.
• Recently deleted restores a module. On the Projects page, Recently deleted brings a module back with the records that went to the Trash. Paused automations stay paused until you turn them on again in Automations. See Delete and restore a custom module.
• Field conditions. A field can be shown, required, or read only based on another field of the same record, with Show only when, Required when, and Read only when in the field's properties. The server enforces them on every create and edit. See Field conditions in Studio.

#App Builder

• The builder answers in plain words before it builds. The reply is a few short sentences about what it is making and how it will feel, with no colour codes, file names, or framework names. The design decisions go to DESIGN.md, the design record in the project that later edits read first. See What the builder tells you.

#Support

• The Support button is in the header, just before Notifications. One press opens the support chat. If the chat is not available yet, it opens a Talk to the Agaro team card. Support is no longer in the account menu and no floating chat bubble appears. See Get help with the Support button.

#Settings

• API and MCP puts AI assistants first. Connect an AI assistant (MCP) has the connector URL with a copy button, steps for Claude, ChatGPT, Cursor, and other apps, and a Connected apps list. No key is needed: you sign in with Agaro. API keys are the second block, for the REST API. Each person also sees their own connected apps under Account Settings. See Connect an AI assistant (MCP) and API overview and request format.

#Integrations

• Wix, Webflow, and Microsoft To Do are removed. Their tiles are gone from the Integrations page.
• NetSuite, Workday, and SAP SuccessFactors are data transfer tiles. They connect through Company connectors to move your data in, and Agaro never writes back. They are not live two way connections.
• A tile that needs a module says which. When the workspace has not added a module of an app's area, the tile names the module to add from the Store, such as Orders, Products, or Inventory for Square and Shippo, instead of blaming your permissions. See The Integrations page.

#Booking pages

• Clear messages when times cannot load. A booker reads that the host's calendar could not be checked, that too many requests came from their connection, or that times could not load, with Retry available times. The host gets a notification that names the calendar and how to fix it.
• No Support button on public pages. A booking page, its manage and return pages, and its embedded pages never load Agaro's Support.
• Choose the host's picture. The event editor and the create dialog have a Host picture control: use the host's own picture, or an image from the Image Bank. By default the page uses the host's employee photo, then their Users and Roles picture. The picture is a rounded square, like the platform's avatars.
• The page animates in when it opens. It plays once, and not at all for people who asked for reduced motion. See Event Types and public booking.