When a user becomes a member of multiple GitHub organizations, which THREE of the following are important considerations for administrators? (Choose three.)

Question

Options

• AThe user will automatically have the same role across all organizations.
• BThe user's repository access and/or team membership needs to be managed separately for each
• CThe user will need to authorize credentials separately for each SAML-enabled organization.
• DThe user will have different permission levels in each organization.
• EThe user's profile information becomes private to non-organization members.
• FThe user's personal repositories will become accessible to all organizations.

• A
  5% (1)
• B
  82% (18)
• E
  9% (2)
• F
  5% (1)

Explanation

When a user joins multiple GitHub organizations, administrators must manage repository access and team membership independently per organization (B), because organizations are isolated silos with no shared membership state. Each SAML-enabled organization requires its own credential authorization (C) - a user's SSO session in Org A does not carry over to Org B. Permission levels are set per-organization (D), so a user could be an Owner in one and a Member in another, depending on what administrators configure in each.

Why the distractors are wrong:

• A contradicts D - roles are not mirrored across organizations; they're configured independently.
• E is false - profile visibility is controlled by the user's own privacy settings, not organization membership.
• F is false - personal repositories remain personal and are never automatically exposed to organizations the user joins.

Memory tip: Think of each GitHub organization as a separate company building. Joining multiple companies doesn't give you the same badge, the same keycard system, or the same office access everywhere - you negotiate each separately. That maps directly to B (access), C (SAML credentials), and D (permission levels).

No community discussion yet for this question.