User Report

Review user growth, engagement, workspace activity, and account-level reporting.

This page explains how User Report 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

Use user reports to understand customer activity and product adoption.
Filter reports by date, plan, user state, and workspace signals.
Export or review user metrics before customer success follow-up.

When to Use This Feature

Use it for weekly, monthly, or campaign-end client reporting.
Use it when leadership needs delivery metrics, approval speed, task volume, or workspace performance.
Use it to turn operational data into a client-ready summary.

Practical Examples

A monthly client report summarizes completed tasks, open approvals, delivered assets, performance notes, and next steps.
An AI report draft can be generated first, then edited by the account manager before sharing with the client.
A leadership report can compare delivery volume, overdue work, and client activity across workspaces.

Recommended Workflow

Choose the workspace, client, project, and reporting period.
Review source data such as tasks, approvals, deliverables, files, and delivery events.
Generate or draft the report, then validate metrics before sharing.
Export or deliver the final report through the client-approved channel.
Use the report history to compare progress across future reporting periods.

Important Fields and Records

Workspace, owner, status, related client, related project, and visibility settings.
Created date, changed date, activity history, and plan or permission requirements.
Any connected records that affect reporting, automation, client access, or billing.

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.