Turn a Module Off for Staff — Don't Just Hide the Owner Tab
Hiding the Owner Tab Is Not the Same as Turning Training Off
A training director tells the front desk that board-and-train is paused until spring. Someone opens Facilities Client Portal, flips Offered to clients off for training at every location, and posts a note in the staff channel: "Training is off in the app."
Monday morning a kennel tech still opens Training from the sidebar, starts an enrollment for a walk-in, and quotes a four-week program. The owner never saw a portal button. The problem is not a software bug. The desk used the owner-only switch when the goal was to get training out of staff menus for a few months.
Pet care software stacks several independent visibility layers. Mixing them up creates enrollments nobody meant to sell, or quiet portals while the floor stays busy.
Three Layers Operators Actually Need
Billing and entitlement answer whether the organization pays for a module. That unlocks admin routes, historical data, and the right to turn work back on without a new purchase.
Organization → Modules (under Facilities, labeled "Modules and staff tools") is the self-serve switch for what your team sees. For a client service such as boarding or training, turning the module off hides it from staff menus and from the owner portal org-wide. Data stays in place. The bill does not change. You can turn it back on when the program returns.
Client Portal → Offered to clients is per location. It only applies while the module is on in Organization → Modules. It hides a service from owners at one site while trainers and desk staff at that building keep full admin access.
You need all three names on the same runbook. "We turned training off" should mean which layer moved.
What Organization → Modules Changes on the Floor
When a covered client module is off in Organization → Modules, sidebar links for that service disappear for staff, including module admin entries. Quick actions that launch boarding or training workflows drop off the header. Setup Center stops nagging about configuration for a product you are not running this quarter.
Owners lose portal paths too, because the org-level off switch is not a staff-only mute. That is why you should not use it when you only want to stop self-serve booking while trainers keep enrolling in-house dogs.
Staff tools on the same page behave differently. Messaging, supplies, and operations stations are not client-bookable. Turning one off removes it from staff menus only. Owners were never in those flows. The copy on the page states that plainly so you do not hunt for a portal toggle that does not exist.
Some staff tools have nuance worth reading before you flip a switch. Hiding Operations Stations removes the station launcher from the menu; Front Door stays available, and tablets already logged in keep working. Hiding Messaging removes the inbox and compose button while thread history remains.
When Client Portal Is the Right Tool
Use Offered to clients when internal work should continue but owners should not book or browse that service yet.
Picture Harbor Kennel running a trainer-led pilot on two board-and-train dogs while marketing is still rewriting the portal card. Training stays on in Organization → Modules so enrollments, session notes, and timelines work. At the main location, Offered to clients stays off until pricing, capacity, and the enrollment call script match what the button will promise. Harbor's annex, which boards only, keeps training off on the portal matrix so annex clients never see a service that building does not deliver.
That is the soft launch pattern in Having a Module and Offering It to Clients Are Different Switches, seen from the owner side. This post is the mirror image for staff: if Harbor had also turned training off in Organization → Modules, trainers would have lost admin on day one of the pilot.
The Failure Mode This Post Is About
Teams hide the owner tab and assume the module is off for everyone.
Symptoms show up fast. Float staff click Training because it is still in the nav. A manager duplicates last season's program template and quotes dates before leadership reopens sales. Reporting mixes paused-program noise with active boarding revenue because nobody agreed whether "off" meant portal-only or org-wide.
The fix is to name the intent before touching a toggle.
| Goal | Organization → Modules | Offered to clients (per location) |
|---|---|---|
| Pause all training work and hide it from staff | Off | N/A while module is off |
| Train in-house; owners must not self-serve yet | On | Off where needed |
| Sell training online at one building only | On | On at that location only |
If your runbook row does not match the table, someone will use the wrong screen and the floor will follow.
Seasonal Pauses, Pilots, and "We Are Not Ready"
Boarding-heavy facilities often keep training entitled year-round for reporting and alumni dogs but want zero new training revenue in January. Organization → Modules off is the honest setting: nobody sees a product you are not staffing.
A multi-site group may keep training on org-wide for the flagship while an annex stays boarding-only on the portal. That is Organization → Modules on plus per-location Offered to clients, not an org-wide off switch.
During software evaluation, ask vendors to demonstrate both controls in one session. If "disable training" only removes an owner tab while staff menus stay crowded, you will recreate Harbor's Monday enrollment on whatever you buy next. A compare demo script should include: module off in admin, then module on with portal offered off at one location, then both on at a single site.
Switching Software Without Losing the Distinction
Migration week is when teams collapse layers again. Importers turn entitlements on so staff can work. Marketing publishes the portal link. Someone disables training in the new admin thinking that only affects owners, then wonders why trainers cannot open enrollments.
Document three columns per location before cutover: entitled (billing), offered to staff (Organization → Modules), offered to clients (portal matrix). Pair that sheet with your kennel software alternative checklist so the first login on the floor matches what leadership announced.
Hiding a module in the old system is not always the same operation in the new one. Map old "inactive" flags to the closest Pet Ops layer instead of assuming one checkbox does everything.
How This Connects to Daily Operations
Module toggles are operational discipline, not billing theater. The features overview is the right place to explain pay-for-what-you-use modules; Facilities Modules and staff tools is where you enforce what runs this month.
Training that shares pets with boarding still needs structured enrollments and owner-visible progress when you turn it back on. That work belongs in board-and-train software workflows, not in a boarding reservation with a longer end date.
Before the next seasonal pause, decide whether staff should see the product at all. If not, use Organization → Modules. If staff should keep working while owners wait, leave the module on and use Offered to clients per location. Either way, write the choice down so "training is off" means the same thing at the desk, on the floor, and in the owner app.