Skip to main content

Two perspectives: Resources and the customer dashboard

Locations, connectors, and access policies each appear in two places in the console. Same resources, two lenses:

  • Resources (provider-wide). The main navigation's Resources section lists every resource across the whole provider — provider-owned infrastructure plus every customer's. This is where you manage the shared pool and author things that span customers.
  • The customer dashboard (one customer). Open Customers and pick one, and the dashboard shows only that customer's resources, alongside its monitoring (summary, recent alerts, live audit) and the operators and members scoped to it. A Customer Admin — provider staff assigned to that account — only ever sees this scoped view; a Provider Admin can also use View as customer to preview it.

Where each resource lives

ResourceProvider-wide (Resources)Per customer (dashboard)
LocationsEvery locationThe customer's locations
ConnectorsEvery connectorThe customer's connectors
Access policiesEvery policyThe customer's policies
Custom variablesProvider scopeCustomer (and per-location) scope
Operators, membersProvider-wideThose scoped to that customer

Some things live in only one perspective:

  • Connector models and templates (customer and location) are authored once at the provider level and reused across customers — they aren't a per-customer view.
  • Customers, branding, and provider-wide operator administration are provider-level tasks.

Which one should I use?

  • Reach for Resources when you're working across customers — auditing every connector, or building an access policy that links provider infrastructure to a customer.
  • Reach for the customer dashboard when you're focused on a single customer — checking their alerts, pausing a location, or reviewing who has access.

The how-to guides describe each resource itself and note both places you can act on it. For the underlying provider/customer model, see Key concepts.

Related: Dashboard · Live Audit