Review GitHub evidence
Inspect captured security, governance, access, automation, activity, and repository information.
Open Workspace > Integrations, then select the GitHub account you need. This requires workspace Admin or Owner access and the Platform feature. Check the connection health and capture time before reviewing its evidence.
Choose the evidence view
Start with Overview for connection health and review priorities. Then choose the section that matches your question.
| Section | What to check |
|---|---|
| Security | Captured alerts, secrets, advisories, and license information. |
| Compliance | Organization controls and repository coverage. |
| Governance | Change management, Policy files, or Custom properties. |
| People & access | Members, teams, or repository access evidence. |
| Automation | Self-hosted runners or outgoing webhooks. |
| Activity | Deliveries, Audit log, Security alerts, Rule changes, Dismissal requests, or Deployments. |
| Repositories | Repository access and captured repository metadata. |
These views show captured evidence. To change repository permissions, policies, members, or other GitHub settings, make the change on GitHub and request a new sync in Sorena.
Find a repository
- Choose Repositories and enter its name in Search repositories.
- Check the visibility and archive-state filters. A repository can disappear from the results because a previous filter is still active.
- Open Advanced filters when you need to narrow by owner or language.
- Review the sort order and other result pages before concluding that a repository is missing.
- Use Reset filters to return to a broader list.
If the repository is still missing, check the installation's repository access on GitHub. A sync cannot collect a repository the app cannot access.
Inspect people, automation, and activity
Choose a subsection before searching or filtering it. For example, check members separately from teams in People & access, and check runners separately from webhooks in Automation. Runner status and webhook scope or active-state filters answer different questions.
In Activity, select the event family you need before narrowing the results. A delivery record concerns webhook delivery; an audit record or deployment record concerns a different type of activity. Review the time and context of the matching record before using it as evidence.
Read evidence status before using a result
An empty filtered result means no captured rows matched those filters. Clear the filters to check the broader capture. A permission-limited, partial, stale, or unavailable section needs a different response: check its message, installation access, and last confirmed capture.
Use a section's retry action when it reports a loading failure. If several sections are missing evidence after a permissions change, sync the connection. Include the section, status, and time when asking support for help; keep private repository names and filtered addresses out of the report unless your team has approved sharing them.