> ## Documentation Index
> Fetch the complete documentation index at: https://bloodhound.specterops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# GH_HasPersonalAccessTokenRequest

> User has a pending personal access token request for the organization

<img noZoom src="https://mintcdn.com/specterops/tTIczgde9H07oLXf/assets/enterprise-AND-community-edition-pill-tag.svg?fit=max&auto=format&n=tTIczgde9H07oLXf&q=85&s=ad49a576589f4d2a8081df77d07fdf56" alt="Applies to BloodHound Enterprise and CE" width="482" height="45" data-path="assets/enterprise-AND-community-edition-pill-tag.svg" />

## Edge Schema

* Source: [GH\_User](/opengraph/extensions/github/nodes/gh_user)
* Destination: [GH\_PersonalAccessTokenRequest](/opengraph/extensions/github/nodes/gh_personalaccesstokenrequest)
* Traversable: ❌

## General Information

The non-traversable GH\_HasPersonalAccessTokenRequest edge represents the relationship between a user and their pending personal access token requests awaiting organizational approval. This edge links each pending token request back to the user who submitted it. Pending token requests are security-relevant because they represent access that may soon be granted, and reviewing them helps administrators understand what permissions users are requesting before approval. Organizations that require approval for fine-grained PATs will have these requests queued until an administrator acts on them.

```mermaid theme={null}
graph LR
    node1("GH_User alice")
    node2("GH_PersonalAccessTokenRequest deploy-request")
    node3("GH_User bob")
    node4("GH_PersonalAccessTokenRequest admin-access-request")
    node1 -- GH_HasPersonalAccessTokenRequest --> node2
    node3 -- GH_HasPersonalAccessTokenRequest --> node4
```