Understanding Applications Activity KPI Cards

Six KPI cards summarize the event set selected by the current activity filters. Use them for orientation, then use the table and event-detail drawer to investigate individual events.

Before you start

• Open https://<workspace>.raptix.app/applications/logs.
• Allow the initial summary to load.
• Set an explicit date range when comparing periods or exporting a report.

The initial unfiltered display uses the server's default 30-day window.

Read the six cards

Application opens, form views, Permissions access, and Logs access contribute to Total Events but do not have dedicated KPI cards. Therefore, the action-specific card values are not expected to add up to Total Events.

Unique Users is a distinct count, not an event count, so it should not be added to the action cards.

Apply filters to KPIs

1. Select Show Filters.
2. Set a date range or another filter.
3. Wait for the cards to display updated values.
4. Review the table below to see the events behind the totals.

All six cards use the same applied search, date, actor, action, outcome, resource type, and resource name filters as the table. During a refresh, card values display an ellipsis.

Examples:

• Filtering Action to builder.open makes Builder Opened equal Total Events; the other action cards should be zero.
• Filtering Actor Email shows activity generated by that stored email only.
• Filtering Outcome limits all cards to events with that stored outcome.
• Sorting a table column does not change the cards because sorting changes order, not membership.

Interpret the cards carefully

• Use Total Events to understand overall recorded interaction volume, not business outcome volume.
• Use Unique Users as a directional adoption measure. Accounts without a recorded event in the selected scope are not counted.
• Use Pages Viewed and Edit Opens to compare consumption with builder editing activity.
• Use Builder Opened to identify periods that deserve a closer builder-access review.
• Use Workspaces Opened to understand top-level explorer navigation.

These KPIs summarize best-effort UI activity records. They are useful for operational review but should not be treated as a complete security audit or proof that an unrecorded action did not occur.

Compare periods

1. Apply an explicit From and To date.
2. Record the six values or export the underlying events.
3. Move to a non-overlapping comparison period of the same length.
4. Compare totals and unique users, then inspect table rows for context.

The page does not display period-over-period percentages and does not export the cards as a separate summary. Use Export to download the filtered event rows, up to 20,000, and calculate additional metrics outside RAPTIX.

Troubleshooting

The cards do not appear

The summary request may have failed. Reload the page and verify connectivity and Applications access. The table and summary load through separate requests, so one can fail while the other succeeds.

The cards show an ellipsis

The summary is refreshing. Wait for the current filter request to complete.

Total Events is larger than the visible page

The table shows 50 rows per page. KPI cards summarize the complete filtered result, not only the current page.

Total Events does not equal the action cards

This is expected when the result includes actions without dedicated cards, including Application Opened, form views, Permissions Accessed, or Logs Accessed.

Unique Users is lower than the number of licensed accounts

It counts only distinct actor emails with matching stored activity, not every account in the workspace.

Builder activity appears under a different name in older material

The current card and table label is Builder Opened, and its action key is builder.open.