Skip to main content

AI activity and usage

RushHour keeps a record of what the AI assistant does, so administrators and users can see who asked for what, which tools the assistant used, and which actions were confirmed.

Reviewing AI activity​

Go to Settings → Activity Logs and open the AI Activity tab. The All tab also mixes AI events in with user and system activity.

Each row shows the Time, User, Event, Tool, Target, Status, whether an action was Confirmed, how long it took, and the Chat it belongs to.

Events you will see include:

EventMeaning
User message / Assistant replyA message in a conversation.
Tool callThe assistant looked something up or ran something for you.
UI action executedThe assistant opened a page, set a filter or changed a setting on your screen.
Action staged / Action confirmed / Action rejected / Action expired / Action apply failedThe life of an action card.
Import preview issued / Import committed / Import failedThe life of an import.
Conversation deletedA user deleted a conversation.
Turn failedThe assistant could not finish answering.

Statuses include Succeeded, Failed, Awaiting confirmation and Interrupted.

Filtering​

Narrow the list with From and To dates, Search (tool, user or detail text), Tool, Event types, and Mutations only to see just the events that changed data.

Opening the trail of one conversation​

  • In the assistant panel, click View audit trail at the top of a conversation, or next to a conversation in Chat history. The AI Activity tab opens filtered to that chat, showing Showing chat #… only.
  • From the AI Activity tab, use Open this conversation in the chat panel to jump back into the chat.

Who can see AI activity​

PermissionShows
Activity log - view own AI activityYour own AI activity.
Activity log - view all users AI activityAI activity of everyone in your company.

AI usage​

Go to Settings → AI Usage to see how much AI your company used. The page is only listed for users with the AI usage - view usage permission.

  1. Choose a Month.
  2. Read the totals: Calls, Tokens in / out, an estimated cost in USD, and the Success rate.
  3. Use Group by to break the month down by Feature, User, Model or Day.

Usage covers all AI features, including the assistant, voice transcription, document reading and AI help when writing emails. Calls made with your own AI provider key are marked own key.

Using your own AI provider​

Under Settings → Integrations, the AI Provider (Bring Your Own Key) card lets a company run RushHour AI on its own OpenAI, Anthropic, Grok or Gemini account. This option is marked Enterprise and must be enabled for your company by RushHour — if it is not, the card tells you to contact us.

When it is enabled, a company administrator can open the card and, for each provider:

  1. Enter the API key (and optionally a Base URL and Model).
  2. Click Test to check the connection.
  3. Choose which connection powers RushHour AI for your company, or None — use RushHour AI.

Stored keys are never shown again; only their last 4 characters are displayed. Allow fallback to RushHour AI (off by default) retries a failed request once on RushHour's own AI, with a notice in the chat. Document search always runs on RushHour's infrastructure; your provider key is used for chat and assistant features.