You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The **Security Manager** org role (separate from repo roles) grants read access to security alerts across all repos in the org without needing Admin on each repo. This is the exam-preferred answer for "how to give the security team visibility without over-provisioning."
|**Enterprise Owner**| Manage all orgs, enterprise policies, billing, SAML/SCIM, audit log, runners, IP allow lists |
248
+
|**Enterprise Billing Manager**| View and manage enterprise billing only — no access to orgs, code, or policies |
249
+
|**Enterprise Member**| Default role — access governed by org membership within the enterprise |
250
+
251
+
### Organization Roles (Extended)
252
+
253
+
| Role | Capabilities |
254
+
|---|---|
255
+
|**Owner**| Full admin — manage members, teams, billing, security settings, integrations, and policies |
256
+
|**Member**| Access based on default permissions + team membership |
257
+
|**Billing Manager**| View and manage org billing — no code or settings access |
258
+
|**Security Manager**| View security alerts and settings across all repos — no code write access |
259
+
|**Outside Collaborator**| Access to specific repos only — no org membership, no team access, no seat consumed |
260
+
261
+
::: warning Trap
262
+
The **Security Manager** role is an organization role, not a repository role. It is assigned to a **team**, not individual users. The exam tests this distinction.
263
+
:::
264
+
265
+
---
266
+
160
267
## Least Privilege in Practice
161
268
162
269
The principle of **least privilege** means giving users only the permissions they need — no more.
0 commit comments