# 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]() for more information. For more information, refer to [Managing Datasets and Resources]() 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](). ## 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](). ### 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](). ## Supported Datasets Go to **Dataset Management \> Datasets** on your Supabase 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](). > [!NOTE] > > These resources do not define owner correlation. The API key and secret list endpoints do not support pagination. Each API key is identified by `id` and displayed by `name`. Each secret is identified and displayed by `name`. | Dataset name | Associated resources | Dataset ID | Aggregation schedule | | --- | --- | --- | --- | | **API Key** | API Key | `supabase:api-key` | Every 12 hours (`0 */12 * * *`) | | **Secret** | Secret | `supabase:secret` | Every 12 hours (`0 */12 * * *`) | For resource schema attributes, refer to [Supported Resources](<#supported-resources>), [API Key Attributes](<#api-key-attributes>), and [Secret Attributes](<#secret-attributes>). ### Dataset Aggregations Dataset aggregation collects resource objects from the managed system and loads them into SailPoint. Repeat the configuration for each dataset on the source. ### Configuring Dataset Aggregation To configure dataset aggregation for a dataset: 1. Go to **Admin \> Connections \> Sources**, and open your source. 2. Go to **Dataset Management \> Datasets**. 3. Select the dataset you want to configure. 4. Select the **Dataset Aggregations** tab. On the **Dataset Aggregations** tab, configure how resource objects from the selected dataset are aggregated into SailPoint. The tab contains **Scheduled Aggregations**, **Manual Aggregation**, and **Latest Aggregation**. #### Scheduled Aggregations Scheduled aggregations run on a schedule to keep the dataset synchronized with the managed system. 1. On the **Dataset Aggregations** tab, select **Enable Schedule** to turn on scheduled aggregations. When scheduled aggregations are enabled, SailPoint aggregates all resource objects in the dataset on the configured schedule. #### Manual Aggregation Manual aggregation runs once and collects all resource objects in the dataset. 1. On the **Dataset Aggregations** tab, select **Start Aggregation**. SailPoint starts the aggregation immediately. When the run completes, results appear in the **Latest Aggregation** section. #### Viewing Aggregation Results After an aggregation completes, review its status in the **Latest Aggregation** section on the **Dataset Aggregations** tab. The **Latest Aggregation** section shows: - **Start Time** - when the aggregation started - **Resource Objects Scanned** - the number of resource objects the aggregation processed - **Status** - whether the aggregation succeeded or failed Select **Details** to view additional information about the most recent run. To view prior runs, select **Aggregation History**. ## Supported Resources For more information, refer to [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. Under **Dataset Management** \> **Resources**, the Supabase source lists each object type that is aggregated. Select a resource to review its schema on the **Schema** tab. | Resource name | Resource type | Resource ID | Identity attribute | Display attribute | | --- | --- | --- | --- | --- | | **API Key** | `std:credential` | `supabase:api-key` | `id` | `name` | | **Secret** | `std:credential` | `supabase:secret` | `name` | `name` | For the complete resource schemas, refer to [API Key Attributes](<#api-key-attributes>) and [Secret Attributes](<#secret-attributes>). ### Owner Correlation These resources do not define owner correlation. For more information, refer to [Owner Correlation](). ## API Key Attributes Use the following schema attributes for the **API Key** resource in the **API Key** dataset. A project API key is a stored credential that an application or service presents when it calls the project. > [!NOTE] > > Do not map `api_key` or `prefix`. Call without `reveal=true`. Endpoint does not support pagination. | Attribute Name | Description | | --- | --- | | id | Unique identifier of the API key. Resource ID. A legacy key uses anon or service\_role. A publishable or secret key uses a UUID. | | name | Display name of the key. Display attribute. | | type | Key kind: legacy, publishable, or secret. | | description | Text set on the key. Null when none was set. | | hash | Hash of the key value. This is not the key itself. | | secret\_jwt\_template.role | Postgres role embedded in a secret key, usually service\_role. Null on a publishable key. Absent on a legacy key. | | inserted\_at | Time the key was created. Present on publishable and secret keys. | | updated\_at | Time the key was last changed. Present on publishable and secret keys. | ## Secret Attributes Use the following schema attributes for the **Secret** resource in the **Secret** dataset. An Edge Function secret is a stored name and value that a function reads with no person present. > [!NOTE] > > Do not map `value`. Endpoint does not support pagination. | Attribute Name | Description | | --- | --- | | name | Name of the secret. Resource ID and display attribute. There is no separate id. | | updated\_at | Time the secret was last changed. |