Heard you liked access, so we built Access to...
summary
Discord builds and runs an open source portal called Access that syncs group membership to Okta, exposes Role groups mapped to Okta, and lets owners approve self‑serve requests with time-bounded access and bulk renewals. It uses a Python Flask backend, React TypeScript front end, Postgres, Docker/Kubernetes, and a plugin system for notifications and automated approvals. Deployed company‑wide for about a year, it shrinks access review time from days to hours, reduces confused‑deputy rubber stamping, and produces auditable historical views.
AI-written summary · about
chapters (11)
- 0:00Introduction and motivation
- 1:40Access control necessity
- 2:20Guiding goals and principles
- 6:22The role-based approach
- 8:12Evaluating external solutions
- 11:22Foundational architecture
- 12:51Key features and functionality
- 21:18Technical stack and design
- 23:17Impact and business results
- 24:25Open sourcing the project
- 25:01Q&A session
related talks
24mEnhancing Compliance and Safety with Argo CD Ephemeral Access
16mAccess Granted with AuthZed
01h 04mTrue Serverless Applications Implementing Cloud Native Access Control Service
46mRebuilding Access Management with ReBAC
27mLessons Learned Implementing Meaningful Access Controls...
48mAccess Control for your API Endpoints with Auth0
23mOne Login to Rule Them All: Cross-App Access for MCP
26mFine-Grained User Authorization for Kubernetes with OPA and LDAP