Skip to main content

Console overview

The app-esper.com console is organized around one active tenant at a time. When you switch tenants, the app reloads the resources tied to that tenant:

  • API keys: Credentials for sending systems to authenticate ingest.
  • Actions: Tenant-defined semantic behaviors in your business language.
  • Entity definitions: Rules for how to identify and group traffic.
  • Mitigations: Reusable response behaviors for matched traffic.
  • Policies: Complete rules binding conditions, actions, entities, and mitigations.
  • Policy results: Performance metrics and outcome tracking for deployed policies.
  • Audit entries: Historical record of tenant changes with actor and timestamp.
  • Supporting operational history: Additional runtime data and system events.

How to read the console​

The easiest way to understand the product is to group pages by job:

  • Set up the workspace: Tenants and API Keys.
  • Build policy behavior: Actions, Entities, Mitigation, and Policies.
  • Inspect what happened: Results.
  • Explain or verify operations: Audit and replay tooling.

Overview​

The overview page summarizes tenant posture, deployed policies, and recent activity.

Use it when you want quick answers such as:

  • Is this tenant active?
  • Are policies deployed?
  • Is traffic arriving?
  • Are outcomes being recorded?

Policies section​

The Policies top-level area is a builder workflow with four sub-sections:

  • Actions
  • Entities
  • Mitigation
  • Policies

The intended order is deliberate.

Actions​

Define tenant-owned semantic events such as login or checkout_complete.

Entities​

Define how Esper should identify and group traffic for analysis and state.

Mitigation​

Define reusable responses such as monitor, challenge, or block.

Policies​

Compose traffic expressions, required actions, entity bindings, mitigation, and optional windows into the final deployed policy.

Results​

The results page is now policy-centered. It summarizes:

  • Decisions by policy: Total matching traffic for each deployed policy.
  • Mitigation breakdown by policy: Distribution of monitor, challenge, and block outcomes.
  • Most recent policy-attributed activity: Real-time view of recent policy matches.

This is where operators monitor the effectiveness of their configured mitigation.

Tenants​

The tenants page is the workspace control plane. It supports:

  • Create a tenant: Set up new workspace with name and unique slug.
  • Update a tenant: Modify tenant settings and configuration.
  • Switch the active tenant: Change which tenant context you're operating in.
  • Manage memberships: Add or remove team members with appropriate access.

API Keys​

The API key page issues ingest credentials tied to a tenant and source_id.

Use it when onboarding a new sending system.

Audit​

The audit page lists tenant-scoped audit entries with actor, action, and timestamp.

Use it to answer:

  • Who changed this?
  • When was it changed?
  • Which tenant was affected?