App activity

App activity shows who is using Runnit and which parts of the app they use. It also shows business actions and API results, so administrators can investigate errors alongside recent work.

You need an owner or admin role. Runnit-managed environments have collection enabled for their tenants. If your installation has collection disabled, the page says so and no new activity is collected.

After an app update enables tracking, refresh any existing tabs to start reporting activity. New tenants on an enabled environment are included automatically, with the same tenant permissions.

Inspect activity

1. Open Organisation > App activity in the sidebar.
2. Choose a Member and Time range, or leave all members selected.
3. Review People for active and recently seen members.
4. Select an entry under Recent activity to see its tenant, user and event IDs. API entries include the response status, such as HTTP 200 or HTTP 503.
5. Keep Refresh every 15 seconds selected, or choose Refresh yourself.

Active means a visible tab recently reported interaction. An idle browser, API polling or a background job does not establish that a person is active. Closing a tab can take up to 90 seconds to be reflected. This is an activity indicator, not an attendance record.

The page shows up to 200 recent results. Narrow the filters if it reports that the result is limited. Owners and admins see their own tenant. Platform administrators can filter configured tenants and see which servers responded. An unavailable server makes the fleet snapshot incomplete.

Google Analytics

Where configured, Open Google Analytics opens the separate app property. Tenant names, tenant IDs and opaque user IDs support reporting there. Personal names, emails, customer content and form values are not included in Runnit’s Google event payloads. Google’s browser tag receives normal connection information when loaded.

In Google’s Realtime overview, select Current tenant name under Active users by User property to see the tenant breakdown. For reports and explorations, use Tenant name with Tenant ID so you can distinguish organisations with the same name. Activity in a client workspace uses its owning tenant’s name. Names appear for new activity and aren’t added to older records. Google may take 24 to 48 hours to make new dimensions available in reports. Long names are shortened to 36 characters in the current-tenant view and 100 characters in event reports. Names with accented letters or other non-ASCII characters may be shortened further to meet Google’s limits. Tenant IDs remain unchanged when a name changes.

Where configured, Google Analytics starts automatically without an extra prompt. You can turn it off in Profile Settings > Google Analytics. The change applies immediately across open tabs in that browser. Existing opt-outs remain off. Browser privacy signals keep Google Analytics off. Operational activity remains available to authorised Runnit administrators. Enabling your environment does not change your Google preference. If Runnit shows activity but Google does not, check that Google Analytics is enabled in the browser you are using and that a browser privacy setting is not blocking it.

Google Analytics delivery shows pending, sent, skipped and failed events. Sent means Google accepted the request; reports may appear later. Failures show the available HTTP code or connection error. Activity remains in Runnit when Google is unavailable. Skipped events can include opted-out members, support sessions and activity without an associated browser session.

Continue with Profile settings or the App activity API.