diff --git a/descriptions/api.github.com/api.github.com.2022-11-28.json b/descriptions/api.github.com/api.github.com.2022-11-28.json
index 81f2146f22..0ba374ab55 100644
--- a/descriptions/api.github.com/api.github.com.2022-11-28.json
+++ b/descriptions/api.github.com/api.github.com.2022-11-28.json
@@ -38681,7 +38681,7 @@
     "/repos/{owner}/{repo}/collaborators": {
       "get": {
         "summary": "List repository collaborators",
-        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nOrganization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have push access to the repository to use this endpoint.\n\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
+        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nThe `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
         "tags": [
           "repos"
         ],
@@ -38934,7 +38934,7 @@
     "/repos/{owner}/{repo}/collaborators/{username}/permission": {
       "get": {
         "summary": "Get repository permissions for a user",
-        "description": "Checks the repository permission of a collaborator. The possible repository\npermissions are `admin`, `write`, `read`, and `none`.\n\n*Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the\ncollaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The\n`permissions` hash can also be used to determine which base level of access the collaborator has to the repository.",
+        "description": "Checks the repository permission and role of a collaborator.\n\nThe `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`.\nThe `role_name` attribute provides the name of the assigned role, including custom roles. The\n`permission` can also be used to determine which base level of access the collaborator has to the repository.\n\nThe calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.",
         "tags": [
           "repos"
         ],
diff --git a/descriptions/api.github.com/api.github.com.2022-11-28.yaml b/descriptions/api.github.com/api.github.com.2022-11-28.yaml
index 448219f3e1..e9e12a1f7f 100644
--- a/descriptions/api.github.com/api.github.com.2022-11-28.yaml
+++ b/descriptions/api.github.com/api.github.com.2022-11-28.yaml
@@ -28157,12 +28157,12 @@ paths:
       summary: List repository collaborators
       description: |-
         For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.
-        Organization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.
+        The `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
 
         Team members will include the members of child teams.
 
-        The authenticated user must have push access to the repository to use this endpoint.
-
+        The authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.
         OAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.
       tags:
       - repos
@@ -28387,13 +28387,15 @@ paths:
     get:
       summary: Get repository permissions for a user
       description: |-
-        Checks the repository permission of a collaborator. The possible repository
-        permissions are `admin`, `write`, `read`, and `none`.
+        Checks the repository permission and role of a collaborator.
+
+        The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
+        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`.
+        The `role_name` attribute provides the name of the assigned role, including custom roles. The
+        `permission` can also be used to determine which base level of access the collaborator has to the repository.
 
-        *Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
-        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the
-        collaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The
-        `permissions` hash can also be used to determine which base level of access the collaborator has to the repository.
+        The calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
       tags:
       - repos
       operationId: repos/get-collaborator-permission-level
diff --git a/descriptions/api.github.com/api.github.com.json b/descriptions/api.github.com/api.github.com.json
index 81f2146f22..0ba374ab55 100644
--- a/descriptions/api.github.com/api.github.com.json
+++ b/descriptions/api.github.com/api.github.com.json
@@ -38681,7 +38681,7 @@
     "/repos/{owner}/{repo}/collaborators": {
       "get": {
         "summary": "List repository collaborators",
-        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nOrganization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have push access to the repository to use this endpoint.\n\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
+        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nThe `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
         "tags": [
           "repos"
         ],
@@ -38934,7 +38934,7 @@
     "/repos/{owner}/{repo}/collaborators/{username}/permission": {
       "get": {
         "summary": "Get repository permissions for a user",
-        "description": "Checks the repository permission of a collaborator. The possible repository\npermissions are `admin`, `write`, `read`, and `none`.\n\n*Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the\ncollaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The\n`permissions` hash can also be used to determine which base level of access the collaborator has to the repository.",
+        "description": "Checks the repository permission and role of a collaborator.\n\nThe `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`.\nThe `role_name` attribute provides the name of the assigned role, including custom roles. The\n`permission` can also be used to determine which base level of access the collaborator has to the repository.\n\nThe calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.",
         "tags": [
           "repos"
         ],
diff --git a/descriptions/api.github.com/api.github.com.yaml b/descriptions/api.github.com/api.github.com.yaml
index 448219f3e1..e9e12a1f7f 100644
--- a/descriptions/api.github.com/api.github.com.yaml
+++ b/descriptions/api.github.com/api.github.com.yaml
@@ -28157,12 +28157,12 @@ paths:
       summary: List repository collaborators
       description: |-
         For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.
-        Organization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.
+        The `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
 
         Team members will include the members of child teams.
 
-        The authenticated user must have push access to the repository to use this endpoint.
-
+        The authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.
         OAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.
       tags:
       - repos
@@ -28387,13 +28387,15 @@ paths:
     get:
       summary: Get repository permissions for a user
       description: |-
-        Checks the repository permission of a collaborator. The possible repository
-        permissions are `admin`, `write`, `read`, and `none`.
+        Checks the repository permission and role of a collaborator.
+
+        The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
+        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`.
+        The `role_name` attribute provides the name of the assigned role, including custom roles. The
+        `permission` can also be used to determine which base level of access the collaborator has to the repository.
 
-        *Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
-        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the
-        collaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The
-        `permissions` hash can also be used to determine which base level of access the collaborator has to the repository.
+        The calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
       tags:
       - repos
       operationId: repos/get-collaborator-permission-level
diff --git a/descriptions/api.github.com/dereferenced/api.github.com.2022-11-28.deref.json b/descriptions/api.github.com/dereferenced/api.github.com.2022-11-28.deref.json
index 9502ab08ea..d2c42e95ee 100644
--- a/descriptions/api.github.com/dereferenced/api.github.com.2022-11-28.deref.json
+++ b/descriptions/api.github.com/dereferenced/api.github.com.2022-11-28.deref.json
@@ -239628,7 +239628,7 @@
     "/repos/{owner}/{repo}/collaborators": {
       "get": {
         "summary": "List repository collaborators",
-        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nOrganization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have push access to the repository to use this endpoint.\n\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
+        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nThe `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
         "tags": [
           "repos"
         ],
@@ -241433,7 +241433,7 @@
     "/repos/{owner}/{repo}/collaborators/{username}/permission": {
       "get": {
         "summary": "Get repository permissions for a user",
-        "description": "Checks the repository permission of a collaborator. The possible repository\npermissions are `admin`, `write`, `read`, and `none`.\n\n*Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the\ncollaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The\n`permissions` hash can also be used to determine which base level of access the collaborator has to the repository.",
+        "description": "Checks the repository permission and role of a collaborator.\n\nThe `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`.\nThe `role_name` attribute provides the name of the assigned role, including custom roles. The\n`permission` can also be used to determine which base level of access the collaborator has to the repository.\n\nThe calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.",
         "tags": [
           "repos"
         ],
diff --git a/descriptions/api.github.com/dereferenced/api.github.com.2022-11-28.deref.yaml b/descriptions/api.github.com/dereferenced/api.github.com.2022-11-28.deref.yaml
index d3beeaaf3e..ca618a4e9b 100644
--- a/descriptions/api.github.com/dereferenced/api.github.com.2022-11-28.deref.yaml
+++ b/descriptions/api.github.com/dereferenced/api.github.com.2022-11-28.deref.yaml
@@ -58112,12 +58112,12 @@ paths:
       summary: List repository collaborators
       description: |-
         For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.
-        Organization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.
+        The `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
 
         Team members will include the members of child teams.
 
-        The authenticated user must have push access to the repository to use this endpoint.
-
+        The authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.
         OAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.
       tags:
       - repos
@@ -58647,13 +58647,15 @@ paths:
     get:
       summary: Get repository permissions for a user
       description: |-
-        Checks the repository permission of a collaborator. The possible repository
-        permissions are `admin`, `write`, `read`, and `none`.
+        Checks the repository permission and role of a collaborator.
+
+        The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
+        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`.
+        The `role_name` attribute provides the name of the assigned role, including custom roles. The
+        `permission` can also be used to determine which base level of access the collaborator has to the repository.
 
-        *Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
-        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the
-        collaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The
-        `permissions` hash can also be used to determine which base level of access the collaborator has to the repository.
+        The calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
       tags:
       - repos
       operationId: repos/get-collaborator-permission-level
diff --git a/descriptions/api.github.com/dereferenced/api.github.com.deref.json b/descriptions/api.github.com/dereferenced/api.github.com.deref.json
index 9502ab08ea..d2c42e95ee 100644
--- a/descriptions/api.github.com/dereferenced/api.github.com.deref.json
+++ b/descriptions/api.github.com/dereferenced/api.github.com.deref.json
@@ -239628,7 +239628,7 @@
     "/repos/{owner}/{repo}/collaborators": {
       "get": {
         "summary": "List repository collaborators",
-        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nOrganization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have push access to the repository to use this endpoint.\n\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
+        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nThe `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
         "tags": [
           "repos"
         ],
@@ -241433,7 +241433,7 @@
     "/repos/{owner}/{repo}/collaborators/{username}/permission": {
       "get": {
         "summary": "Get repository permissions for a user",
-        "description": "Checks the repository permission of a collaborator. The possible repository\npermissions are `admin`, `write`, `read`, and `none`.\n\n*Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the\ncollaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The\n`permissions` hash can also be used to determine which base level of access the collaborator has to the repository.",
+        "description": "Checks the repository permission and role of a collaborator.\n\nThe `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`.\nThe `role_name` attribute provides the name of the assigned role, including custom roles. The\n`permission` can also be used to determine which base level of access the collaborator has to the repository.\n\nThe calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.",
         "tags": [
           "repos"
         ],
diff --git a/descriptions/api.github.com/dereferenced/api.github.com.deref.yaml b/descriptions/api.github.com/dereferenced/api.github.com.deref.yaml
index d3beeaaf3e..ca618a4e9b 100644
--- a/descriptions/api.github.com/dereferenced/api.github.com.deref.yaml
+++ b/descriptions/api.github.com/dereferenced/api.github.com.deref.yaml
@@ -58112,12 +58112,12 @@ paths:
       summary: List repository collaborators
       description: |-
         For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.
-        Organization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.
+        The `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
 
         Team members will include the members of child teams.
 
-        The authenticated user must have push access to the repository to use this endpoint.
-
+        The authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.
         OAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.
       tags:
       - repos
@@ -58647,13 +58647,15 @@ paths:
     get:
       summary: Get repository permissions for a user
       description: |-
-        Checks the repository permission of a collaborator. The possible repository
-        permissions are `admin`, `write`, `read`, and `none`.
+        Checks the repository permission and role of a collaborator.
+
+        The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
+        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`.
+        The `role_name` attribute provides the name of the assigned role, including custom roles. The
+        `permission` can also be used to determine which base level of access the collaborator has to the repository.
 
-        *Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
-        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the
-        collaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The
-        `permissions` hash can also be used to determine which base level of access the collaborator has to the repository.
+        The calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
       tags:
       - repos
       operationId: repos/get-collaborator-permission-level
diff --git a/descriptions/ghec/dereferenced/ghec.2022-11-28.deref.json b/descriptions/ghec/dereferenced/ghec.2022-11-28.deref.json
index 2864884754..fe895b6262 100644
--- a/descriptions/ghec/dereferenced/ghec.2022-11-28.deref.json
+++ b/descriptions/ghec/dereferenced/ghec.2022-11-28.deref.json
@@ -275144,7 +275144,7 @@
     "/repos/{owner}/{repo}/collaborators": {
       "get": {
         "summary": "List repository collaborators",
-        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nOrganization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have push access to the repository to use this endpoint.\n\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
+        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nThe `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
         "tags": [
           "repos"
         ],
@@ -276961,7 +276961,7 @@
     "/repos/{owner}/{repo}/collaborators/{username}/permission": {
       "get": {
         "summary": "Get repository permissions for a user",
-        "description": "Checks the repository permission of a collaborator. The possible repository\npermissions are `admin`, `write`, `read`, and `none`.\n\n*Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the\ncollaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The\n`permissions` hash can also be used to determine which base level of access the collaborator has to the repository.",
+        "description": "Checks the repository permission and role of a collaborator.\n\nThe `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`.\nThe `role_name` attribute provides the name of the assigned role, including custom roles. The\n`permission` can also be used to determine which base level of access the collaborator has to the repository.\n\nThe calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.",
         "tags": [
           "repos"
         ],
diff --git a/descriptions/ghec/dereferenced/ghec.2022-11-28.deref.yaml b/descriptions/ghec/dereferenced/ghec.2022-11-28.deref.yaml
index ba197c6535..2211b1824b 100644
--- a/descriptions/ghec/dereferenced/ghec.2022-11-28.deref.yaml
+++ b/descriptions/ghec/dereferenced/ghec.2022-11-28.deref.yaml
@@ -66393,12 +66393,12 @@ paths:
       summary: List repository collaborators
       description: |-
         For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.
-        Organization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.
+        The `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
 
         Team members will include the members of child teams.
 
-        The authenticated user must have push access to the repository to use this endpoint.
-
+        The authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.
         OAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.
       tags:
       - repos
@@ -66928,13 +66928,15 @@ paths:
     get:
       summary: Get repository permissions for a user
       description: |-
-        Checks the repository permission of a collaborator. The possible repository
-        permissions are `admin`, `write`, `read`, and `none`.
+        Checks the repository permission and role of a collaborator.
+
+        The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
+        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`.
+        The `role_name` attribute provides the name of the assigned role, including custom roles. The
+        `permission` can also be used to determine which base level of access the collaborator has to the repository.
 
-        *Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
-        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the
-        collaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The
-        `permissions` hash can also be used to determine which base level of access the collaborator has to the repository.
+        The calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
       tags:
       - repos
       operationId: repos/get-collaborator-permission-level
diff --git a/descriptions/ghec/dereferenced/ghec.deref.json b/descriptions/ghec/dereferenced/ghec.deref.json
index 2864884754..fe895b6262 100644
--- a/descriptions/ghec/dereferenced/ghec.deref.json
+++ b/descriptions/ghec/dereferenced/ghec.deref.json
@@ -275144,7 +275144,7 @@
     "/repos/{owner}/{repo}/collaborators": {
       "get": {
         "summary": "List repository collaborators",
-        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nOrganization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have push access to the repository to use this endpoint.\n\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
+        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nThe `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
         "tags": [
           "repos"
         ],
@@ -276961,7 +276961,7 @@
     "/repos/{owner}/{repo}/collaborators/{username}/permission": {
       "get": {
         "summary": "Get repository permissions for a user",
-        "description": "Checks the repository permission of a collaborator. The possible repository\npermissions are `admin`, `write`, `read`, and `none`.\n\n*Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the\ncollaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The\n`permissions` hash can also be used to determine which base level of access the collaborator has to the repository.",
+        "description": "Checks the repository permission and role of a collaborator.\n\nThe `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`.\nThe `role_name` attribute provides the name of the assigned role, including custom roles. The\n`permission` can also be used to determine which base level of access the collaborator has to the repository.\n\nThe calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.",
         "tags": [
           "repos"
         ],
diff --git a/descriptions/ghec/dereferenced/ghec.deref.yaml b/descriptions/ghec/dereferenced/ghec.deref.yaml
index ba197c6535..2211b1824b 100644
--- a/descriptions/ghec/dereferenced/ghec.deref.yaml
+++ b/descriptions/ghec/dereferenced/ghec.deref.yaml
@@ -66393,12 +66393,12 @@ paths:
       summary: List repository collaborators
       description: |-
         For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.
-        Organization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.
+        The `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
 
         Team members will include the members of child teams.
 
-        The authenticated user must have push access to the repository to use this endpoint.
-
+        The authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.
         OAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.
       tags:
       - repos
@@ -66928,13 +66928,15 @@ paths:
     get:
       summary: Get repository permissions for a user
       description: |-
-        Checks the repository permission of a collaborator. The possible repository
-        permissions are `admin`, `write`, `read`, and `none`.
+        Checks the repository permission and role of a collaborator.
+
+        The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
+        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`.
+        The `role_name` attribute provides the name of the assigned role, including custom roles. The
+        `permission` can also be used to determine which base level of access the collaborator has to the repository.
 
-        *Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
-        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the
-        collaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The
-        `permissions` hash can also be used to determine which base level of access the collaborator has to the repository.
+        The calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
       tags:
       - repos
       operationId: repos/get-collaborator-permission-level
diff --git a/descriptions/ghec/ghec.2022-11-28.json b/descriptions/ghec/ghec.2022-11-28.json
index 61d3db3cba..09e1da0b62 100644
--- a/descriptions/ghec/ghec.2022-11-28.json
+++ b/descriptions/ghec/ghec.2022-11-28.json
@@ -46742,7 +46742,7 @@
     "/repos/{owner}/{repo}/collaborators": {
       "get": {
         "summary": "List repository collaborators",
-        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nOrganization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have push access to the repository to use this endpoint.\n\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
+        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nThe `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
         "tags": [
           "repos"
         ],
@@ -46995,7 +46995,7 @@
     "/repos/{owner}/{repo}/collaborators/{username}/permission": {
       "get": {
         "summary": "Get repository permissions for a user",
-        "description": "Checks the repository permission of a collaborator. The possible repository\npermissions are `admin`, `write`, `read`, and `none`.\n\n*Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the\ncollaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The\n`permissions` hash can also be used to determine which base level of access the collaborator has to the repository.",
+        "description": "Checks the repository permission and role of a collaborator.\n\nThe `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`.\nThe `role_name` attribute provides the name of the assigned role, including custom roles. The\n`permission` can also be used to determine which base level of access the collaborator has to the repository.\n\nThe calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.",
         "tags": [
           "repos"
         ],
diff --git a/descriptions/ghec/ghec.2022-11-28.yaml b/descriptions/ghec/ghec.2022-11-28.yaml
index 7947c92dd8..a61d1ca96f 100644
--- a/descriptions/ghec/ghec.2022-11-28.yaml
+++ b/descriptions/ghec/ghec.2022-11-28.yaml
@@ -33922,12 +33922,12 @@ paths:
       summary: List repository collaborators
       description: |-
         For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.
-        Organization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.
+        The `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
 
         Team members will include the members of child teams.
 
-        The authenticated user must have push access to the repository to use this endpoint.
-
+        The authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.
         OAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.
       tags:
       - repos
@@ -34152,13 +34152,15 @@ paths:
     get:
       summary: Get repository permissions for a user
       description: |-
-        Checks the repository permission of a collaborator. The possible repository
-        permissions are `admin`, `write`, `read`, and `none`.
+        Checks the repository permission and role of a collaborator.
+
+        The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
+        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`.
+        The `role_name` attribute provides the name of the assigned role, including custom roles. The
+        `permission` can also be used to determine which base level of access the collaborator has to the repository.
 
-        *Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
-        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the
-        collaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The
-        `permissions` hash can also be used to determine which base level of access the collaborator has to the repository.
+        The calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
       tags:
       - repos
       operationId: repos/get-collaborator-permission-level
diff --git a/descriptions/ghec/ghec.json b/descriptions/ghec/ghec.json
index 61d3db3cba..09e1da0b62 100644
--- a/descriptions/ghec/ghec.json
+++ b/descriptions/ghec/ghec.json
@@ -46742,7 +46742,7 @@
     "/repos/{owner}/{repo}/collaborators": {
       "get": {
         "summary": "List repository collaborators",
-        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nOrganization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have push access to the repository to use this endpoint.\n\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
+        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nThe `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
         "tags": [
           "repos"
         ],
@@ -46995,7 +46995,7 @@
     "/repos/{owner}/{repo}/collaborators/{username}/permission": {
       "get": {
         "summary": "Get repository permissions for a user",
-        "description": "Checks the repository permission of a collaborator. The possible repository\npermissions are `admin`, `write`, `read`, and `none`.\n\n*Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the\ncollaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The\n`permissions` hash can also be used to determine which base level of access the collaborator has to the repository.",
+        "description": "Checks the repository permission and role of a collaborator.\n\nThe `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`.\nThe `role_name` attribute provides the name of the assigned role, including custom roles. The\n`permission` can also be used to determine which base level of access the collaborator has to the repository.\n\nThe calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.",
         "tags": [
           "repos"
         ],
diff --git a/descriptions/ghec/ghec.yaml b/descriptions/ghec/ghec.yaml
index 7947c92dd8..a61d1ca96f 100644
--- a/descriptions/ghec/ghec.yaml
+++ b/descriptions/ghec/ghec.yaml
@@ -33922,12 +33922,12 @@ paths:
       summary: List repository collaborators
       description: |-
         For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.
-        Organization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.
+        The `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
 
         Team members will include the members of child teams.
 
-        The authenticated user must have push access to the repository to use this endpoint.
-
+        The authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.
         OAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.
       tags:
       - repos
@@ -34152,13 +34152,15 @@ paths:
     get:
       summary: Get repository permissions for a user
       description: |-
-        Checks the repository permission of a collaborator. The possible repository
-        permissions are `admin`, `write`, `read`, and `none`.
+        Checks the repository permission and role of a collaborator.
+
+        The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
+        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`.
+        The `role_name` attribute provides the name of the assigned role, including custom roles. The
+        `permission` can also be used to determine which base level of access the collaborator has to the repository.
 
-        *Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
-        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the
-        collaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The
-        `permissions` hash can also be used to determine which base level of access the collaborator has to the repository.
+        The calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
       tags:
       - repos
       operationId: repos/get-collaborator-permission-level
diff --git a/descriptions/ghes-3.12/dereferenced/ghes-3.12.2022-11-28.deref.json b/descriptions/ghes-3.12/dereferenced/ghes-3.12.2022-11-28.deref.json
index 9c1322fab8..af951350b8 100644
--- a/descriptions/ghes-3.12/dereferenced/ghes-3.12.2022-11-28.deref.json
+++ b/descriptions/ghes-3.12/dereferenced/ghes-3.12.2022-11-28.deref.json
@@ -211676,7 +211676,7 @@
     "/repos/{owner}/{repo}/collaborators": {
       "get": {
         "summary": "List repository collaborators",
-        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nOrganization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have push access to the repository to use this endpoint.\n\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
+        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nThe `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
         "tags": [
           "repos"
         ],
@@ -212371,7 +212371,7 @@
     "/repos/{owner}/{repo}/collaborators/{username}/permission": {
       "get": {
         "summary": "Get repository permissions for a user",
-        "description": "Checks the repository permission of a collaborator. The possible repository\npermissions are `admin`, `write`, `read`, and `none`.\n\n*Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the\ncollaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The\n`permissions` hash can also be used to determine which base level of access the collaborator has to the repository.",
+        "description": "Checks the repository permission and role of a collaborator.\n\nThe `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`.\nThe `role_name` attribute provides the name of the assigned role, including custom roles. The\n`permission` can also be used to determine which base level of access the collaborator has to the repository.\n\nThe calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.",
         "tags": [
           "repos"
         ],
diff --git a/descriptions/ghes-3.12/dereferenced/ghes-3.12.2022-11-28.deref.yaml b/descriptions/ghes-3.12/dereferenced/ghes-3.12.2022-11-28.deref.yaml
index cafa1621d2..7b72261aae 100644
--- a/descriptions/ghes-3.12/dereferenced/ghes-3.12.2022-11-28.deref.yaml
+++ b/descriptions/ghes-3.12/dereferenced/ghes-3.12.2022-11-28.deref.yaml
@@ -51367,12 +51367,12 @@ paths:
       summary: List repository collaborators
       description: |-
         For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.
-        Organization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.
+        The `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
 
         Team members will include the members of child teams.
 
-        The authenticated user must have push access to the repository to use this endpoint.
-
+        The authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.
         OAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.
       tags:
       - repos
@@ -51712,13 +51712,15 @@ paths:
     get:
       summary: Get repository permissions for a user
       description: |-
-        Checks the repository permission of a collaborator. The possible repository
-        permissions are `admin`, `write`, `read`, and `none`.
+        Checks the repository permission and role of a collaborator.
+
+        The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
+        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`.
+        The `role_name` attribute provides the name of the assigned role, including custom roles. The
+        `permission` can also be used to determine which base level of access the collaborator has to the repository.
 
-        *Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
-        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the
-        collaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The
-        `permissions` hash can also be used to determine which base level of access the collaborator has to the repository.
+        The calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
       tags:
       - repos
       operationId: repos/get-collaborator-permission-level
diff --git a/descriptions/ghes-3.12/dereferenced/ghes-3.12.deref.json b/descriptions/ghes-3.12/dereferenced/ghes-3.12.deref.json
index 9c1322fab8..af951350b8 100644
--- a/descriptions/ghes-3.12/dereferenced/ghes-3.12.deref.json
+++ b/descriptions/ghes-3.12/dereferenced/ghes-3.12.deref.json
@@ -211676,7 +211676,7 @@
     "/repos/{owner}/{repo}/collaborators": {
       "get": {
         "summary": "List repository collaborators",
-        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nOrganization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have push access to the repository to use this endpoint.\n\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
+        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nThe `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
         "tags": [
           "repos"
         ],
@@ -212371,7 +212371,7 @@
     "/repos/{owner}/{repo}/collaborators/{username}/permission": {
       "get": {
         "summary": "Get repository permissions for a user",
-        "description": "Checks the repository permission of a collaborator. The possible repository\npermissions are `admin`, `write`, `read`, and `none`.\n\n*Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the\ncollaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The\n`permissions` hash can also be used to determine which base level of access the collaborator has to the repository.",
+        "description": "Checks the repository permission and role of a collaborator.\n\nThe `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`.\nThe `role_name` attribute provides the name of the assigned role, including custom roles. The\n`permission` can also be used to determine which base level of access the collaborator has to the repository.\n\nThe calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.",
         "tags": [
           "repos"
         ],
diff --git a/descriptions/ghes-3.12/dereferenced/ghes-3.12.deref.yaml b/descriptions/ghes-3.12/dereferenced/ghes-3.12.deref.yaml
index cafa1621d2..7b72261aae 100644
--- a/descriptions/ghes-3.12/dereferenced/ghes-3.12.deref.yaml
+++ b/descriptions/ghes-3.12/dereferenced/ghes-3.12.deref.yaml
@@ -51367,12 +51367,12 @@ paths:
       summary: List repository collaborators
       description: |-
         For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.
-        Organization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.
+        The `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
 
         Team members will include the members of child teams.
 
-        The authenticated user must have push access to the repository to use this endpoint.
-
+        The authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.
         OAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.
       tags:
       - repos
@@ -51712,13 +51712,15 @@ paths:
     get:
       summary: Get repository permissions for a user
       description: |-
-        Checks the repository permission of a collaborator. The possible repository
-        permissions are `admin`, `write`, `read`, and `none`.
+        Checks the repository permission and role of a collaborator.
+
+        The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
+        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`.
+        The `role_name` attribute provides the name of the assigned role, including custom roles. The
+        `permission` can also be used to determine which base level of access the collaborator has to the repository.
 
-        *Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the
-        `maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the
-        collaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The
-        `permissions` hash can also be used to determine which base level of access the collaborator has to the repository.
+        The calculated permissions are the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.
+        There is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.
       tags:
       - repos
       operationId: repos/get-collaborator-permission-level
diff --git a/descriptions/ghes-3.12/ghes-3.12.2022-11-28.json b/descriptions/ghes-3.12/ghes-3.12.2022-11-28.json
index 6595610cc9..ce950279f8 100644
--- a/descriptions/ghes-3.12/ghes-3.12.2022-11-28.json
+++ b/descriptions/ghes-3.12/ghes-3.12.2022-11-28.json
@@ -35396,7 +35396,7 @@
     "/repos/{owner}/{repo}/collaborators": {
       "get": {
         "summary": "List repository collaborators",
-        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nOrganization members with write, maintain, or admin privileges on the organization-owned repository can use this endpoint.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have push access to the repository to use this endpoint.\n\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
+        "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\nThe `permissions` hash returned in the response contains the base role permissions of the collaborator. The `role_name` is the highest role assigned to the collaborator after considering all sources of grants, including: repo, teams, organization, and enterprise.\nThere is presently not a way to differentiate between an organization level grant and a repository level grant from this endpoint response.\n\nTeam members will include the members of child teams.\n\nThe authenticated user must have write, maintain, or admin privileges on the repository to use this endpoint. For organization-owned repositories, the authenticated user needs to be a member of the organization.\nOAuth app tokens and personal access tokens (classic) need the `read:org` and `repo` scopes to use this endpoint.",
         "tags": [
           "repos"
         ],
@@ -35634,7 +35634,7 @@
     "/repos/{owner}/{repo}/collaborators/{username}/permission": {
       "get": {
         "summary": "Get repository permissions for a user",
-        "description": "Checks the repository permission of a collaborator. The possible repository\npermissions are `admin`, `write`, `read`, and `none`.\n\n*Note*: The `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role assigned to the\ncollaborator, see the `role_name` attribute, which will provide the full role name, including custom roles. The\n`permissions` hash can also be used to determine which base level of access the collaborator has to the repository.",
+        "description": "Checks the repository permission and role of a collaborator.\n\nThe `permission` attribute provides the legacy base roles of `admin`, `write`, `read`, and `none`, where the\n`maintain` role is mapped to `write` and the `triage` role is mapped to `read`.\nThe `role{"code":"internal","msg":"git-diff-tree: context deadline exceeded","meta":{"cause":"*fmt.wrapError"}}