Skip to content

Sessions and API usage

Two read-mostly pages under Administration › User Authentication give operators a cross-tenant view of portal activity: Users Web Sessions (who is signed in right now) and API Usage (request volumes against each tenant's limits). Customer administrators have the same pages scoped to their own organization — see Web sessions and API usage in the Administration Guide.

Users Web Sessions

Administration › User Authentication › Users Web Sessions lists every active session across all tenants. Columns: Tenant, User, Login, IP address, and Session Start Time, with a View action for session details. Narrow the list with the Select a Tenant drop-down or search by user, login, or IP address.

Typical operator uses:

  • security review — spot sign-ins from unexpected addresses, or accounts that should be disabled;
  • support — confirm whether a user is currently signed in, and from where;
  • integration hygiene — automation accounts that sign in per request instead of keeping a session show up as long runs of near-identical rows.

Select sessions and click Terminate to sign the users out immediately. Termination does not disable the account — pair it with a password reset or disabling web access on the user account when responding to a compromise.

API usage

Administration › User Authentication › API Usage shows request statistics per tenant: pick the tenant, and the page displays its API access limits and Web access limits, plus historical counters for the selected date range — API and web requests served and denied — with a per-day chart.

A denied request was rejected by the tenant's rate limits. Sustained denials usually mean a customer integration is polling too aggressively; either the integration slows down, or you raise the tenant's limits in its rate limits (the tenant page's View usage links land on this same data).

Access to the REST API is permission-controlled per role, and the API itself is documented in the REST API Developer Guide.