# 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 Buildkite 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>).

| Dataset Name | Associated Resource | Dataset ID | Default Schedule |
| --- | --- | --- | --- |
| Buildkite Agent Tokens | Buildkite Agent Token | `buildkite:agent-tokens` | 1:30 AM and 1:30 PM UTC |
| Buildkite Secrets | Buildkite Secret | `buildkite:secrets` | 3:00 AM and 3:00 PM UTC |
| Buildkite Package Registries | Buildkite Registry Token | `buildkite:registries` | 9:00 AM and 9:00 PM UTC |

The connector staggers the schedules to reduce simultaneous demand on shared Buildkite rate limits. Manually started or long-running aggregations can overlap.

## Supported Resources

Resource schemas appear under **Dataset Management** \> **Resources**. The connector-specific attributes are read-only.

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.

| Resource Name | Resource Type | Resource ID |
| --- | --- | --- |
| [Buildkite Agent Token](<#buildkite-agent-token-attributes>) | Credential | `buildkite:agent-token` |
| [Buildkite Secret](<#buildkite-secret-attributes>) | Credential | `buildkite:secret` |
| [Buildkite Registry Token](<#buildkite-registry-token-attributes>) | Credential | `buildkite:registry-token` |

## Owner Correlation

The connector maps each resource's `created_by_id` attribute to the `id` of an aggregated Buildkite account. When Buildkite does not return creator information, the credential is aggregated without an owner.

## Buildkite Agent Token Attributes

Schema attributes for the **Buildkite Agent Token** resource (`buildkite:agent-token`). The identity attribute is `id`, and the display attribute is `name`.

| Attribute Name | Description | Type | Multi-Valued |
| --- | --- | --- | --- |
| `allowed_ip_addresses` | CIDR allowlist. Empty when access is unrestricted. | string | Yes |
| `cluster_id` | ID of the cluster this token registers agents into. | string | No |
| `cluster_name` | Display name of the cluster this token registers agents into. | string | No |
| `created_at` | Date and time the token was created. | string | No |
| `created_by_id` | UUID of the user who created the token. Used for owner correlation. | string | No |
| `expired` | Whether the token has expired. The value is true or false. | string | No |
| `expires_at` | Date and time the token expires. Empty when the token does not expire. | string | No |
| `id` | Agent token UUID. | string | No |
| `name` | Token description. Buildkite agent tokens have no name field. | string | No |
| `owner` | Display name of the user who created the token. | string | Yes |

## Buildkite Secret Attributes

Schema attributes for the **Buildkite Secret** resource (`buildkite:secret`). The identity attribute is `id`, and the display attribute is `name`.

| Attribute Name | Description | Type | Multi-Valued |
| --- | --- | --- | --- |
| `cluster_id` | ID of the cluster this secret belongs to. | string | No |
| `cluster_name` | Display name of the cluster this secret belongs to. | string | No |
| `created_at` | Date and time the secret was created. | string | No |
| `created_by_id` | UUID of the user who created the secret. Used for owner correlation. | string | No |
| `description` | Description of the secret. | string | No |
| `id` | Secret UUID. | string | No |
| `last_read_at` | Date and time a build last read this secret. Empty if no build has read it. | string | No |
| `name` | Environment variable name a build uses to read this secret. | string | No |
| `never_read` | Whether a build has never read this secret. The value is true or false. | string | No |
| `owner` | Display names of the users who created and last updated the secret. | string | Yes |
| `policy` | YAML access policy that names which pipelines may read this secret. | string | No |
| `updated_at` | Date and time the secret was last updated. | string | No |
| `updated_by_id` | UUID of the user who last updated the secret. This is not used for owner correlation. | string | No |

## Buildkite Registry Token Attributes

Schema attributes for the **Buildkite Registry Token** resource (`buildkite:registry-token`). The identity attribute is `id`, and the display attribute is `name`.

| Attribute Name | Description | Type | Multi-Valued |
| --- | --- | --- | --- |
| `created_at` | Date and time the token was created. | string | No |
| `created_by_id` | UUID of the user who created the token. Used for owner correlation. | string | No |
| `id` | Registry token UUID. | string | No |
| `name` | Token description. Buildkite registry tokens have no name field. | string | No |
| `owner` | Display name of the user who created the token. | string | Yes |
| `registry_id` | ID of the registry this token can read. | string | No |
| `registry_slug` | Slug of the registry this token can read. | string | No |

> [!NOTE]
>
> Buildkite registry tokens do not include an expiration date.
