Workspace activity
Review recorded repository connection and access changes, then use scan, finding, and fix histories for their outcomes.
Understand what changedPermalink to Understand what changed
Use Activity to review recorded repository connection and access changes across the workspace. These include adding or disconnecting a repository, reconnect attempts, access synchronization, and repository-status changes. This is useful when a repository becomes unavailable to scan or a teammate needs the context behind an access change.
Activity is not a complete audit log
You need access to the workspace whose activity you want to review. Confirm the workspace before investigating a missing entry, and have the relevant repository name, approximate time, or action in mind. Reading activity does not grant permission to change the recorded resource.
Review the recorded sequencePermalink to Review the recorded sequence
Open Activity
Read the newest entries first. Each entry has a title and may include further detail, a repository, or the actor who made the change.
Check the timestamp
Activity times are labeled UTC. Use the time and repository together when investigating a connection or access change.
Load older entries
Choose Show more until you reach the period you need. An empty page with more activity available is not the end of the record.
Check the current repository state
Open Repositories to see current access and eligibility. A recorded reconnect attempt is not proof that access was restored.
Distinguish an action from its resultPermalink to Distinguish an action from its result
| Recorded action | What still needs checking |
|---|---|
| Repository added | Whether access is still valid and the repository is currently eligible to scan. |
| Access synced | Which repositories are currently accessible and whether their status changed. |
| Repository disconnected | Whether the repository needs to be reconnected before another scan can start. |
| Reconnect attempted or access restored | Whether access was actually restored. Read the detail and current state; an attempt can leave access unavailable. |
| Repository status changed | The stated reason and current status before planning the next scan. |
Read the event title and detail, not just its color. A successful connection change is not successful scanning. Review scan outcomes and triage decisions in their own workflows; the absence of an entry here does not establish that no other action occurred.
Handle missing or incomplete activityPermalink to Handle missing or incomplete activity
Nothing recorded yet describes the currently available workspace record, not a security assessment. If older entries fail to load, the entries already shown remain available; choose Retry loading more. When the feed says everything recorded is shown, there are no more entries available in that view.
If an expected action is missing, check the current workspace and the relevant resource's current state before repeating the action. For support, provide the repository, approximate UTC time, and visible message or scan reference. Do not include webhook URLs, credentials, or unnecessary source content.
Related workflowsPermalink to Related workflows
- Findings and triageUnderstand decisions that can change confirmed counts.
- Fix workflowRead proposal, pull-request, and verification activity in context.
- Security automationSeparate configuration from actual run and delivery outcomes.
- Reports and exportsPrepare a handoff that retains the underlying assessment limits.