How do you give local managers visibility while keeping regional teams in control?

Slate gives each authorized client contact a property view based on their role and assignments. That means a local manager can see the locations relevant to day-to-day oversight, while a regional team can review its managed territory without making every person a client-wide administrator. The same scope is applied to portfolio information and portal reporting, so visibility follows responsibility rather than a shared password or an informal spreadsheet.

Build access around the operating structure

The client portal resolves a contact’s scope before returning properties. A main contact or facilities manager has client-wide visibility. A location manager can see directly assigned properties. An area manager can see properties in the areas managed by that contact. A regional manager can see properties in regions associated with that role, including regions represented through the current regional assignment structure and the supported legacy relationship. If a contact has more than one applicable scoped role, the permitted properties are the union of those role-based sets.

Open Properties to work from the resulting portfolio. Search, active or inactive status, region, and area filters help a regional team review its territory. Group by region makes the hierarchy visible, while a local contact can focus on the smaller “My Property” set shown for their scope. Property cards can include next visits and client-visible open issue counts, allowing each manager to prioritize the locations they are actually responsible for.

This is also the scope used when a contact opens a property detail or reviews portal metrics. A regional manager can filter service measures across the permitted regional portfolio; a local manager can investigate the visits and issues available for assigned sites. The result is a consistent boundary: the person is not shown a broad portfolio in one screen and then accidentally exposed to another location through a detail or reporting endpoint.

Keep regional control without hiding useful context

Role-scoped visibility separates local awareness from centralized operating control. Local managers can know what is scheduled next and which client-visible issues are open at their locations. Regional teams can compare and prioritize across their managed properties. The main or facilities contact can retain the broadest client view for account-level reviews. Slate’s operations team remains responsible for running the cleaning operation; the portal view does not grant a client contact authority to dispatch cleaners, change internal assignments, or bypass Slate’s controls.

Access is not inferred from a person’s title in an email. It depends on configured contact roles, property assignments, area ownership, regional relationships, and the client account. A billing_contact role by itself is a billing authorization and does not automatically make someone a property-wide operations viewer. A contact with no applicable property scope should receive an empty property view, not another manager’s locations. Removing or changing an assignment changes the data that contact can see on subsequent requests.

What managers should expect

Two contacts at one client may legitimately see different property counts, upcoming visits, issue totals, and metric results. That is a privacy and governance feature, not a data discrepancy to solve by giving everyone all-property access. Before rollout, confirm who needs client-wide visibility, which properties belong to each location manager, how areas roll up to regions, and who should hold billing access separately.

The view remains a record of scheduled and reported information. A next visit is not proof of attendance, and an open issue count includes only issues exposed to the client portal. Role configuration can change what appears, so access reviews should be part of your operating process.

Review your access model

Ask Slate to map your regional, area, and local responsibilities to portal roles and demonstrate a portfolio review for each contact type before access is issued.

Review role-scoped location access