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 OpenRouter 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. Each API key is identified by hash and displayed by name. Each credential provider is identified by id and displayed by name. When a name is empty, the masked label is used as the display name.
| Dataset name | Associated resources | Dataset ID | Aggregation schedule |
|---|---|---|---|
| API Keys | API Key | openrouter:api-key |
Every 12 hours (0 */12 * * *) |
| Credential Providers | Credential Provider | openrouter:credential-provider |
Every 12 hours (0 */12 * * *) |
For resource schema attributes, refer to Supported Resources, API Key Attributes, and Credential Provider 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:
- Go to Admin > Connections > Sources, and open your source.
- Go to Dataset Management > Datasets.
- Select the dataset you want to configure.
-
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.
- 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.
- 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 OpenRouter 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 |
openrouter:api-key |
hash |
name |
| Credential Provider | std:credential |
openrouter:credential-provider |
id |
name |
For the complete resource schemas, refer to API Key Attributes and Credential Provider 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 Keys dataset. An OpenRouter API key is a credential that an application uses to call OpenRouter.
Note
The raw API key secret is not available from the list response and is not stored.
| Attribute Name | Description |
|---|---|
| hash | Hash of the API key. Resource ID. The raw API key secret is not available from the list response and is not stored. |
| name | Name of the API key. Display attribute. When the name is empty, the label is shown instead. |
| label | Masked label for the API key. |
| creator_user_id | User identifier of the member who created the key. |
| workspace_id | Workspace that owns the key. |
| disabled | Whether the key is disabled. |
| expires_at | Date and time when the key expires. |
| created_at | Date and time when the key was created. |
| updated_at | Date and time when the key was last updated. |
| last_used_at | Date and time when the key was last used. |
| limit | Spend limit configured on the key. |
| limit_remaining | Remaining spend on the key. |
Credential Provider Attributes
Use the following schema attributes for the Credential Provider resource in the Credential Providers dataset. A credential provider is a bring-your-own-key (BYOK) credential that OpenRouter uses to call an upstream provider, such as OpenAI or Anthropic.
Note
The raw provider key is write-only. It is not returned by the list response and is not stored.
| Attribute Name | Description |
|---|---|
| id | Unique identifier of the credential provider. Resource ID. The raw provider key is write-only. It is not returned by the list response and is not stored. |
| name | Name of the credential provider. Display attribute. When the name is empty, the label is shown instead. |
| label | Masked label for the provider credential. |
| provider | Upstream provider this credential authenticates, such as openai or anthropic. |
| workspace_id | Workspace that owns the credential. |
| disabled | Whether the credential is disabled. |
| created_at | Date and time when the credential was created. |
| is_byok_only | Whether requests for this provider run only on your own keys. |
| is_fallback | Whether OpenRouter uses this credential only after its shared endpoints have been tried. |
| is_required | Whether requests for the models this credential applies to must use this key. |
| declared_region | Data region declared for the upstream provider account. |
| declared_zdr | Whether the upstream provider account is declared to have zero data retention. |
| sort_order | Priority order of the credential among the credentials for that provider. |