Files

Manage admin-level files, uploads, storage visibility, and shared media records.

This page explains how Files works inside FlowCRM AI, when to use it, how teams should operate it, and what administrators should check before enabling it for real workspaces or paid plans.

Main Capabilities

Review uploaded files, storage usage, file actions, and file manager settings.
Use files for support, admin content, or shared platform assets.
Keep private storage and customer-facing shared files separated.

When to Use This Feature

Use it when the workflow needs a structured record instead of scattered messages.
Use it when multiple team members or clients need visibility into the same work.
Use it when plan limits, addon access, or audit history must be enforced.

Practical Examples

Use this page while setting up a demo workspace so buyers understand the feature with real client data.
Create one sample record, connect it to a client and project, then test what internal users and client portal users can see.
Review the related report, activity, permission, and export behavior before presenting the feature to customers.

Recommended Workflow

Upload or select the files that belong to the client or project.
Create a deliverable record with version, owner, client, project, and delivery status.
Attach files, notes, approval links, or report references before sharing.
Send or publish the delivery package through the approved client workflow.
Review delivery events, downloads, and client feedback after handoff.

Important Fields and Records

File name, type, storage path, owner, project, client, version, and visibility.
Deliverable title, package status, approval status, delivery date, and client access.
Download, view, or activity events used for delivery tracking.

Best Practices

Keep names and descriptions clear enough for another team member to understand without extra context.
Attach records to the correct workspace, client, and project so reports and permissions stay accurate.
Use statuses consistently; avoid using notes or comments as a replacement for workflow status.
Review client-facing content before sharing it through a portal, report, approval, or delivery flow.
Clear application cache after module, permission, route, or pricing changes.

Plan Access and Permissions

Use this feature with the correct workspace, role permissions, plan limits, and installed modules. Some functionality can be enabled by plan, sold as an addon, or hidden when the related module is not installed. Administrators should review plan permissions before making the feature visible to customers.

Confirm the current user role can view, create, update, and delete related records.
Confirm the workspace plan includes the required feature key or addon permission.
Confirm related buttons, menus, and pricing rows are hidden when the module is not installed.
Confirm customer-facing records only expose the intended workspace, client, or project data.

Troubleshooting

The page or button does not appear
Confirm the related module is installed, routes are loaded, and the current plan includes the required permission. Also clear route, config, and view cache after module changes.

The record saves but does not show in reports
Confirm it is attached to the correct workspace, client, project, status, and date range used by the report.

A client or team member cannot access the item
Review role permissions, workspace membership, portal settings, and plan limits. Access is usually blocked by scope, role, or missing addon permission.

Old information is still visible
Clear application cache and refresh the browser. If the page is public-facing, confirm the public documentation or portal cache has been refreshed.

FAQ

Can this feature be sold as part of a paid plan?
Yes, if the related permission or addon key is connected to plans. Review your license type before selling customer access.

Can customers see this data?
Only when portal routes, workspace permissions, and visibility settings allow it. Internal records should remain hidden from client users.

What happens if the related addon is removed?
Menus, buttons, pricing fields, and routes should be hidden when the module is not installed. Keep a database backup before removing addon tables.