> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/github-users.md). # GitHub users You can view personal details and event data for all your internal and external GitHub users: * [Internal users](#github-internal-users) - Users who belong to your organization's GitHub platform and operate within the organization domains or subdomains. * [External users](#github-external-users) - Users who are outside your organization, but have access to your GitHub files. ## Locate a GitHub user To view personal details and event data for a specific internal or external user in GitHub: 1. From the DoControl side menu, click **Inventory** > **Users**. 2. Select **GitHub**.

3. Select **Internal** or **External**.

4. Filter for a specific user. 5. Click the user name to open the user details. ## GitHub internal users All internal users in your GitHub platform are displayed with these parameters:

Internal user parameter	Description
User	Internal user name. Click the user name to open the internal user details with event data.
First name	Internal user's given name
Last name	Internal user's surname
Role	Indication if the user is a GutHub admin or member
Created on	Date when the user was created in GitHub
Last active	Date when the user was updated in GitHub

{% hint style="success" %} Click **Export to CSV**

to download a consolidated report of internal GitHub users in CSV format. {% endhint %} ## GitHub external users All external users in your GitHub platform are displayed with these parameters:

External user parameter	Description
User	External user name. Click the user name to open the external user details with event data.
First name	External user's given name
Last name	External user's surname
Role	Indication if the user is a GutHub admin or member
Created on	Date when the user was created in GitHub
Last active	Date when the user was updated in GitHub

{% hint style="success" %} Click **Export to CSV**

to download a consolidated report of external GitHub users in CSV format. {% endhint %} ## Events DoControl monitors real-time events of user activities in GitHub for internal and external users. If no date range is selected, events are displayed from the last 30 days. #### To view events for a specific internal or external user: 1. From the DoControl side menu, click **Inventory** > **Users**. 2. Select **GitHub**. 3. Select **Internal** or **External**. 4. Filter for a specific user. 5. Click the user name to open the internal user details. 6. Scroll down to view metadata for the user's events in GitHub.

The metadata displayed for a user's events in GitHub includes these parameters:

Event parameter	Description
Date and time	When the event occurred
Actor	The user who triggered the event
Target	The user whom the actor shared data with
App	App involved in the event: GitHub
Asset	Branch name in GitHub
Event type	Type of event as defined in GitHub (Push, etc)
Triggered	Number of workflows or alerts that were triggered by this event
Event ID	Unique identifier for the event
Event JSON	Click to open the JSON file with raw details about the event

{% hint style="success" %} Click **Export to CSV**

to download a consolidated report of event metadata for a specific GitHub user. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.docontrol.io/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/github-users.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.