Skip to content
Control access

Read an Activity Feed

Trace denials, credential issuance, and policy decisions for a Resource, Provider, Application, or User from that entity's Activity feed.

Every credential issued, policy decision, Provider check, and configuration change is recorded as an activity. The Activity feed on an entity’s page shows only the activities that touched that entity, in order. Credential issuance, sign-in and authorization checks, and configuration changes are also kept Zone-wide in the Audit Log, and credential issuance per agent run in Sessions. Policy evaluations (policies:evaluate), Provider validations (providers:validate), and grant events (delegated-grants:*) show only here today. If an agent was denied a credential, the feed is the fastest place to see it, and the troubleshooting tips below cover when to switch to the other two views.

  • Sign in to the Keycard Console with the organization Admin Role. Activity needs the events:list permission, which Viewers and custom Zone roles don’t have.
  • The entity the activity touched: Activity is a tab on the detail page for a Resource, Provider, Application, or User; Policies → Activity covers policy decisions for the whole Zone.

Say an agent asked for a credential for a billing API Resource and a policy turned it down. To find out what happened:

  1. Open the entity’s Activity feed

    Go to the Resource’s detail page and select the Activity tab. Each row is one activity. For policy activities, open Policies, then select Activity.

  2. Scan the row

    • Outcome shows a red denied indicator. An issued credential would show green allowed, configuration and service activities get a neutral marker, and an inconclusive activity shows a warning.
    • Action names the activity, here Credential issued, with a status message explaining that the request was denied.
    • Actor is who performed it. Here it is the agent, but it can also be a User or Keycard itself.
  3. Open the detail panel

    Select the row and read the panel:

    • Overview carries the Event ID, the Request ID, when it occurred, and severity.
    • Reason says why the request was denied, in this case naming the deciding policy.
    • Actor identifies who performed the action. In this example, Resource identifies the billing API.
    • The middle of the panel depends on the activity type. A successful credential issuance shows the grant and scopes, a Provider validation lists each configuration check, and a policy evaluation shows the decision breakdown.
    • Raw OCSF is the full machine-readable record, in the same OCSF shape used for export.
  4. Narrow the feed

    Select Filters to add Outcome, Actor, App, Session, Resource, Policy, Policy set, or Request filters. Use the range picker to change the time period; it defaults to Last 7 days. Set Outcome to Failure to see every denial on this entity at once.

Copy the Request ID from Overview and search for it in the Audit Log to find related audit events from the same request.

  • An activity you expect isn’t in the feed: feeds only surface the actions in the Activity Events registry. Deletions, archivals, and lower-level operations land in the Audit Log and in Audit Log Export.
  • To search across the Zone or filter by action or category, open the Audit Log. Open Sessions to follow one session’s events in order.
  • The same activity shows on two feeds: expected. An activity appears on the feed of each entity it touched, so credentials:issue shows on both the Resource and the Provider it involves.