Identity & Access
SSO, OAuth provider, session service, RBAC, device trust.
Persona → context mapping
Which sources each role sees when they (or an agent on their behalf) asks for context on this team.
Engineer
5 sources
</>
identity/auth-gateway</>
identity/session-storeC
Identity System Design (v3)J
ID — Security Backlog{}
Auth API v2 specArchitect
3 sources
C
Identity System Design (v3)C
Threat model — Identity{}
Auth API v2 specSecurity
3 sources
</>
identity/auth-gatewayC
Threat model — IdentityS
SOC2 Audit Evidence — 2026BA
0 sources
No sources mapped
PO
1 sources
J
ID — Security BacklogCode repositories 2
</>
identity/auth-gateway
github.com/acme/auth-gateway
</>
identity/session-store
github.com/acme/session-store
Documentation & knowledge 3
C
Identity System Design (v3)
confluence.acme.io/spaces/ID/sysdesign
C
Threat model — Identity
confluence.acme.io/spaces/SEC/threat-id
S
SOC2 Audit Evidence — 2026
sharepoint.acme.io/sites/sec/soc2-2026
Product & delivery 1
J
ID — Security Backlog
acme.atlassian.net/browse/ID
API contracts 1
{}
Auth API v2 spec
api.acme.io/auth/v2/openapi.yaml
Coverage
How well this team's context is mapped.
88/ 100
Code repos2 mapped
Architecture docs3 mapped
API contracts1 mapped
Delivery board✓ Linked
Security threat model✓ Linked
Owners
Approvers for PRs generated against this team's scope.
MB
Maria Bakker
Platform Admin
AC
Amara Chen
Tech Lead
JT
Jonas Tirel
Security Champion