About access permissions on GitHub
Para llevar a cabo cualquier acción en GitHub, tal como crear una solicitud de cambios en un repositorio o cambiar los ajustes de facturación de una organización, los individuos deben tener acceso suficiente a la cuenta o recurso relevante. Los permisos son los que controlan este tipo de acceso. Un permiso es la capacidad de llevar a cabo una acción específica. Por ejemplo, la capacidad de borrar una propuesta constituye un permiso. Un rol es un conjunto de permisos que puedes asignar a los individuos o equipos.
Roles work differently for different types of accounts. For more information about accounts, see Tipos de cuentas de GitHub.
Personal accounts
A repository owned by a personal account has two permission levels: the repository owner and collaborators. See Niveles de permisos para un repositorio de una cuenta personal.
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 Roles en una empresa.
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 cuentas de usuario administradas 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 cuentas de usuario administradas can be granted the same granular access levels available for regular organizations. For more information, see Acerca de 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.