Client Accounts

A client is a company you report to inside DashCore — a property owner, a management company, a university department, a municipal agency. You run the parking; they own the asset and want to see how it's performing.

Giving a client a login is how you stop sending monthly PDFs. They sign in to DashCore, see their own numbers, and see nothing else.

This section explains what a client account is, how to set one up, what a client can and cannot see once they're in, and how to check it yourself before you hand over the credentials.

The model in one picture

DashCore nests data in three levels:

Organization  (Acme Parking — you)

   └── Client  (Meridian Property Group)

          └── Location  (Keystone Lot)

                 └── Spaces, transactions, parkers, pages

• Organization is your operating company. Everything you manage lives under it.

• Client is a grouping of locations that belong to one customer of yours.

• Location is a garage or lot. A location belongs to exactly one client.

A client account is a scoped window onto that tree. When a client user signs in, DashCore filters every screen to the locations under their client — dashboards, parker records, exports, landing page stats, all of it. There is no toggle for them to widen it.

What a client can never see

This is the question every operator asks first, so it's worth stating plainly. A client user cannot see:

• Other clients. Not their names, not their revenue, not their locations. The Client filter that org users see is removed from the client view entirely, so there is nothing to widen to.

• Organization-wide totals. Their Home screen shows their revenue, not yours.

• Your admin surfaces. Settings, Users, Clients, Marketing, and Super Admin are all absent from their sidebar.

• Raw operational tables. Accounts, Transactions, Subscription Events, Vehicles, and Forms are org-only.

In this section

Related

• Disclaimers — how to put a notice on a client's dashboards when data is provisional or under review.