Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,60 @@
---
id: ciem-auto-include-scope-setting-changed
title: CIEM Auto-Include Scope Setting Changed
pagination_label: CIEM Auto-Include Scope Setting Changed
sidebar_label: CIEM Auto-Include Scope Setting Changed
sidebar_class_name: ciemAutoIncludeScopeSettingChanged
keywords: ['event', 'trigger', 'ciem', 'scope', 'auto-include', 'setting', 'available']
description: Fires after a user enables or disables the Auto-Include Scope setting for a CIEM source.
slug: /extensibility/event-triggers/triggers/ciem-auto-include-scope-setting-changed
tags: ['Event Triggers', 'Available Event Triggers', 'Fire and Forget']
---

## Event Context

A user has disabled or enabled the Auto-Include Scope functionality for a source. When auto-include scope is disabled, SailPoint CIEM will not check for newly added AWS accounts, Azure subscriptions, or GCP projects.

You can use a JSONPath filter expression to narrow down the circumstances under which your workflow will be triggered.

This trigger only fires if you have the CIEM service.

This is an example input from this trigger:

```json
{
"$ref": "#/definitions/record:AutoIncludeScopeSettingChanged",
"definitions": {
"record:AutoIncludeScopeSettingChanged": {
"additionalProperties": true,
"properties": {
"event": {
"type": "string"
},
"identityDisplayName": {
"type": "string"
},
"identityId": {
"type": "string"
},
"sourceIscId": {
"type": "string"
},
"sourceName": {
"type": "string"
},
"sourceNativeId": {
"type": "string"
},
"timestamp": {
"type": "string"
}
},
"type": "object"
}
}
}
```

## Additional Information and Links

- **Trigger Type**: [FIRE_AND_FORGET](../trigger-types.md#fire-and-forget)
Original file line number Diff line number Diff line change
@@ -0,0 +1,86 @@
---
id: ciem-new-scope-detected
title: CIEM New Scope Detected
pagination_label: CIEM New Scope Detected
sidebar_label: CIEM New Scope Detected
sidebar_class_name: ciemNewScopeDetected
keywords: ['event', 'trigger', 'ciem', 'scope', 'detected', 'available']
description: Fires after a new AWS account, Azure subscription, or GCP project is detected by SailPoint CIEM.
slug: /extensibility/event-triggers/triggers/ciem-new-scope-detected
tags: ['Event Triggers', 'Available Event Triggers', 'Fire and Forget']
---

## Event Context

A new AWS account, Azure subscription, or GCP project was detected by SailPoint CIEM.

You can use a JSONPath filter expression to narrow down the circumstances under which your workflow will be triggered.

This trigger only fires if you have the CIEM service.

This is an example input from this trigger:

```json
{
"$ref": "#/definitions/record:NewScopeDetected",
"definitions": {
"record:NewScopeDetected": {
"additionalProperties": true,
"properties": {
"event": {
"type": "string"
},
"org": {
"type": "string"
},
"scopesDiscovered": {
"items": {
"$ref": "#/definitions/record:Scope"
},
"type": "array"
},
"scopesEnabled": {
"type": "boolean"
},
"sourceIscId": {
"type": "string"
},
"sourceName": {
"type": "string"
},
"sourceNativeId": {
"type": "string"
},
"timestamp": {
"type": "string"
},
"total": {
"minimum": 1,
"type": "integer"
},
"truncated": {
"type": "boolean"
}
},
"type": "object"
},
"record:Scope": {
"additionalProperties": true,
"properties": {
"name": {
"type": "string"
},
"nativeId": {
"type": "string"
}
},
"required": ["name", "nativeId"],
"type": "object"
}
}
}
```

## Additional Information and Links

- **Trigger Type**: [FIRE_AND_FORGET](../trigger-types.md#fire-and-forget)
Original file line number Diff line number Diff line change
@@ -0,0 +1,86 @@
---
id: ciem-scope-selection-changed
title: CIEM Scope Selection Changed
pagination_label: CIEM Scope Selection Changed
sidebar_label: CIEM Scope Selection Changed
sidebar_class_name: ciemScopeSelectionChanged
keywords: ['event', 'trigger', 'ciem', 'scope', 'selection', 'available']
description: Fires after a user changes the scope selection for a CIEM source.
slug: /extensibility/event-triggers/triggers/ciem-scope-selection-changed
tags: ['Event Triggers', 'Available Event Triggers', 'Fire and Forget']
---

## Event Context

A user has changed the scope selection for a source. If a cloud scope is deselected, SailPoint CIEM will no longer check for changes to that specific AWS account, Azure subscription, or GCP project.

You can use a JSONPath filter expression to narrow down the circumstances under which your workflow will be triggered.

This trigger only fires if you have the CIEM service.

This is an example input from this trigger:

```json
{
"$ref": "#/definitions/record:ScopeSelectionChanged",
"definitions": {
"record:Scope": {
"additionalProperties": true,
"properties": {
"name": {
"type": "string"
},
"nativeId": {
"type": "string"
}
},
"required": ["name", "nativeId"],
"type": "object"
},
"record:ScopeSelectionChanged": {
"additionalProperties": true,
"properties": {
"event": {
"type": "string"
},
"identityDisplayName": {
"type": "string"
},
"identityId": {
"type": "string"
},
"scopesModified": {
"items": {
"$ref": "#/definitions/record:Scope"
},
"type": "array"
},
"sourceIscId": {
"type": "string"
},
"sourceName": {
"type": "string"
},
"sourceNativeId": {
"type": "string"
},
"timestamp": {
"type": "string"
},
"total": {
"minimum": 1,
"type": "integer"
},
"truncated": {
"type": "boolean"
}
},
"type": "object"
}
}
}
```

## Additional Information and Links

- **Trigger Type**: [FIRE_AND_FORGET](../trigger-types.md#fire-and-forget)
Loading