How To: Site Configuration

CM ships with the same broad, construction/remodeling-leaning schema for every tenant — Property lookups, Bid Requests, Warranty tracking, and dozens of other fields not every business needs. Site Configuration lets your own Administrator declutter your copy of CM down to just what your business actually uses, without touching anyone else's tenant or the underlying shared data.

The core idea

Hiding is cosmetic, never destructive. Every hide feature described here is a per-tenant overlay on top of shared data — it never deletes a row, never changes what other tenants see, and never touches the underlying schema. You can always change your mind and un-hide something later with zero data loss.

Administrator-only, site-wide — not per-Role. Every hide decision applies to your whole tenant at once, for every user in it. There's no "hide this for Role A but not Role B" option today — that's a deliberate simplification to keep this genuinely easy to use.

What you can hide today

Tabs on entity detail pages. Every record type with a tabbed detail view — Project, Company, Person, Asset, and the rest — can have individual tabs hidden site-wide. A landscaping company that never uses Warranty tracking can hide that tab everywhere it appears; a service business with no vendor-procurement workflow can hide Vendor Quotes & POs.

Where: Site Settings → Tab Order. The same screen already used to reorder tabs now also has a hide/show toggle per tab.

Specific values inside a shared reference list. CM's reference lookups (things like Property Roof Type, Dumpster size, Bid Type) are shared across every tenant by default. You can hide individual values you'll never use — a lacrosse club never needs "Metal Roof" or "Concrete Foundation" cluttering a dropdown that was really built for contractors.

This is only for the shared/core values every tenant starts with. Your own custom values are already fully yours to edit or delete directly — this feature exists specifically for the core values you can't otherwise touch.

Where: Site Settings → Reference Data (the same generic editor already used to browse any reference table) — a hide/show action now appears on core rows.

Once hidden, that value disappears from every dropdown across the whole app for your tenant — as if it never existed — while staying completely intact for every other tenant.

Not built yet — don't expect this

• Hiding side-menu categories (e.g. hiding the whole "Financials" or "Human Resource" section for a tenant that doesn't use it) is designed but not built yet.
• Per-Role hiding (different visibility for different Roles within the same tenant) was deliberately not built — today's design is intentionally simpler.

Who can grant & restrict what

Any Administrator of your tenant can hide or show an entity tab or a core reference value — it applies to the whole tenant, every user, immediately.

Worth knowing: hiding something is purely organizational — it doesn't revoke access to it. A user who knows a hidden page's direct URL can, in most cases, still reach it. This mirrors how most of CM's page-level access already works (visibility and permission are two separate concerns), not a gap unique to this feature.

Why this exists

CM's schema was originally shaped by construction/remodeling workflows. The real goal behind this feature is broader: making CM feel purpose-built for any business with clients — a lacrosse club, an art studio, a skating school — not just a contractor. A tenant that only ever sees reference values and tabs relevant to their own business reads as the app having understood them, not just as a settings toggle they configured.