How do you give us one view of cleaning across all our locations?

Slate’s client portal gives authorized contacts a property portfolio instead of making them reconstruct service from separate emails. On Properties, you can search the portfolio, filter active or inactive sites, narrow by region or area, and switch to a list organized by region. Each property card can show the property count, open client-visible issue count, next visit date, and—when relevant—a My Property indicator for the scope assigned to your contact.

Organize the portfolio the way your team works

Start with the client portal’s Properties page. Search is useful when a facilities lead knows a site name or address; status filters help separate current locations from inactive ones. Region and area filters support the way multi-location cleaning programs are commonly managed: a regional leader can review one territory, while a local contact can focus on the area or properties in their assignment. Group by region provides a quick roll-up without losing the ability to open an individual property.

The portfolio is designed for operational triage. A next-visit date tells you what service is coming up, while an open-issue count highlights locations that may need attention. Select a property to open its detail view at /properties/:id and review the location’s service context, upcoming work, and available issue information. This turns “What is happening at our sites?” into a short review of the portfolio followed by a drilldown into the exceptions.

A useful weekly routine is to scan the regional groups, check sites with open issues, and then look ahead at the next visits for locations with a pending concern. A facilities team can use that view in a service review; a regional team can use it to prioritize a conversation with Slate’s operations team. The page also keeps location identity visible, reducing the risk of discussing the wrong building when several sites have similar names.

Keep the view honest and scoped

The portfolio is not an unrestricted database export. Slate resolves each contact’s property scope on the server before returning properties, visits, or client-visible issues. A main contact or facilities manager has client-wide property visibility. Other contacts see the properties allowed by their role and assignments. A location manager’s direct property assignments, an area manager’s managed areas, and a regional manager’s managed regions can contribute to the permitted set. If a contact has no property assignment, the correct result is an empty property view rather than another contact’s locations.

That permission model is useful for privacy and accountability: a local manager can work from the sites they are responsible for without automatically seeing every client location. It also means two contacts at the same client may see different counts, next visits, and issue summaries. The “one view” is one coherent view for the authorized portfolio, not a promise that every contact sees the same portfolio.

The page’s information is also operational rather than a guarantee of performance. A next visit reflects the schedule available to Slate, not proof that a cleaner will attend. An open issue count reflects issues visible to the client portal and may not include internal-only work. Region and area labels, issue visibility, and future visits depend on account configuration and current records.

Make every location reviewable

Ask Slate to map your property hierarchy and show how your team would move from regional roll-up to a location detail and an open issue, while preserving each contact’s authorized scope.

Review your client property portfolio