# SailPoint GitHub Enterprise Server Connector

> GitHub Enterprise Server Connector Documentation

# Documentation

# Connecting SailPoint and GitHub Enterprise Server

To connect SailPoint with GitHub Enterprise Server, perform the following tasks:

## Adding the Source in SailPoint

To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs.

> [!IMPORTANT]
>
> By default, the provisioning feature is **disabled**, and the connector only supports read-only operations. To support provisioning operations, you must manually enable the feature in the source configuration.

**To configure a new source:**

1. Sign in to SailPoint.
2. Go to **Admin \> Connections \> Sources**.
3. Select **Create New**.
4. Search for the connector by entering the name in the search box, and then select **Actions**.
5. In the **Actions** dropdown list, select the setup method:

   - [**Express Setup**](<#configuring-a-source-using-express-setup>) - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started.

     > **Note**
     >
     > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>). For more information, contact your SailPoint Customer Service Manager.
   - [**Standard Setup**](<#configuring-a-source-using-standard-setup>) - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

### Configuring a Source Using Express Setup

Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data.

1. Review the directions and select **Start Express Setup**.
2. Review the pre-populated **Source Name**, **Source Owner**, and **Description**. To update, select **Edit**.

   > **Note**
   >
   > The source name must be unique. You can change these settings later in the source configuration.
3. Select **Virtual Appliance**. A virtual appliance is a Linux-based virtual machine that connects to your sources and apps using SailPoint APIs, connectors, and integrations. For more information about configuring and deploying virtual appliances, refer to [SailPoint Virtual Appliances](<https://documentation.sailpoint.com/saas/help/va/index.html>).
4. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider.

   > **Note**
   >
   > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>).
5. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** section.
6. Select **Finish**.

   After a successful test connection, the system creates your source and prompts you to run an aggregation.

   - If you want to aggregate now, select **Aggregate**.

     - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**.
     - To see the list of aggregated source accounts, go to **Account Management \> Accounts**.
   - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet.

### Configuring a Source Using Standard Setup

Use Standard Setup to configure the connector for full feature support.

1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters.
3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](<https://documentation.sailpoint.com/saas/help/sources/index.html#assigning-a-source-owner>).
4. Under **Connection Type**, select **Direct Connection** or **Flat File**.

   - **Direct Connection** - A direct connection fetches data from the **Virtual Appliance Cluster** you choose as the application connector for the source. A direct connection configuration allows for real-time updates. For more information about configuring and deploying virtual appliances, refer to the [Virtual Appliance Reference Guide](<https://documentation.sailpoint.com/saas/help/va/index.html>).
   - **Flat File** - Select the flat file if no connector is available, or if another system restricts the connection. This option allows only reading and aggregating data as a generic/delimited application. Provisioning activity is unsupported, and additional configuration pages like connection settings and aggregation settings are unavailable.
5. If you selected **Direct Connection**, in **Virtual Appliance Cluster**, select the virtual appliance cluster that will be used as the application connector for the source.
6. (Optional) Select a governance group to grant its members [source](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#source-sub-admin-user-level>) or [role](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#role-sub-admin-user-level>) sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html>).
7. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](<https://documentation.sailpoint.com/saas/help/setup/identity_profiles.html>).
8. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Continue to configure your connected source there.

## Base Configuration

Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary.

1. Enter a unique name and description for the source.
2. In the **Source Owner** dropdown list, select the identity that owns this source.

   - To find a source owner, begin entering their name.
3. In the **Virtual Appliance Cluster** dropdown list, select the virtual appliance to use when communicating with your organization's systems. For more information, refer to [SailPoint Virtual Appliances](<https://documentation.sailpoint.com/saas/help/va/index.html>).
4. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider.

   > **Note**
   >
   > To add a credential provider, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>).
5. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information.
6. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to [Associating Governance Groups with a Source](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html#associating-a-governance-group-with-a-source>).
7. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default.

   - **Enable Provisioning** - Set the toggle to **Enabled** to allow the source to create, update, and deactivate accounts in the connected source system.
   - **Disable Provisioning** - Set the toggle to **Disabled** to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source.
8. Select **Save**.

## Connection Settings

Enter the following values to connect to your GitHub Enterprise Server instance:

> [!NOTE]
>
> **Screenshot**
>
> [![Connection Settings page with the Host, GitHub App ID, and Private Key fields](<https://documentation.sailpoint.com/connectors/github_enterprise_server/va/help/img/connection_settings.png>)](<https://documentation.sailpoint.com/connectors/github_enterprise_server/va/help/img/connection_settings.png>)

1. In **Host**, enter the base URL of your GitHub Enterprise Server appliance, such as `https://github.contoso.com`. Do not include a path.
2. In **GitHub App ID**, enter the numeric App ID from the GitHub App settings page on your GitHub Enterprise Server instance.
3. In **Private Key**, paste the PEM-encoded private key for the GitHub App. Include the BEGIN and END lines.
4. Select **Save**.

## Aggregation Settings

Configure the following settings for account and entitlement aggregation:

> [!NOTE]
>
> **Screenshot**
>
> [![Aggregation Settings page with the Aggregate Outside Collaborators checkbox and the Page Size field](<https://documentation.sailpoint.com/connectors/github_enterprise_server/va/help/img/aggregation_settings.png>)](<https://documentation.sailpoint.com/connectors/github_enterprise_server/va/help/img/aggregation_settings.png>)

1. Select **Aggregate Outside Collaborators** to aggregate outside collaborators and organization members. Outside collaborators can access specific repositories without belonging to the organization. Clear the checkbox to aggregate organization members only.
2. In **Page Size**, enter the number of records to read per request. The maximum and default value is 100.
3. Select **Save**.

When repository aggregation is enabled, the connector includes team-repository access as repository entitlements.

## Review and Test

Perform a test to confirm the connection to SailPoint.

1. Go to **Review and Test**.
2. Confirm that the entries in each field are correct.

   If you note any mistakes, return to the section and make corrections.
3. Select **Test Connection**.

## SailPoint Application Onboarding

SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface.

For more information, refer to [Application Onboarding](<https://documentation.sailpoint.com/saas/help/ai/app_onboarding/index.html>) in the SailPoint SaaS documentation.

# Dataset Management

Dataset Management lets you review the object types a source collects and control how the source aggregates those objects into SailPoint. Use Dataset Management to view and manage resource attributes, datasets and their resources, enable dataset aggregation schedules, perform manual aggregation, and view aggregation history.

> [!NOTE]
>
> Datasets are also available in SailPoint Agentic Fabric. Contact your Customer Success team and refer to [SailPoint Agentic Fabric](<https://documentation.sailpoint.com/saas/help/agentic_fabric/index.html>) for more information.

For more information, refer to [Managing Datasets and Resources](<https://documentation.sailpoint.com/saas/help/sources/datasets.html>) for datasets, resources, owner correlation, and aggregation.

## Datasets

A *dataset* is a named group of one or more related resources that the source aggregates together.

When aggregation runs for a dataset, the source collects all resources in that dataset from the managed system in one aggregation job. Activate or deactivate aggregation at the dataset level, not for individual resources.

> [!NOTE]
>
> Each resource belongs to exactly one dataset for that source. The source defines which resources belong to each dataset. You can enable aggregation and review associated resources, but you cannot create or delete datasets or move resources between them.

### Dataset Aggregation

Configure aggregation on the **Dataset Aggregations** tab for each dataset. Configure each dataset separately. During aggregation, your owner correlation rules are automatically applied to link machine identities to their human owners. For more information, refer to [Configuring Dataset Aggregations](<https://documentation.sailpoint.com/saas/help/sources/datasets.html#configuring-dataset-aggregations>).

## Resources

A resource defines an object type from the managed system. It specifies the kind of object, the attributes the source collects, and how the source identifies and displays each object. Resources form the building blocks of the data model.

In the UI, each resource appears under **Dataset Management** \> **Resources** with its schema. A resource does not run aggregation by itself. The dataset that owns the resource collects it during aggregation.

For more information, refer to [Managing Resources](<https://documentation.sailpoint.com/saas/help/sources/datasets.html#managing-resources>).

### Owner Correlation

Configure owner correlation on each resource to link aggregated objects to human owners. If you do not configure owner correlation, or if the mapping produces no match, an owner is not assigned. For more information, refer to [Configuring Owner Correlation](<https://documentation.sailpoint.com/saas/help/sources/datasets.html#configuring-owner-correlation>).

## Supported Datasets

Go to **Dataset Management \> Datasets** on your GitHub Enterprise Server source to view the datasets the connector aggregates. Select a dataset to review its associated resources and configure aggregation.

> [!NOTE]
>
> Configure aggregation for each dataset separately. For more information, refer to [Dataset Aggregation](<https://documentation.sailpoint.com/saas/help/sources/datasets.html#configuring-dataset-aggregations>).

The connector aggregates each dataset for every in-scope organization and adds `organization` to every row before combining the results.

| Dataset name | Associated resources | Dataset ID |
| --- | --- | --- |
| GitHub App installations | GitHub App Installation | `github:app-installations` |
| GitHub workflows | GitHub Workflow | `github:workflows` |
| GitHub Action runs | GitHub Action Run | `github:actions` |
| GitHub environment secrets | GitHub Environment Secret | `github:secrets` |

The connector aggregates environment secret names only. It does not aggregate secret values.

Workflow, action run, and environment secret datasets require GitHub Actions and blob storage on your GitHub Enterprise Server instance.

## Supported Resources

A resource represents a type of object the connector collects from GitHub Enterprise Server, such as app installations, workflows, action runs, or environment secrets. Each resource defines the attributes the connector collects for that object type and how SailPoint displays each object.

For more information, refer to [Managing Resources](<https://documentation.sailpoint.com/saas/help/sources/datasets.html#managing-resources>).

> [!NOTE]
>
> When you enable dataset aggregation for a selected dataset, all resources in that dataset are collected at once. Activate or deactivate aggregation at the dataset level, not for individual resources.

Go to **Dataset Management** \> **Resources** on your GitHub Enterprise Server source to view each object type the connector aggregates. Select a resource to review its schema on the **Schema** tab.

The connector supports the following organization-qualified resources:

| Resource name | Resource type | Dataset ID |
| --- | --- | --- |
| GitHub App Installation | Account | `github:app-installations` |
| GitHub Workflow | Application | `github:workflows` |
| GitHub Action Run | Application | `github:actions` |
| GitHub Environment Secret | Credential | `github:secrets` |

## GitHub App Installation Attributes

Every row identifies its source organization.

| Attribute | Type | Description |
| --- | --- | --- |
| id | string | Unique identifier of the GitHub App installation. |
| name | string | Application slug associated with the installation. |
| app\_id | string | GitHub App ID. |
| owner | string list | Human GitHub logins associated with the installation. |
| permissions | string list | Installation permissions represented as `scope:access` pairs. |
| repository\_selection | string | Repository access scope for the installation. |
| target\_type | string | Installation target type. |
| created\_at | string | Date and time the installation was created. |
| updated\_at | string | Date and time the installation was last updated. |
| suspended | string | Indicates whether the installation is suspended. |
| suspended\_at | string | Date and time the installation was suspended. |
| organization | string | Organization login associated with this row. |

## GitHub Workflow Attributes

Every row identifies its source organization.

| Attribute | Type | Description |
| --- | --- | --- |
| id | string | Unique workflow identifier. |
| node\_id | string | Global GitHub node identifier. |
| name | string | Workflow name. |
| owner | string list | Human GitHub logins accountable for the workflow file. |
| repository | string | Repository name. |
| repository\_full\_name | string | Repository name in `owner/repo` format. |
| workflow\_id | string | Numeric GitHub workflow identifier. |
| path | string | Workflow file path in the repository. |
| state | string | Current workflow state. |
| html\_url | string | URL of the workflow definition. |
| created\_at | string | Date and time the workflow was created. |
| updated\_at | string | Date and time the workflow was last updated. |
| organization | string | Organization login associated with this row. |

## GitHub Action Run Attributes

Every row identifies its source organization.

| Attribute | Type | Description |
| --- | --- | --- |
| id | string | Unique workflow run identifier. |
| name | string | Workflow run title. |
| node\_id | string | Global GitHub node identifier. |
| status | string | Current workflow run status. |
| head\_branch | string | Branch associated with the run. |
| actor | string | Login of the user who created the run. |
| triggering\_actor | string | Login of the user who triggered the run. |
| event | string | GitHub event that triggered the run. |
| run\_number | string | Sequential workflow counter. |
| workflow\_id | string | Parent workflow identifier. |
| workflow | string | Parent workflow label used for correlation. |
| check\_suite\_id | string | Associated check suite identifier. |
| repository | string | Repository name in `owner/repo` format. |
| owner | string list | Human GitHub logins accountable for the run. |
| created\_at | string | Date and time the run was created. |
| updated\_at | string | Date and time the run was last updated. |
| organization | string | Organization login associated with this row. |

## GitHub Environment Secret Attributes

The connector aggregates secret names and metadata. It does not aggregate secret values.

| Attribute | Type | Description |
| --- | --- | --- |
| id | string | Stable secret identifier in `{owner}/{repo}/environment/{env}/secret/{name}` format. |
| name | string | Secret name. |
| scope | string | Secret scope. |
| organization | string | Organization where the secret is configured. |
| repository | string | Repository name in `owner/repo` format. |
| environment | string | Environment that owns the secret. |
| owner | string | Human GitHub logins accountable for the environment secret. |
| created\_at | string | Date and time the secret was created. |
| updated\_at | string | Date and time the secret was last updated. |

# Integrating SailPoint with GitHub Enterprise Server

This guide provides the requirements and field definitions you need to configure the GitHub Enterprise Server connector.

GitHub Enterprise Server is a self-hosted GitHub product that runs on your infrastructure. The connector aggregates accounts, entitlements, and non-human identities from the organizations governed by your GitHub App.

> [!NOTE]
>
> To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes](<https://community.sailpoint.com/release-notes/saas>) page.

## Supported Features

The GitHub Enterprise Server connector supports the following features:

#### Account Management

- Test connection.
- Account aggregation. The connector merges organization members with the same GitHub `login`.
- Account creation through organization invitations.
- Adding and removing team membership.

#### Entitlement Management

- Team, organization role, and repository entitlement aggregation.
- Access certifications for entitlements connected to accounts.

#### Machine Identity Aggregation

- Dataset 2.0 aggregation for GitHub App installations, workflows, action runs, and environment secret names.

## Supported Versions

The connector supports self-hosted GitHub Enterprise Server 3.21 and later.

## Prerequisites

Before you configure the connector, prepare your virtual appliance and GitHub App.

Configure at least one virtual appliance cluster and successfully test the connection. Refer to the [Virtual Appliance Reference Guide](<https://documentation.sailpoint.com/saas/help/va/index.html>) for more information.

### GitHub App

**To prepare GitHub Enterprise Server:**

1. Confirm that your virtual appliance can reach the hostname of your GitHub Enterprise Server 3.21 or later instance.
2. Create a GitHub App on the GitHub Enterprise Server instance.
3. Set the App installation availability to **Any account**.
4. Grant the permissions listed in [Required Permissions](<#required-permissions>).
5. Install the same App on every organization you want to govern. Use the same App ID and PEM private key.

## Required Permissions

Grant the following permissions to the GitHub App:

### GitHub App Permissions for User Management

| Purpose | GitHub App permission | Level |
| --- | --- | --- |
| Identity management and provisioning | Organization Members | Write |
| Organization invitations and team membership | Administration | Write |

### Permissions Required for Each Resource

| Dataset name | Permission |
| --- | --- |
| **GitHub Apps** | Read permission to Organization - Administrator |
| **GitHub Actions** | Read permission to Repository - Actions |
| **GitHub Workflows** | Read permission to Repository - Actions |
| **Environment Secrets** | Read permission to Repository - Environment |

# Provisioning

The GitHub Enterprise Server connector supports provisioning, allowing you to create and manage accounts and entitlements in GitHub Enterprise Server directly from SailPoint.

**Prerequisite:** Your system is configured for provisioning.

When SailPoint provisions new accounts to the source, it uses the attributes on the **Create Account** page as instructions or a template for what to include in the account. This page is also referred to as the *provisioning policy*.

When new access is granted on a source where a user does not already have an account, SailPoint automatically includes account creation in the provisioning. This applies whether provisioning is started from an access request or from an automated role or lifecycle state assignment.

For direct-connect sources, SailPoint automatically creates the account from this configuration. If the source is not configured as a direct-connect source, SailPoint creates and assigns a provisioning task to the source owner and includes the values for the source owner to use in manually creating the account.

> [!IMPORTANT]
>
> This section describes the default **Create Account** configuration. SailPoint recommends that you work with Services to define a provisioning configuration specific to your company's needs. Be sure to verify large changes to the provisioning policy before implementation. Failure to do so might cause provisioning to fail.

## Default Create Account Attributes

| Account Attribute | Generator | Description |
| --- | --- | --- |
| login | Identity attribute - uid | The GitHub username. |
| role | Static `direct_member` | Invitation role. Supported values are `direct_member`, `admin`, and `billing_manager`. |
| organization | Required for GitHub Enterprise Server | Target organization login. |
| teams | Entitlement | Optional team IDs or slugs for the target organization. |

> [!IMPORTANT]
>
> The provisioning plan must include the target organization. The connector can also parse the organization from a team entitlement in `org/slug` format. Provisioning fails without a target organization.

## Provisioning Accounts

1. Configure the Create Account mappings, including the target organization.
2. Submit the provisioning request. The connector sends an organization invitation with `POST /orgs/{org}/invitations`.
3. Ask the user to accept the invitation. GitHub typically allows 7 days for acceptance.
4. Run account aggregation after acceptance so the connector can aggregate the organization member.

## Updating Team Membership

The connector uses the team native identity in `org/slug` format.

- Add membership - `PUT /orgs/{org}/teams/{team_slug}/memberships/{username}` with `{"role":"member"}`.
- Remove membership - `DELETE /orgs/{org}/teams/{team_slug}/memberships/{username}`.

# Schema Reference

The application schema is used to configure the objects returned from a connector.

> [!NOTE]
>
> - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.
> - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified.

The GitHub Enterprise Server connector uses the following default correlation and object configurations.

The connector aggregates organization members as accounts. It merges records with the same GitHub login across governed organizations.

The connector aggregates teams, organization roles, and repository access as entitlements.

## Default Correlation Configuration

Before you aggregate accounts from this source, you can map account attributes with their corresponding identity attributes based on your requirements.

You can customize the correlation configuration. Refer to [Assigning Source Accounts to Identities](<https://documentation.sailpoint.com/saas/help/accounts/correlation.html>) for more information.

When you first create the GitHub Enterprise Server source, the default correlation mapping is:

Map account attributes to identity attributes before you aggregate accounts. Profile email is often empty on GitHub Enterprise Server. The login value is the stable native identity.

| Account Attribute | Operation | Identity Attribute |
| --- | --- | --- |
| email | Equals | email |
| name | Equals | name |

## Default Account Schema

Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.

The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.

### Default Account Attributes

The GitHub Enterprise Server connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.

The identity and display attribute is `login`. The group attribute is `teams`.

Go to **Admin** \> **Connections** \> **Sources**, open your GitHub Enterprise Server source, and select **Account Schema** to review the live schema.

| Attribute | Type | Description |
| --- | --- | --- |
| databaseId | string | Primary key from the GitHub database. |
| login | string | Username used to sign in. |
| name | string | Public profile name. |
| id | string | GitHub global node ID. |
| email | string | Publicly visible profile email. |
| organizationVerifiedDomainEmails | string list | Verified emails matching organization-verified domains. This value is often empty on GitHub Enterprise Server. |
| twitterUsername | string | Twitter username. |
| url | string | Public profile URL. |
| bio | string | Public profile bio. |
| bioHTML | string | Public profile bio as HTML. |
| location | string | Public profile location. |
| company | string | Public profile company. |
| companyHTML | string | Public profile company as HTML. |
| isBountyHunter | boolean | Indicates GitHub Security Bug Bounty participation. |
| isHireable | boolean | Indicates whether the user is marked as available for hire. |
| isEmployee | boolean | Indicates whether the user is a GitHub employee. |
| isSiteAdmin | boolean | Indicates whether the user is a site administrator. |
| isGitHubStar | boolean | Indicates GitHub Stars Program membership. This value is often empty on GitHub Enterprise Server. |
| isViewer | boolean | Indicates whether the user is the viewing user. |
| isCampusExpert | boolean | Indicates GitHub Campus Experts participation. |
| isDeveloperProgramMember | boolean | Indicates GitHub Developer Program membership. |
| hasSponsorsListing | boolean | Indicates whether the user has a GitHub Sponsors listing. This value is often empty on GitHub Enterprise Server. |
| followers | int | Number of followers. |
| following | int | Number of users followed. |
| gists | int | Number of gists created. |
| repositories | int | Number of repositories owned. |
| watching | int | Number of repositories watched. |
| estimatedNextSponsorsPayoutInCents | int | Estimated next Sponsors payout in US cents. |
| monthlyEstimatedSponsorsIncomeInCents | int | Estimated monthly Sponsors income in US cents. |
| websiteUrl | string | Public website URL. |
| createdAt | string | Date and time the user was created. |
| updatedAt | string | Date and time the user was last updated. |
| samlNameId | string | SAML name ID. |
| organizations | string list | In-scope organization logins for the user. |
| teams | string list, entitlement, writable | Team memberships in `{org}/{slug}` format. |
| role | string list, entitlement, writable | Organization roles in `{org}:ADMIN` or `{org}:MEMBER` format. |
| repositoryIDs | string list, entitlement | Repositories the user can access. |

## Default Entitlement Attributes

Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to [Managing Entitlements](<https://documentation.sailpoint.com/saas/help/access/entitlements.html>) for more information.

> [!CAUTION]
>
> Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations.

The connector supports team, organization role, and repository entitlements.

### Default Group Attributes

The GitHub Enterprise Server connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups.

Groups represent teams. The identity attribute is `combinedSlug` in `org/slug` format. The display attribute is `name`.

Go to **Admin** \> **Connections** \> **Sources**, open your GitHub Enterprise Server source, and select **Entitlement Schema** to review the live schema.

| Attribute | Type | Description |
| --- | --- | --- |
| databaseId | string | Primary key from the database. |
| slug | string | Team slug in the organization. |
| name | string | Team display name. |
| id | string | GitHub global node ID. |
| description | string | Team description. |
| privacy | string | Team privacy level. |
| combinedSlug | string | Organization and team slug in `org/slug` format. |
| url | string | Team page URL. |
| members | int | Number of team members. |
| repositories | int | Number of repositories associated with the team. |
| parentTeam | string | Parent team. |
| createdAt | string | Date and time the team was created. |
| updatedAt | string | Date and time the team was last updated. |
| repositoryNames | string list | Repositories the team can access. |
| organization | string | Organization login. |

### Default Role Attributes

The GitHub Enterprise Server connector supports roles. The following attributes must be configured on the managed system and in the SailPoint source schema to manage roles.

The identity attribute is `id` in `{org}:ADMIN` or `{org}:MEMBER` format. The display attribute is `name`.

The connector does not use global Cloud role identities `1` and `2` when multiple organizations are in scope.

Go to **Admin** \> **Connections** \> **Sources**, open your GitHub Enterprise Server source, and select **Entitlement Schema** to review the live schema.

| Attribute | Type | Description |
| --- | --- | --- |
| id | string | Organization-qualified role in `{org}:ADMIN` or `{org}:MEMBER` format. |
| name | string | `ADMIN` or `MEMBER`. |
| organization | string | Organization login. |

### Default Repository Attributes

The identity attribute is the instance-unique `id`. The display attribute is `name`. Repository entitlements include `permission`.

Go to **Admin** \> **Connections** \> **Sources**, open your GitHub Enterprise Server source, and select **Entitlement Schema** to review the live schema.

| Attribute | Type | Description |
| --- | --- | --- |
| id | string | Primary key from the database. |
| name | string | Repository name. |
| permission | string | Permission on the repository. |
| visibility | string | Repository visibility. |
| organization | string | Organization login. |