Docs / FlowCRM AI

Changelogs

Review version history, release notes, update instructions, database changes, addon updates, and compatibility notes.

Estimated reading: 5 minutes

Changelogs

The Changelogs page helps buyers and administrators understand what changed between FlowCRM AI releases. Read this page before every production update so you know which files, database tables, modules, permissions, routes, and customer workflows may be affected.

🚀 Version 1.0.0 - Initial Release

✨ Added

  • Initial FlowCRM AI release for agency workspace management, client operations, projects, tasks, approvals, deliverables, reports, and client portal workflows.
  • Workspace dashboard for monitoring clients, projects, reviews, approvals, delivery activity, reports, files, and operational signals.
  • Client management system with companies, stakeholders, client portals, and structured client requests.
  • Project workspace with workspaces, delivery timeline, tasks, deliverables, activity tracking, and project-level collaboration.
  • Review and approval workflows for internal QA, client feedback, review queue management, formal approvals, rejection reasons, and signoff history.
  • Asset management with asset library, shared files, reusable templates, project resources, and client-facing file visibility.
  • Reports module with client reports, AI reports support, exports, delivery metrics, and workspace performance summaries.
  • Operations workspace with operations dashboard, delivery activity, activity feed, communication hub, and automation-ready workflows.
  • Team management with team members, roles, permissions, workspace access, and SaaS-ready account controls.
  • Settings area for subscription, billing, workspace settings, plan limits, payment access, branding, and production configuration.
  • Client Portal for customers to view overview, delivery timeline, deliverables, approvals, review queue, shared files, reports, exports, and new requests.
  • Admin Workspace documentation and structure for Admin Dashboard, AI Center, User Portal, Main Content and Operations, Finance, Settings, and Localization.
  • Marketplace-ready addon architecture for AppAIReports, AppAIWriter, AppAutomations, and future FlowCRM AI modules.
  • Plan-based addon permissions, pricing visibility, sidebar visibility, and module-safe install/uninstall behavior.

âš¡ Improved

  • Documentation structure aligned with the real FlowCRM AI user sidebar, client portal sidebar, and admin sidebar.
  • Detailed buyer documentation for installation, upgrade workflow, marketplace package management, extended license usage, and changelogs.
  • Expanded documentation depth for every core section so buyers can understand setup, workflows, permissions, best practices, troubleshooting, and FAQs.
  • Admin sidebar documentation now follows the live FlowCRM AI admin registry, including nested items for AI, users, finance, settings, support, blogs, and localization.
  • Client portal documentation now explains customer-facing review, approval, delivery, report, export, and request workflows.
  • Addon handling improved so related menus, pricing fields, plan permissions, and buttons remain hidden when optional modules are not installed.

🛠 Fixed

  • Fixed optional addon visibility behavior for demo mode and marketplace package records.
  • Fixed sidebar addon badge behavior so badges appear only when demo mode is enabled and the module exists in marketplace packages.
  • Fixed plan and pricing permission visibility for optional AI Reports, AI Writer, and Automations modules.
  • Fixed detachable module behavior so removing optional modules does not break core routes, sidebar buttons, pricing screens, or plan setup.
  • Fixed documentation content that was too generic by adding detailed workflows, examples, fields, troubleshooting, and FAQs.
  • Fixed FlowCRM AI documentation sidebar structure to include core workspace, client portal, admin workspace, installation, upgrade, marketplace, extended license, and changelog pages.

What Changelogs Are Used For

  • Review new features added to FlowCRM AI.
  • Review bug fixes and behavior changes.
  • Check security improvements and recommended upgrade urgency.
  • Check database migrations and table changes before updating production.
  • Review addon compatibility for AI Reports, AI Writer, Automations, and future marketplace modules.
  • Identify changes that may affect client portal, admin workspace, billing, reports, files, or permissions.

Recommended Release Note Format

Each release should be written in a consistent format so buyers can quickly decide whether they need to update immediately and what they should test after updating.

  • Version: release number, for example 1.0.1.
  • Release date: date the update was published.
  • Type: major, minor, patch, security, or addon update.
  • Summary: short explanation of the release.
  • New features: features added in this version.
  • Improvements: UX, performance, workflow, or admin improvements.
  • Bug fixes: issues resolved in this version.
  • Database changes: migrations, new tables, changed columns, or seed updates.
  • Breaking changes: changes that may affect custom edits or integrations.
  • Post-update checks: workflows buyers should test after upgrade.

Example Changelog Entry

Version 1.0.1 - Patch Update

  • Summary: improves dashboard visibility, client portal review flow, and admin documentation.
  • New: added expanded documentation for Client Portal and Admin Workspace.
  • Improved: refined reports, operations, and company management guidance.
  • Fixed: corrected addon sidebar visibility when modules are removed.
  • Database: includes migration updates for optional addon modules where applicable.
  • Post-update: clear cache, run migrations, then test dashboard, client portal, reports, approvals, and admin marketplace.

How Buyers Should Read Changelogs

  1. Check whether the update is for the main product or an addon module.
  2. Read the summary to understand the release purpose.
  3. Review database changes before running migrations.
  4. Review breaking changes before replacing files on a customized installation.
  5. Back up the database, application files, .env, and storage folder.
  6. Update the main FlowCRM AI product before addon packages.
  7. Run migrations and clear application cache.
  8. Test the workflows listed in the post-update checklist.

Update Testing Checklist

  • Admin login and dashboard load correctly.
  • User portal and workspace dashboard load correctly.
  • Client portal pages open for client users.
  • Clients, companies, stakeholders, and requests can be created or updated.
  • Projects, tasks, deliverables, reviews, and approvals still work.
  • Reports, AI reports, exports, and delivery activity load correctly.
  • Files upload and download correctly.
  • Plans, billing, subscriptions, and payment history remain accurate.
  • Marketplace packages show the correct installed version.
  • Optional addons are hidden when removed and visible when installed.

Addon Changelog Notes

Optional modules should have their own changelog notes when they change independently from the main product. This is especially important for marketplace packages that can be installed, updated, disabled, or removed separately.

  • AppAIReports: document changes to AI reports, workspace insights, delivery metrics, and report tables.
  • AppAIWriter: document changes to AI writing, client replies, task generation, and content tools.
  • AppAutomations: document changes to triggers, actions, reminders, approvals, scheduler behavior, and run logs.

Important Notes

  • Always back up before applying updates.
  • Do not skip database migrations unless the release note explicitly says no migration is required.
  • Do not update addon modules before the main product when the changelog says the addon depends on a newer core version.
  • Custom edits may be overwritten during updates.
  • After updating, clear cache and test the public site, admin workspace, user portal, and client portal.

Troubleshooting After an Update

A page returns 404 after update
Clear route cache and confirm the module provider is loaded.

A menu item is missing
Confirm the related module exists, the provider is registered, the plan permission is enabled, and cache has been cleared.

Database error appears
Run migrations and check whether the update contains required schema changes.

Old design or text still appears
Clear view cache, browser cache, and any public documentation cache.