Use this page to find the right place for a decision or operational question.

​
Where to look

​
Approvals

An Approval gives or refuses permission for a proposed action. It is not the same as a Review, which judges whether an output is good enough. An approval can be pending, revision_requested, approved, rejected, or cancelled. The request should name the action, risk, requester, and relevant context. Deciding the same request again should not apply the action twice.

​
Budgets and cost

Budgets can limit an organization or Agent. Cost events can still be attributed to projects for reporting, but projects do not have their own budget limits. When a hard limit is reached, Rudder pauses the affected Agent or organization instead of allowing hidden additional spend. A failed or cancelled Run can still have cost. Missing provider usage is shown as unavailable rather than estimated as a false zero.

​
Activity

Activity is the change history for important actions: status changes, assignments, comments, review decisions, approval decisions, configuration changes, and similar mutations. Entries show who acted, what changed, when, and which organization record was affected. Use Activity to answer “who changed this?” It is not a replacement for the actual output or Run.

​
Agent Runs

Organization Run lists show a compact summary: Agent, task, status, result or error, usage and cost when available, Skill usage, and log availability. Open a Run for the full result, transcript, events, or raw logs. Readable summaries make scanning easier; they do not delete the lower-level details.

​
Dashboard, Calendar, and Messenger

  • Dashboard summarizes current movement, failures, cost, and items needing attention.
  • Calendar places scheduled and completed work on a timeline.
  • Messenger gathers questions, failed Runs, blockers, reviews, and approvals that need a human response.
All three point back to the original Chat, Issue, Run, Automation, or Approval.

​
Rules worth remembering

  • Review judges quality; Approval grants permission.
  • A budget limit must stop or pause spending where configured.
  • Activity records changes; Run details explain execution.
  • Summary screens never become a second copy of task state.

​
Organization boundary

Approvals, budgets, Activity, Runs, Dashboard, Calendar, and Messenger stay inside their organization. Credentials created in one organization cannot open records from another.

​
Examples

  • A release note is well written but publishing requires separate approval.
  • An Agent reaches its hard monthly limit and pauses before the next Run.
  • A reviewer wants to know who reassigned an Issue and checks Activity.
  • An operator sees a failed Automation in Messenger and opens its source Run.