Skip to content

Managing Datasets and Resources

You can use datasets to aggregate and govern AI agents and other non-human identities such as MCP servers, credentials, and IAM roles. Datasets group one or more resources on a single aggregation schedule. A resource defines the object type from the managed system, the attributes the source collects, and how the source identifies and displays each object. When a dataset is aggregated, the source collects all resources in that dataset from the managed system.

Managing Datasets

You can view the out-of-the-box datasets and resources for a supported connector in the source's configuration. You can configure an aggregation schedule for datasets and their resource objects or perform manual aggregations as needed.

Supported Connectors

The following connectors include default datasets and resources. Refer to the appropriate connector guide for more information.

Anthropic Claude Enterprise Argo CD SaaS AWS SaaS
Cursor SaaS Databricks SaaS Google Workspace SaaS
JDBC SaaS Jenkins Microsoft Entra SaaS
N8N Salesforce SaaS ServiceNow Identity Governance SaaS
Snowflake SaaS Web Services SaaS Wiz

Configuring Dataset Aggregations

  1. Go to Admin > Connections > Sources.

  2. Create or select an existing source.

  3. In the Dataset Management section, select Datasets.

  4. Select the dataset you want to configure.

  5. Select the Dataset Aggregations tab.

  6. To enable scheduled aggregations, select the Enable Schedule checkbox in the Schedule Aggregations section.

  7. To run a single aggregation, select Start Aggregation in the Manual Aggregation section.

After an aggregation has started, you can view its progress in the Latest Aggregation section.

Managing Resources

You can update a resource by editing its schema or owner correlation. You can also remove a resource from a dataset as needed.

Updating Resource Schemas

You can update a resource's schema by adding, editing, or deleting its attributes.

Adding Attributes

  1. Go to Admin > Connections > Sources.

  2. Select the source you want to configure.

  3. In the Dataset Management section, select Resources.

  4. Select the resource you want to update.

  5. In the Schema tab, select + Add Attribute.

  6. Enter a unique name and description for the attribute.

    Notes

    • The attribute's name should exactly match the attribute name in the source system.
    • Attribute names cannot exceed 128 characters.
  7. To configure this attribute to support multiple values, select the Multi-Valued checkbox.

  8. Select the Designate this attribute as the Resource ID attribute checkbox to designate this attribute as the Resource ID.

  9. Select the Designate this attribute as the Resource Name attribute checkbox to designate this attribute as the Resource Name.

    Warning

    If the Resource ID and Resource Name attributes require changes, it is strongly recommended to do so before an aggregation is performed. After an aggregation has run, editing these attributes can result in duplicate non-human identities and other serious issues.

  10. From the Type dropdown list, select the type of value this attribute will contain.

  11. Select Save to add the attribute to the schema.

  12. Repeat the above steps for each attribute you want to add.

Updating Attributes

  1. Go to Admin > Connections > Sources.

  2. Select the source you want to configure.

  3. In the Dataset Management section, select Resources.

  4. Select the resource you want to update.

  5. In the Schema tab, find the attribute you want to update and select the edit icon from the Actions columns.

  6. Make changes as needed.

  7. Select Save to update the attribute.

Deleting Attributes

You can delete custom attributes from a resource schema.

  1. Go to Admin > Connections > Sources.

  2. Select the source you want to configure.

  3. In the Dataset Management section, select Resources.

  4. Select the resource you want to update.

  5. In the Schema tab, find the custom attribute you want to remove and select the delete icon from the Actions columns.

  6. Confirm the deletion.

Configuring Owner Correlation

You can configure owner correlation for each resource. The matching human identity will become responsible for managing and reviewing aggregated non-human identities.

Note

If owner correlation is not configured or the mapping results in no match, no owner is assigned.

To configure owner correlation:

  1. Go to Admin > Connections > Sources.

  2. Select the source you want to configure.

  3. In the Dataset Management section, select Resources.

  4. Select the resource you want to configure owner correlation for.

  5. Select the Owner Correlation tab.

  6. In the Primary Correlation section, choose a method to identify the human identity responsible for managing and reviewing non-human identities for this resource:

    • Select + Add Criteria if no criteria row is present.

    • Set the Attribute Type to Human Identity or Account.

    • In the Schema Attribute field, select the resource schema attribute to use in the match.

    • (Optional) In the Transform field, select a transform to apply to the schema attribute value before matching.

    • Complete the target attribute for the attribute type you selected:

      • When Human Identity is selected, search for and select a value in Human Identity Attribute.

      • When Account is selected, search for and select a value in Account Attribute.

        Tip

        Define correlation criteria using attributes that reliably identify the owner in your environment, such as email or employee ID mapped to a human identity attribute.

  7. (Optional) Select Sync to Machine Accounts to apply the primary owner mapping to machine accounts when supported for the resource.

  8. (Optional) Select + Add Criteria to add more mapping rules. Drag a criteria row to change evaluation order or select the delete icon to remove a criteria row.

  9. Configure additional owners as needed. You can use criteria to define the human identity responsible for these non-human identities or select a governance group.

  10. Select Save to save these configurations.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.