Read Workspace Activity as a bounded operational record
Evidence first
Clear ownership
Verified next step
Activity joins recorded work from several product areas
The page normalizes supported operations from Action Center, Domain and Competitive Research, Keyword Research and Database, Position Tracking, Site Audit, Search Performance, Research, Content, Brain, and a small Other category. Every row belongs to the active workspace.
Coverage is broader than a single event table. It combines purpose-built operation records and source-specific run documents. It is still not an exhaustive audit log of every click, edit, API call, or background task in Crawl Foundry.
Start wide, then move to the owning product
The analysis window and calendar use different horizons
The dashboard aggregates either 30 or 90 days in the browser's named time zone. The activity calendar requests a separate trailing 365-day day index so it does not delay the main dashboard. Days outside the active analysis window are unmeasured for the current dashboard, not zero activity.
While daily rollups are still backfilling, the calendar uses bounded live source reads. A capped year is a sample and is labelled accordingly.
Structured filters and search do not have the same scope
Category, status, initiator, cost, and selected calendar day are sent to the server. Summary, chart, categories, attention, contributors, and timeline then describe the same structured subset.
Free-text search runs only over the returned timeline rows because localized titles exist in the client. It searches title, scope, category, and support code, but it does not recalculate the aggregates above it.
Read the Coverage panel before making absence claims
Each source reports complete, capped, or viewer-scoped coverage and the number of rows read. Viewer-scoped Action Center work contains only the current user's saved work items. Source budgets and the 100-row timeline cap can make the whole dashboard a bounded sample.
No row can mean no supported operation in the chosen window, a structured filter, a source cap, a viewer-specific boundary, or a product action that does not project into Activity. It does not prove that nothing happened.
Costs appear only with organization billing access
A viewer without organization billing permission receives no cost values, cost filters, spend calendar, contributor ranking, or money columns. This is an authorization boundary, not zero spend.
When the usage-ledger read reaches its limit, spend is explicitly a lower bound. Contributor totals group returned settled charges by initiating user and can also be limited by the source and profile read caps.
Charts show rhythm, not causality
The daily chart combines operation counts with cumulative settled spend when visible. The atlas groups activity by product category and calendar week. The twelve-month calendar can switch between fixed operation buckets and spend intensity relative to the busiest day.
These views show when recorded work concentrated. They do not establish that one operation caused a ranking, traffic, revenue, or cost outcome elsewhere.
Activity is a read model, not job control
The page cannot cancel, retry, resume, reschedule, change scope, or repair a source run. A destination link is shown only when the route can be mapped safely. Use the owning product for current state and controls.