About access permissions on GitHub
Zum Ausführen von Aktionen für GitHub, z. B. das Erstellen eines Pull Requests in einem Repository oder das Ändern der Abrechnungseinstellungen einer Organisation, muss eine Person über ausreichenden Zugriff auf das relevante Konto oder die entsprechende Ressource verfügen. Dieser Zugriff wird mit Berechtigungen gesteuert. Eine Berechtigung ist die Möglichkeit, eine bestimmte Aktion auszuführen. Die Möglichkeit, ein Issue zu löschen, ist beispielsweise eine Berechtigung. Eine Rolle ist eine Reihe von Berechtigungen, die du Personen oder Teams zuweisen kannst.
Roles work differently for different types of accounts. For more information about accounts, see Arten von GitHub-Konten.
Personal accounts
A repository owned by a personal account has two permission levels: the repository owner and collaborators. See Berechtigungsebenen für ein Repository in einem persönlichen Konto.
Organization accounts
Organization members can have owner, billing manager, or member roles. Owners have complete administrative access to your organization, while billing managers can manage billing settings. Member is the default role for everyone else. You can manage access permissions for multiple members at a time with teams. For more information, see:
Enterprise accounts
Enterprise owners have ultimate power over the enterprise account and can take every action in the enterprise account. Billing managers can manage your enterprise account's billing settings. Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings.
Enterprise owners cannot access organization content or repositories unless they are explicitly granted a role in the organization. However, enterprise owners can manage enterprise settings and policies that impact an organization in the enterprise. For more information, see Rollen in einem Unternehmen.
If an enterprise uses Enterprise Managed Users, members are provisioned as new personal accounts on GitHub and are fully managed by the identity provider. The verwaltete Benutzerkonten have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the verwaltete Benutzerkonten can be granted the same granular access levels available for regular organizations. For more information, see Informationen zu Enterprise Managed Users.
Next steps
Next, learn about how you can use rulesets to manage how people interact with your enterprise's repositories. See About rulesets.