Difference between revisions of "GitHub organization"
Jump to navigation
Jump to search
(Created page with "* https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization == See also == * {{GitHub}} Categ...") |
|||
| (15 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
* https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization | * https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization | ||
| + | == Organization Roles == | ||
| + | * [[Owners]] | ||
| + | * Members | ||
| + | * Billing managers | ||
| + | * Security managers (beta as Jan 2022). It gives every member of the team permissions to manage security alerts and settings across your organization, as well as read permissions for all repositories in the organization. | ||
| + | * Outside collaborators | ||
| + | |||
| + | |||
| + | * Repository roles: https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization | ||
| + | ** Read: Recommended for non-code contributors who want to view or discuss your project | ||
| + | ** Triage: Recommended for contributors who need to proactively manage issues and pull requests without write access | ||
| + | ** Write: Recommended for contributors who actively push to your project | ||
| + | ** Maintain: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions | ||
| + | ** Admin: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository | ||
| + | |||
| + | == Related terms == | ||
| + | * [[Google Cloud organizations]] | ||
| + | * [[GitHub Free for organizations]] and [[GitHub Team]] | ||
| + | * [[GitHub Enterprise]] | ||
| + | * [[GitHub base permissions]] | ||
== See also == | == See also == | ||
Latest revision as of 07:01, 2 March 2023
Organization Roles[edit]
- Owners
- Members
- Billing managers
- Security managers (beta as Jan 2022). It gives every member of the team permissions to manage security alerts and settings across your organization, as well as read permissions for all repositories in the organization.
- Outside collaborators
- Repository roles: https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization
- Read: Recommended for non-code contributors who want to view or discuss your project
- Triage: Recommended for contributors who need to proactively manage issues and pull requests without write access
- Write: Recommended for contributors who actively push to your project
- Maintain: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions
- Admin: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository
Related terms[edit]
- Google Cloud organizations
- GitHub Free for organizations and GitHub Team
- GitHub Enterprise
- GitHub base permissions
See also[edit]
- GitHub, GitHub Actions, GitHub Actions Runner, Events, CodeQL, GitHub Desktop, GitHub organization, base permissions, GitHub Copilot,
.gitignore, GitHub Codespaces, GitHub Marketplace, GitHub Apps, GitHub Enterprise Server, GitHub CLI (gh), Dependabot, GitHub security,.github/, GitHub code scanning, GitHub Pages, GitHub Packages, GitHub Advanced Security, GitHub Mobile, GitHub Importer, GitHub versions
Advertising:
