Companies

Create and manage client companies, organizations, brands, billing profiles, and account ownership.

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

Store company identity, workspace relationship, primary owner, status, and client context.
Connect companies to stakeholders, projects, reports, files, approvals, and client portal access.
Use company records to keep multi-brand or multi-location clients organized.

When to Use This Feature

Use it when one customer has multiple brands, departments, locations, or business units.
Use it when several stakeholders from the same organization need access to projects or approvals.
Use it when billing, reporting, files, and delivery history should be grouped under one company profile.

Practical Examples

A digital agency creates "NovaPeak Studio" as a company, then adds the marketing manager as reviewer, the founder as final approver, and the finance lead as billing contact.
A client with three brands can be stored under one parent company while projects, reports, and deliverables remain separated by brand or workspace.
A monthly retainer client can have one company profile connected to ongoing SEO reports, design deliverables, campaign approvals, and new service requests.

Recommended Workflow

Open Clients > Companies from the workspace sidebar.
Create the company record with legal or display name, brand name, owner, status, contact details, and notes.
Add stakeholders who belong to the company, such as decision makers, reviewers, billing contacts, and project owners.
Connect the company to active projects, deliverables, reports, requests, shared files, and client portal access.
Review the company profile before inviting client users so they only see the correct projects and shared records.

Important Fields and Records

Company name, display name, brand name, website, industry, status, owner, and workspace.
Primary contact, billing contact, stakeholders, portal users, and relationship notes.
Connected projects, requests, reports, approvals, deliverables, shared files, and activity timeline.
Billing profile, plan relationship, account ownership, and any internal tags used for segmentation.

Best Practices

Create one company record per real client organization, then attach stakeholders and projects under it.
Use consistent naming for companies and brands so search, reports, and exports stay readable.
Do not give portal access to a company until stakeholders and visible projects have been reviewed.
Keep billing contact and project contact separate when different people own payment and review decisions.
Archive inactive companies instead of deleting them when historical reports, files, or approvals still matter.

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

A company does not appear in project forms
Confirm the company belongs to the same workspace as the project and is active. Also check whether the current user role can view company records.

A stakeholder cannot access company portal content
Confirm the stakeholder has portal access, belongs to the correct company, and has permission for the specific project, report, file, or approval.

Reports are missing company data
Confirm projects, deliverables, requests, and reports are attached to the company or to clients under that company. Data outside the company relationship will not be grouped correctly.

Duplicate companies appear
Merge operational usage manually by moving stakeholders, projects, and reports to the correct company, then archive the duplicate to preserve history.

FAQ

Should I create a company or a stakeholder first?
Create the company first when the client is an organization, then add stakeholders under that company. For a solo client, the company can represent the client brand or business name.

Can one company have multiple projects?
Yes. A company can be connected to multiple projects, reports, deliverables, approvals, requests, and shared files. This is useful for agencies managing ongoing retainers or multiple campaigns.

Can clients see company records?
Only if portal access and visibility settings allow it. Internal company notes, billing details, and private activity should stay hidden from client portal users.