Hide a service without disconnecting it

The platform owner can hide any connected-service card from a tenant's Settings without changing whether it is connected or how it syncs.

What it is

Per-organisation visibility switches for the CRM, estimating, payment and accounting cards. Hiding removes the UI only; connection state, credentials and sync behaviour are untouched. The default for the CRM card is hidden, because the platform doctrine is CRM-free for new accounts.

Also called: don't show GHL · hide integration · too many options for my staff

See it
Hide a service without disconnecting it
Day rate
$600
Days figured
5
Crew size
5
Fuel & equipment
$300
Finished 2 days early — $1,600 back to the crew
Two side-by-side Integrations screenshots — one with the GoHighLevel card present, one without — same connection state. Sample data — no customer information appears here.
How it works
  1. 1Each service's status carries a hidden flag; the tab renders the card only when it is false.
  2. 2Migration 194 covers the CRM card and defaults it hidden; migration 195 covers the estimating, payment and accounting cards.
Why we built it

Migration 194 states the intent: 'Hiding NEVER changes connection state or sync behavior — it only removes the UI so tenant users can't accidentally disconnect or overwrite credentials they don't recognize. Reveal → configure → hide is the intended operator flow for GHL-backed installs.'

The problem
  • A tenant user could disconnect a service they did not recognise.
  • Every account saw cards for services it would never use.
Sound familiar?
What you get
A working integration cannot be broken by curiosity.
New accounts see only the services that apply to them.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →