Modules

The per-client switches that decide what a client is sold and what they can see.

A module is a per-client switch. It decides what an agency has agreed to do for one client, and — separately — what that client can see. Every agency has every module available; which modules a given client gets is the decision an agency makes one client at a time.

#Two switches, not one

Switch	Question	What turning it off does
Enabled	Does this client get this capability at all?	Stops the work. Scheduled paid jobs skip the client entirely.
Visible	Can the client see it in their portal?	Hides the section from them. The work carries on.

Visible only appears once Enabled is on — a module cannot be shown before it exists. The pair came apart when agencies wanted to track something without publishing it: rankings gathered weekly and discussed monthly, a service being prepared before it is announced.

Hiding never stops the work Anything that decides whether work happens — a scheduled rank check, a spend gate — asks whether the module is enabled. Anything rendering the client's own portal asks whether it is visible. Hiding a chart must never stop the tracking behind it.

#Where to set them

Step 4 of the onboarding wizard, for a new client.
The client's Settings tab, at any time afterwards.

#Core is different

Core is the only module a client has from the moment it exists, and it is the product itself — the dashboard, the team, the settings — rather than something an agency sells on top of it.

Everything else starts off. That is deliberate: switching every module on at creation would make the agreement a default rather than a decision, and the client's portal would advertise SEO and review monitoring on day one, before anyone had promised either. Turning a module on should be the act that says we do this for you.

#The catalogue

Module	Key	Catalogue description
Core	core	Dashboard, team management, and settings
Website Management	website	Change tickets and website approvals
Ticketing	ticketing	Support and change request tickets
Content	content	Blog, social, and campaign content approval workflow
Contracts	contracts	Contract templates, drafting, and legally binding e-signature
Reputation	reputation	Review monitoring across Google, Yelp, and Facebook
SEO	seo	Keyword rankings and organic performance
Website Health	sites	Security and maintenance telemetry from client websites
Social	social	Social media scheduling and publishing
Analytics	analytics	Traffic, leads, and conversion tracking
Lead Tracking	leads	Calls, forms, and appointment attribution
AI Assistant	ai	In-portal AI assistant for client accounts
Reporting	reporting	Automated monthly executive reports

Not every module in the catalogue is built The catalogue is the platform's full list, and some entries are placeholders for work that is not finished — Social, Analytics, Lead Tracking, AI Assistant and Reporting have no pages behind them yet. Enabling one gives a client nothing today. The modules with documentation in this library are the ones that do something.

#The modules with pages behind them

Module	Agency page	Client portal section
Core	Everywhere	Home, Brand assets, Your team
Ticketing	Tickets	Requests
Content	Content	Content
Contracts	Contracts	Agreements — also needs contract.view
Reputation	Reviews	Reviews
SEO	SEO	Search visibility
Website Health	Web Health	Nothing directly — findings reach the client as tickets, in Requests

Website Health decides whether a plugin is listened to at all Turning it off for a client does not merely hide a page — an installed plugin on that client's sites stops being processed. That is the one module switch with an effect outside this platform, so it is worth turning off deliberately rather than while tidying a menu.

Uptime is governed by permissions rather than by a module, and has no client-portal section of its own.

#What a client sees when a module is off

The sidebar entry is absent. Typing the URL gives a plain module not enabled page rather than an error — the section is not broken, it is not part of what they bought.

Their portal home carries a What's included card listing only the modules that are enabled and visible, named the way a client would name them. It is the client's own answer to what they are paying for.

#How account status interacts

Three conditions all have to hold before a module counts as enabled for a client:

The module is switched on for this client.
The client is one the agency is still working for — Active. A paused or offboarded client keeps every module switch exactly where it was, and stops being a reason to spend money.
The agency is one the platform is still working for. A past-due or suspended agency stops buying, because every billed call downstream lands on the platform's own invoice.

All three are checked in one place — the gate every paid path already passes through — because a spend gate is only worth having if it is the kind you cannot forget to call.