Docs / FlowCRM AI
Signup

Extended License

Understand Regular and Extended License usage for paid workspaces, subscriptions, and addon sales.

Estimated reading: 7 minutes

Extended License - Main Features Overview

The Extended License explains when FlowCRM AI or a marketplace package can be used in a commercial product where end users pay to access the final service. This page helps buyers choose the right license before launching a SaaS, agency platform, client portal, subscription product, or paid project management service.

License rules can vary by marketplace and product. Always review the official license file and purchase terms included with your package. This documentation is a practical guide for common FlowCRM AI use cases, not legal advice.

Regular License vs Extended License

Regular License

A Regular License is generally suitable when the final product is used by one owner or one business and end users are not directly paying for access to the software-powered service.

Common Regular License examples:

  • A company installs FlowCRM AI for its own internal project delivery team.
  • An agency uses FlowCRM AI to manage its own clients, tasks, approvals, files, and reports internally.
  • A consultant uses one installation to organize client work without selling platform access.
  • A business uses dashboards, reports, project workspaces, and file delivery as part of internal operations.
  • An agency creates reports or deliverables for clients, but clients do not pay to access the software platform itself.

Extended License

An Extended License is generally required when you monetize the end product itself or charge users/customers for access to the software-powered service.

Common Extended License examples:

  • You sell FlowCRM AI as a SaaS where customers register and pay for plans.
  • You offer paid client portal access to agencies, teams, clients, or consultants.
  • You charge customers to use workspaces, projects, approvals, deliverables, reports, AI tools, automations, storage, or team access.
  • You bundle FlowCRM AI into a paid agency platform where customers log in and manage their own work.
  • You create a white-label project delivery or client portal service where customers pay for access to the platform.

How This Applies to FlowCRM AI

FlowCRM AI includes multiple monetizable areas: subscription plans, workspaces, clients, projects, tasks, approvals, deliverables, file storage, AI reports, AI writer, workflow automations, team seats, analytics, billing, support, and marketplace packages. If you enable these features for paying customers, review whether an Extended License is required.

Features That Often Indicate Extended Usage

  • Plans: customers buy monthly, yearly, or lifetime packages.
  • Workspaces: customers create and manage their own agency workspaces.
  • Clients and projects: customers manage their own clients, projects, tasks, approvals, and deliverables.
  • AI usage: customers pay for AI reports, AI writing, workspace insights, client replies, or task generation.
  • Automations: customers pay for triggers, reminders, approval workflows, scheduled rules, or process automation.
  • Team access: customers invite members into their own workspace.
  • Client portal access: clients log in to view reports, files, approvals, and delivery status.
  • File storage: customers pay for upload capacity, delivery packages, or storage limits.
  • Support access: support or premium support is tied to a paid package.

Marketplace Packages and License Type

The Marketplace can show product actions such as Add Regular and Add Extended. Choose the license type based on how the package will be used inside your final product.

When Regular Is Usually Enough

  • The package is used only for your own business operations.
  • The package does not power a paid customer-facing service.
  • Users are internal staff, not paying customers.
  • The package is not resold, sublicensed, or redistributed.

When Extended Should Be Chosen

  • The package adds features to a paid SaaS.
  • Customers pay to access the feature provided by the package.
  • The package is part of a commercial platform sold to end users.
  • The package is bundled into a paid white-label service.
  • The package directly supports paid subscriptions, AI usage, reports, automations, analytics, approvals, storage, or customer dashboards.

What You Can Do

A valid license allows you to install, configure, and use the product according to the purchased license terms.

  • Install FlowCRM AI on the licensed domain.
  • Configure plans, branding, payments, integrations, AI providers, and modules.
  • Create workspaces, clients, projects, tasks, approvals, deliverables, reports, and client portals.
  • Use purchased marketplace packages on the licensed installation.
  • Update the product and packages when updates are available for the licensed purchase.

What You Should Not Do

Even with an Extended License, there are important limits. The license usually does not allow unrestricted redistribution of source code or resale of the product as a standalone script.

  • Do not resell FlowCRM AI source code as your own product.
  • Do not redistribute the package files publicly.
  • Do not share purchase codes with other people or domains.
  • Do not install one license on multiple unrelated production domains unless the license explicitly allows it.
  • Do not sell the unmodified product as a downloadable script.
  • Do not bypass license verification or marketplace licensing checks.

Choosing the Right License

Use this decision guide before buying FlowCRM AI or any marketplace package.

Choose Regular License If

  • You are using FlowCRM AI for one company, one agency, or one internal team.
  • You do not charge customers to access the app.
  • Your clients only receive reports, files, or deliverables, but they do not pay to use the software platform.
  • You are managing internal agency operations for your own business.

Choose Extended License If

  • You run FlowCRM AI as a paid SaaS.
  • Your customers create their own workspaces, clients, projects, tasks, approvals, deliverables, or reports through your platform.
  • You charge for plans, AI usage, storage, automations, reports, team seats, client portals, or premium modules.
  • You provide customer accounts where users log in and manage their own agency workflows.
  • The package becomes part of a service that directly generates revenue from end users.

Client Work and Agency Usage

Agency usage depends on how the product is delivered.

Typical Agency Internal Use

If an agency uses one installation internally to manage clients, projects, tasks, files, reports, and approvals, and clients do not log in or pay to access the software, a Regular License may be enough depending on the exact license terms.

Client Portal or Paid Access

If clients can log in, manage projects, approve deliverables, view reports, download files, use AI, invite team members, or pay for access, treat it as a customer-facing commercial service and review Extended License requirements.

SaaS Launch Checklist

Before launching a paid FlowCRM AI service, confirm these items.

  • Purchase the correct license for the main FlowCRM AI product.
  • Purchase the correct license type for marketplace packages used in the paid service.
  • Install on the correct production domain.
  • Keep purchase codes private and stored securely.
  • Configure plans, payments, taxes, refund policy, and terms of service.
  • Set plan limits for workspaces, clients, projects, reports, AI tools, automations, teams, approvals, deliverables, and storage.
  • Test user registration, checkout, subscription changes, team access, AI usage, automation usage, and cancellation flows.
  • Review privacy policy and data processing requirements for client files, project data, AI prompts, analytics, and activity logs.
  • Back up database and files before launch.

Marketplace Purchase Flow

When buying packages from Marketplace, choose the license type before checkout.

  1. Open Admin > Marketplace.
  2. Find the product in Product catalog.
  3. Click Add Regular for internal/non-SaaS use, or Add Extended for paid customer-facing use.
  4. Open the cart and review the selected license type.
  5. Complete checkout from the connected storefront.
  6. Install the package from purchase code after purchase.

Common Mistakes

  • Buying Regular License, then launching a paid SaaS without upgrading license rights.
  • Using one purchase code across multiple production domains.
  • Installing marketplace packages with Regular License while selling the package feature to customers.
  • Letting clients access the admin/customer portal without reviewing license scope.
  • Forgetting to keep purchase codes private.
  • Assuming Extended License allows source-code redistribution.

FAQ

Do I need Extended License if clients only receive reports or files?
Usually no, if clients only receive exported reports or delivered files and are not paying to access the software service. If customers pay to create, manage, approve, or access those workflows through your platform, review Extended License requirements.

Do I need Extended License for subscriptions?
If customers pay for plans, platform access, AI tools, automations, reports, team workspaces, storage, approvals, or client portals, Extended License is usually the safer and more appropriate choice.

Can I use one license for many client domains?
Do not assume this is allowed. Check the official license terms. Marketplace license verification usually ties the purchase to an installed domain.

Can I upgrade from Regular to Extended later?
This depends on the marketplace purchase rules. If you plan to launch a paid customer-facing service soon, choose Extended License before launch to avoid license issues.