In Copilot Memory, who can see repository-level facts?
Why A is the answer
Users with read access to the repository
Repository-level facts are shared with collaborators, while user-level preferences follow one person.
In detail
- Repository-level facts are visible to users with read access to the repository.
- Treat stored facts like repository content.
Use case
An illustrative scenario, not a real incident.
A repository fact in Copilot Memory is visible to people with read access to that repository, so it should hold nothing they should not see.
See it in different ways
mindmap
root((Agent memory))
Short term
This task only
External
Files in the repository
Progress artifacts
Copilot Memory
Repository facts
Care
Expiry
Pruningflowchart TD
Q{"Does the user have read access?"}
Q -->|"Yes"| A0["Can see repository facts"]
Q -->|"No"| A1["Cannot see them"]Key point: Repository memory follows read access.
Why the other options are wrong
- B. Anyone on the internet, including for private repositories
- Private repository facts are not public.
- C. Only the person whose session created each fact
- They are not limited to the person whose session created them.
- D. Only enterprise owners, through the audit log
- They are not limited to enterprise owners.