A single GitHub user account can be a member of multiple, distinct organizations. Each organization functions as a separate administrative boundary. Therefore, an administrator must manage a user's team memberships and repository access on a per-organization basis. Roles and permissions are not global; they are assigned within the context of each organization, resulting in different permission levels for the user across them. Similarly, security configurations like SAML single sign-on (SSO) are managed per-organization. A user must authenticate and authorize their credentials separately for each SAML-enabled organization they need to access, as authentication policies are not shared between them.

A. Roles are assigned independently within each organization; they are not automatically synchronized or inherited from one organization to another.

E. A user's core profile remains public. The user can choose to publicize or hide their membership in a specific organization, but this does not make their entire profile private.

F. A user's personal account and repositories are entirely separate from any organization they join. Organizational membership does not grant access to personal repositories.

1. GitHub Docs

"Roles in an organization": This document details the different roles (owner

member

billing manager) that are assigned within a specific organization. It states

"In an organization

you can assign different roles to members

" which confirms that roles are managed separately for each organization

supporting answers B and D and refuting A.

2. GitHub Docs

"About identity and access management with SAML single sign-on": This source explains that SAML SSO is configured at the organization level. It notes

"After you enable SAML SSO for your organization

you must create a linked identity for each member

" and "When a member accesses resources in an organization that uses SAML SSO

GitHub will redirect them to the organization's IdP to authenticate." This confirms that authentication is a separate process for each organization

supporting answer C.

3. GitHub Docs

"Managing your organization membership": This page clarifies the relationship between a user and an organization

including the ability to "Publicize or hide your organization membership." This shows that profile privacy is related to membership visibility

not the entire profile

refuting E. The entire concept of managing membership implies a separation that refutes F.