| 1 | --- |
| 2 | title: GitHub audit |
| 3 | description: Collect and review GitHub audit-related data inside CoPilot. |
| 4 | --- |
| 5 | |
| 6 | ## What it is |
| 7 | |
| 8 | CoPilot contains schema and capability to store GitHub audit-related data (wireframe). |
| 9 | |
| 10 | ## Who this is for |
| 11 | |
| 12 | - **Admin / Platform**: org security posture and governance |
| 13 | |
| 14 | ## Inputs (what it needs) |
| 15 | |
| 16 | - GitHub org access and permissions to collect audit/security signals (implementation-dependent) |
| 17 | |
| 18 | ## Outputs (what you get) |
| 19 | |
| 20 | - Audit views / reports (to be documented) |
| 21 | |
| 22 | ## Where it lives in the UI |
| 23 | |
| 24 | - (Wireframe) This page will be updated with the exact menu path/route. |
| 25 | |
| 26 | ## Success criteria |
| 27 | |
| 28 | - [ ] GitHub audit data can be collected |
| 29 | - [ ] Data can be displayed and searched |
| 30 | |
| 31 | ## Safety / guardrails |
| 32 | |
| 33 | - Treat audit exports as sensitive (users, access patterns, security events). |
| 34 | |
| 35 | ## Troubleshooting |
| 36 | |
| 37 | - Confirm GitHub permissions/token scopes |
| 38 | - Confirm collection job is running and storing results |