Which permissions are required for each integration?
Learn the permissions required for each Nightfall integration.
Please find the permissions required for each integration, in the table below: Native Integrations:
Integrations | Permissions Required | Roles Required for install |
---|---|---|
Slack | You can create private channels in Channel Management Permissions. To create, Select the default option - Everyone, plus multi-channel guests. Nightfall Enterprise DLP for Slack uses three user token scopes:
Nightfall Enterprise DLP for Slack has 13 Bot Token Scopes:
Nightfall Pro DLP for Slack has 26 Bot Token Scopes:
Nightfall Pro DLP for Slack has nine User Token Scopes:
| Slack Workspace Owner - Pro Slack Org Owner - Enterprise |
Google Drive | The following access permissions are required: https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.group.member.readonly, https://www.googleapis.com/auth/admin.directory.domain.readonly, https://www.googleapis.com/auth/drive | Google Super Admin |
Access to the following is required:
| Google Service Account | |
Confluence | Space Permissions:
| Confluence Admin |
Jira | Nightfall for Jira can perform the following actions on your behalf:
| Jira Admin |
Github | To enable integration, Read access to the following is required:
| Github Organization Owner |
Salesforce | Nightfall DLP connected app package required the following permissions:
| A dedicated user with system administrator privileges in Salesforce can install the connected app package, and grant access to Nightfall via OAuth. |
Alert Platforms:
Alert Platform | Permissions Required for Install |
---|---|
Slack | Slack Workspace Owner |
Jira | Jira Admin |
For more information on which integrations/platforms would require/recommend a service account, please refer the page below:
Using Service Accounts with NightfallLast updated