
Data Detection and Response	Detect and remediate PII, PCI, PHI, and API keys exposed in locations like Slack and GitHub.	/files/pPNBuDKmz3V075vxLJg0	/pages/zVY2aXRrK7YPp9hyVE62
Posture Management	Get real-time visibility into permissions and sharing settings to prevent security posture drift.	/files/EIQXW0vn2K2Tv3MjvzH5	https://help.nightfall.ai/data-security-posture-management
Data Exfiltration Prevention	See the full lineage of sensitive documents inadvertently or maliciously transferred and take action.	/files/SlSFdIYOjrtTdEzXCNZa	https://help.nightfall.ai/data-exfiltration-prevention
Data Encryption	AI-Native sensitive data detection and encryption for email.	/files/Gzk3o8r7FTLi6rhzvQqM	https://help.nightfall.ai/data-encryption
Developer APIs	APIs to filter sensitive data from your GenAI apps, models, and datasets.	/files/RSi3S6jgptD6Go9Pb3IR	https://help.nightfall.ai/firewall-for-ai
Data Discovery and Classification	Scan historic data to detect sensitive data exposed on public platforms.	/files/P1jHnS3treYpdObqGtqT	https://help.nightfall.ai/audit
Detection Playground	Test drive the Nightfall Detection Engine. Scan input text & files for sensitive data	/files/z7KccfXaWMYcoBv5a8Ji	https://playground.nightfall.ai/

\n\n{% hint style=\"info\" %}\nYou must add the Nightfall Pro Slack application to all the channels that you wish to scan with Nightfall.\n{% endhint %}\n\n## Applying Filters\n\nThe Filters section provides you an added level of granularity in setting the Scope. You can use specific filters to filter data based on Users, Groups, Channels, or Apps. \n\n## How Slack Filters Work\n\nSlack policies support filtering based on users, user groups, and apps. These options provide flexible, granular control on whom to apply the monitoring. The **Only Include** option is very useful to pick specific required users, groups or apps for monitoring. particularly useful for creating broad policies with specific exceptions. Combining user and group options allows for complex, layered access control. The **exclude** option allows you to exclude the monitoring of unwanted users, user groups and apps, thus reducing the unwanted noise from secure entities.\n\n

\n\n### Filtering by Users\n\n- **Only Include**: Only messages sent by selected users are scanned for sensitive data. \n- **Exclude**: Messages sent by excluded users are not scanned. \n\n### Filtering by Groups\n\n- **Only Include**: Only messages sent by users in included Slack groups are scanned for sensitive data. \n- **Exclude**: Messages sent by users in excluded Slack groups are not scanned.\n\n### Filtering by Apps\n\n- **Only Include**: Only messages sent by included Slack apps are scanned for sensitive data. \n- **Exclude**: Messages sent by excluded Slack apps are not scanned.\n\n## Priority Order for Conflict Management\n\nNightfall uses prioritization to decide which messages to scan when multiple filters are configured in a policy. The order of priority is:\n\n1. User Exclusion\n2. User Inclusion\n3. Group Exclusion\n4. Group Inclusion\n\n**How it works:**\n\n1\\. Initially, Nightfall checks if the file owner is on the User Exclusion list. If they are, their messages are not scanned, no matter how other filters are configured in a policy.\n\n2\\. If the user isn't excluded, Nightfall then checks if they're on the User Inclusion list. If they are, all their messages are scanned for that policy.\n\n3\\. If the user isn't on either the exclusion or inclusion lists, Nightfall looks at group memberships. It checks if the user belongs to any excluded groups. If they do, their messages are not scanned for that policy.\n\n4\\. Finally, if none of the above apply, Nightfall checks if the user is in any included groups. If they are, their messages are scanned for that policy. If not, the messages are not scanned.\n\n
\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/slack/slack_pro_policy/scope.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:40:55.265Z","2026-08-04T18:41:06.165Z","adebb942-f8d0-4892-bce6-e124560c044f",[],[],[],"help.nightfall.ai / slack / slack_pro_policy.md","helpnightfallai-slack-slack-pro-policymd","https://help.nightfall.ai/slack/slack_pro_policy.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/slack/slack_pro_policy.md).\n\n# Configuring Policies for Slack Pro and the Slack Business+ Editions\n\nDLP policies are a set of rules that include specific conditions, actions, and exceptions that monitor and filter data. DLP policies help you to monitor and remediate the flow of sensitive data within your organization. Depending on your Nightfall policy configuration, you can set up policies to monitor data that is sent through some or all applications within your organization. You can configure policies and choose to not apply them all the time. \n\nBefore you define a policy, or a set of policies, you must define the objectives of each policy, which can then be fulfilled when you configure the policy. Here are a few important questions to ask before configuring your policies: \n\n• What data do you plan to monitor? \n\n• Where within the organization do you want to monitor? \n\n• What should be the scope of each policy? \n\n• What conditions must apply for the policy to match? \n\n• What exceptions/exclusions can be allowed? \n\n• What remediation actions should the policy take? \n\nYou can now set up policies to determine which Slack channels are monitored (and which are excluded) for violations and what actions Nightfall must take. Policies determine the content that will be scanned by Nightfall, and workflows that are followed to manage violations. \n\nPolicies for Slack integration allow you to define configurations specific to Slack, such as how to handle messages for particular channels or use automated actions such as Quarantine.\n\nCreating a Nightfall policy involves the following tasks:\n\n1. Create Policies\n2. Define the policy scope and exclusions\n3. Configure Detection Rule\n4. Configure Automated Actions\n\n**Note:** Instructions to configure policies differ for Slack Pro and Slack Enterprise options. Refer to the Slack tier that you are using.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/slack/slack_pro_policy.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:13:05.745Z","2026-08-04T18:33:00.846Z","30e2129b-1ec7-4c02-9fca-f4e99db5115a",[],[],[],"help.nightfall.ai / slack / slack_pro_policy / integration.md","helpnightfallai-slack-slack-pro-policy-integrationmd","https://help.nightfall.ai/slack/slack_pro_policy/integration.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/slack/slack_pro_policy/integration.md).\n\n# Slack Pro and Business+ App Selection\n\nIn this stage, you select the Integration for which the policy is created. In this case, Slack integration must be selected. \n\n1. Click **Policies** from the left menu.\n2. Click **+ New Policy**.\n3. Select **Sensitive Data**.\n4. Select the **Slack** integration.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/slack/slack_pro_policy/integration.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:40:55.139Z","2026-08-04T18:40:55.172Z","9ceee96f-f0b0-4caa-8eab-c45794d27dd4",[],[],[],"help.nightfall.ai / slack / slack-faqs.md","helpnightfallai-slack-slack-faqsmd","https://help.nightfall.ai/slack/slack-faqs.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/slack/slack-faqs.md).\n\n# FAQs\n\nPlease find links to our FAQs for Slack in the subpages of this section.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/slack/slack-faqs.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:13:10.105Z","2026-08-04T18:33:03.171Z","567d7d8a-c053-4b1d-ba56-e85fc3baa5b0",[],[],[],"help.nightfall.ai / slack / enterprise_policy.md","helpnightfallai-slack-enterprise-policymd","https://help.nightfall.ai/slack/enterprise_policy.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/slack/enterprise_policy.md).\n\n# Configuring Policies for the Slack Enterprise Edition\n\nDLP policies are a set of rules that include specific conditions, actions, and exceptions that monitor and filter data. DLP policies help you to monitor and remediate the flow of sensitive data within your organization. Depending on your Nightfall policy configuration, you can set up policies to monitor data that is sent through some or all applications within your organization. You can configure policies and choose to not apply them all the time. \n\nBefore you define a policy, or a set of policies, you must define the objectives of each policy, which can then be fulfilled when you configure the policy. Here are a few important questions to ask before configuring your policies: \n\n• What data do you plan to monitor? \n\n• Where within the organization do you want to monitor? \n\n• What should be the scope of each policy? \n\n• What conditions must apply for the policy to match? \n\n• What exceptions/exclusions can be allowed? \n\n• What remediation actions should the policy take? \n\nYou can now set up policies to determine which Slack channels are monitored (and which are excluded) for violations and what actions Nightfall must take. Policies determine the content that will be scanned by Nightfall, and workflows that are followed to manage violations. \n\nPolicies for Slack integration allow you to define configurations specific to Slack, such as how to handle messages for particular channels or use automated actions such as Quarantine.\n\n![Setting up Policies](/api/knowledge-base/images/d36427e1-79fd-4aec-890c-e055853ef0f0)\n\nCreating a Nightfall policy involves the following tasks:\n\n1. Create Policies\n2. Define the policy scope and exclusions\n3. Configure Detection Rule\n4. Configure Automated Actions\n\n**Note:** Instructions to configure policies differ for Slack Pro and Slack Enterprise options. Refer to the Slack tier that you are using.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/slack/enterprise_policy.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:13:08.074Z","2026-08-04T18:33:02.080Z","d6095ff2-3619-4aed-a1eb-3622daf53517",[],[],[],"help.nightfall.ai / salesforce / policies.md","helpnightfallai-salesforce-policiesmd","https://help.nightfall.ai/salesforce/policies.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/salesforce/policies.md).\n\n# Nightfall Policies for Salesforce\n\nDLP policies are a set of rules that include specific conditions, actions, and exceptions that monitor and filter data. DLP policies also enable you to remediate any leakage of sensitive information from within your organization.\n\n- You can set up policies to scan data that is sent through some or all applications within your organization. \n- You can configure policies and choose to not apply them all the time.\n\nBefore you define a policy, or a set of policies, we recommend that you define the objectives of each policy, which can then be fulfilled when you configure the policy.\n\nHere are a few important questions to ask before configuring your policies:\n\n- What data do you plan to monitor?\n- Where within the organization do you want to monitor?\n- What should be the scope of each policy?\n- What conditions must apply for the policy to match?\n- What exceptions/exclusions can be allowed?\n- What remediation actions should the policy take?\n\nYou can configure policies on the Salesforce integration to determine which objects and fields must be monitored, and which ones excluded. You can also automate the remediation actions that you want Nightfall to perform on a policy violation.\n\nConfiguring DLP policies on Salesforce involves the following steps:\n\n- [Salesforce App Selection](/salesforce/policies/integration.md)\n- [Configure Scope for Salesforce](/salesforce/policies/scope.md)\n- [Configure Detection Rules for Salesforce](/salesforce/policies/detection_rules.md)\n- [Configure Advanced Settings for Salesforce](/salesforce/policies/advanced_settings.md)\n- [Risk Score for Salesforce](/salesforce/policies/risk_score.md)\n- [Manage Salesforce Events](/salesforce/policies/events.md)\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/salesforce/policies.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:30:41.474Z","2026-08-04T18:30:41.502Z","d0b3463b-2d2f-42d3-81fa-5d3f02ad87d0",[],[],[],"help.nightfall.ai / salesforce / overview.md","helpnightfallai-salesforce-overviewmd","https://help.nightfall.ai/salesforce/overview.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/salesforce/overview.md).\n\n# Overview\n\nWhen working within a Salesforce environment, you can add data in up to 2000 fields. This data moves between Salesforce and other applications, from headquarters to remote work zones, from your premises to cloud, from a trusted account to a lead. When you perform tasks like updating records via email, web, or by using APIs that integrate with Salesforce, you expose your data and make it vulnerable to misuse.\n\nData leaks can impact your business in many ways - revenue loss, customer satisfaction and damaged brand reputation, besides potential penalties and lawsuits.\n\nLegacy DLP solutions don’t collect threat context information, and leave you blind to data movement between compromised user accounts and identities. Data leakage through compromised accounts appears genuine to such solutions.\n\nNightfall for Salesforce enables you to enforce policies for data classification and protection on standard objects, files and attachments. It scans objects and fields in real time in production or sandbox environments. You can instantly discover any theft or leakage, and take remedial action.\n\nNightfall for Salesforce supports the following Salesforce Sales Cloud editions across both production and sandbox instances:\n\n- Salesforce Sales Cloud - Enterprise, Unlimited and Developer editions\n- Salesforce Service Cloud - Enterprise, Unlimited and Developer editions \n- Salesforce Health Cloud - Enterprise, Unlimited and Developer editions \n- Salesforce Experience or Community Cloud \n\nYou can install and authorize Nightfall DLP app package in Salesforce production environments.\n\nNightfall for Salesforce supports real-time scans and alerts for the following objects: \n\n- Accounts\n- Attachments\n- Case\n- Contacts\n- Contracts\n- Email messages\n- Feed Comments\n- Feed Item\n- Lead\n- Opportunity\n- Task\n- User\n\nNote: Field types including standard and custom only are currently supported\n\nFeatures like audit trails, which track who has accessed and modified data help in preventing accidental or unauthorized loss of sensitive data. Nightfall DLP for Salesforce eliminates data exposure risks from Salesforce by automating data security across all objects in your organization. It will enable you to be compliant with[ PCI DSS](https://www.pcicomplianceguide.org/faq/) as well as [GDPR](https://ec.europa.eu/info/law/law-topic/data-protection_en) and [CCPA](https://oag.ca.gov/privacy/ccpa).\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/salesforce/overview.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:30:38.264Z","2026-08-04T18:30:38.299Z","13fc06f8-0e5c-4ac7-829b-d910261b6cc9",[],[],[],"help.nightfall.ai / salesforce / getting-started.md","helpnightfallai-salesforce-getting-startedmd","https://help.nightfall.ai/salesforce/getting-started.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/salesforce/getting-started.md).\n\n# Getting Started\n\nNightfall's Salesforce integration allows you to scan updates to objects and fields in real-time across sandbox and production organizations in Salesforce. \\\n\\\nThis getting started guide will walk you through installing and upgrading the components of the solution.\n\n{% hint style=\"warning\" %}\nSalesforce vertical cloud offerings are not supported as of today.\n{% endhint %}\n\nNightfall's Salesforce integration allows you to scan updates to objects and fields in real-time across sandbox and production organizations in Salesforce. \\\n\\\nThis getting started guide will walk you through installing and upgrading the components of the solution.\n\nNightfall DLP for Salesforce supports the following Salesforce Sales Cloud editions across both production and sandbox instances:\n\n- Enterprise\n- Unlimited\n- Developer\n\nSalesforce vertical cloud offerings are not supported as of today.\n\nYou can install and authorize Nightfall DLP app package in Salesforce production environments.\n\nYou can view and remediate Salesforce DLP policy violations within the Nightfall dashboard and violations monitoring page. \n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/salesforce/getting-started.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:30:38.115Z","2026-08-04T18:30:38.155Z","f98cc56d-1580-4ab8-8335-1397c5c16f12",[],[],[],"help.nightfall.ai / salesforce / faqs.md","helpnightfallai-salesforce-faqsmd","https://help.nightfall.ai/salesforce/faqs.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/salesforce/faqs.md).\n\n# FAQs\n\n#### How does Nightfall DLP for Salesforce leverage Salesforce Platform Events?\n\nNightfall DLP for Salesforce depends on the [Platform Events](https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_intro_emp.htm) messaging platform of a Salesforce org that Salesforce promotes as best practise to receive notifications for Salesforce events. Further, [Platform Events limits](https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_limits_default.htm) are shared across all workflows that leverage Platform Events and, per Salesforce, are replinished on a 24 hour rolling basis.\n\nEvery time an update happens on one of the objects monitoried by Nightfall DLP for Salesfoce, Nightfall's Salesforce package triggers an event that is queued in the Salesforce orgs Platform Events messaging queue. Subsequently Nightfall DLP Platform retrieves the event and the payload from the Platform Events queue and processes the update.\n\n#### How Salesforce Platform Events limits affect Nightfall DLP for Salesforce processing?\n\nNightfall understands the criticality of Platform Events for Salesforce workflows and has defined a High Threshold and a Low Threshold for Platform Events usage on the customer's Salesforce org. If the Platform Events usage on the customer's Salesforce org breaches the High Threshold then Nightfall DLP for Salesforce will pause scan. Nightfall DLP for Salesforce will resume scan only when the Platform Events usage on the customer's Salesforce org goes below the Low Threshold. This way Nightfall DLP for Salesforce behaves as a model enterprise application and ensures that critical Salesforce workflows (like order processing) are prioritised over sensitive data scan.\n\nPlease reach out to your customer success manager for further details.\n\n#### I selected Delete and Redact in my Policy. Is that a problem?\n\nIf you opted for both Redact and Delete actions in a policy for a set of objects and fields, Delete takes precedence over redact. \n\nAll potential sensitive tokens are automatically deleted from the configured objects and fields.\n\n#### On a single object, I want to configure a policy to automatically delete all credit card data, but auto-redact SSN.\n\nYou can create two policies on the object;\n\n- one policy with a detection rule for the SSN detector, with redaction as the automated action.\n- Another policy with a detection rule for credit card detector with delete as the automation action.\n\n#### Why does Nightfall only scan emails that are sent, replied, forwarded but not the draft emails?\n\nSalesforce may save emails in draft stage multiple times either because of the user action or automatically. Every save triggers a Salesforce event which causes Nightfall to scane the contents of the email draft if there is a policy to scan emails objects. This can lead to a situation where multiple violations are reported for the same sensitive data if the email is saved multiple times in the draft stage. \n\nSo, Nightfall has disabled scanning of emails as long as they are in draft stage. However, emails will continue to be be scanned when other operations happen, for examples emails are sent, replied and forwarded. The user can reach out to Nightfall if they wish Nightfall to scan the drafts too, but it should be noted that as described above, this can lead to the same findings getting flagged across violations whenever the draft is saved.\n\n#### Nightfall doesn’t remediate sensitive information from Email Message object. How do I solve this?\n\nEmail message is an immutable object in Salesforce. Therefore, Nightfall cannot modify the object record. You can delete the email from within Salesforce, once you receive a notification.\n\n**I received a violation notification. However, the information was removed by the user in Salesforce. How will auto remediation respond?**\n\nIf the object does not contain sensitive information at the time of remediation, Nightfall will not remediate any data. Nightfall will re-scan the violated object and fields before performing any remediation.\n\n#### I performed manual remediation on an object record after the object was deleted from Salesforce. How do I know if it was successful?\n\nNightfall detects that the object record does not exist anymore, and will stop remediation. A notification is sent to you.\n\n#### How do I know if remediation action was successful?\n\nNightfall sends notifications for remediation action it performs.\n\n#### A new version of the attachment was uploaded, can I remediate the previous version which had sensitive information?\n\nNo, Salesforce does not provide the option to delete specific versions of a file. Further, Salesforce only allows deletion of all the versions of an attachment. You can manually delete the attachment in Salesforce.\n\nIf the version was updated, and the object clears the scan, Nightfall will not delete the attachment and issues a notification with this information. \n\n#### If I have Einstein Activity Capture configured which synchronizes my mail and I see them in Salesforce. Can Nightfall detect sensitive information in these objects too?\n\nNo. Nightfall does not have the capability to detect sensitive information in any entity synced by Einstein Activity Capture.\n\n#### What does the Nightfall DLP webhook notification for Salesforce look like?\n\nPlease see some example webhook responses below:\n\n- Violations\n- Manual Remediation\n- Automated Remediation\n\n#### Violation\n\n```\n{\n\"detectionRulesLink\": \"https://app.nightfall.ai/?intendedRoute=detection-engine/detection-rules\",\n\"detectionRulesViolated\": \"SSN DR\",\n\"eventType\": \"violation\",\n\"message\": \"Policy violation detected in Salesforce\",\n\"policiesLink\": \"https://app.nightfall.ai/?intendedRoute=salesforce/?policyUUID%5B%5D=cfa52d83-76d4-4840-a260-15e535c740a6\",\n\"policiesViolated\": \"Account\",\n\"service\": \"Salesforce\",\n\"timestamp\": \"2022-06-22T06:34:30Z\",\n\"violationID\": \"CRY7XI\",\n\"violationMetadata\": {\n\t\"acknowledgeLink\": \"https://app.nightfall.ai/?intendedRoute=salesforce/remediation/082c0eb5-df1c-46cb-b8c2-f649747c9020/CRY7XI/acknowledge\",\n\t\"deleteRecordLink\": \"https://app.nightfall.ai/?intendedRoute=salesforce/remediation/082c0eb5-df1c-46cb-b8c2-f649747c9020/CRY7XI/delete\",\n\t\"event\": \"Record Updation\",\n\t\"fields\": \"description\",\n\t\"findingSnippets\": [\n\t\t\"SSN: 55*********.\"\n\t],\n\t\"findings\": \"US social security number (SSN) (1 Very Likely)\",\n\t\"objectName\": \"Case\",\n\t\"orgName\": \"NightfallProdDemo\",\n\t\"orgType\": \"Sandbox\",\n\t\"recordID\": \"5008K000000yP86QAE\",\n\t\"recordLink\": \"https://prodnfdlpdemo--fullsandbo.sandbox.my.salesforce.com/5008K000000yP86QAE\",\n\t\"redactFindingsLink\": \"https://app.nightfall.ai/?intendedRoute=salesforce/remediation/082c0eb5-df1c-46cb-b8c2-f649747c9020/CRY7XI/redact\",\n\t\"who\": \"Mohit Mangnani\",\n\t\"whoLink\": \"https://prodnfdlpdemo--fullsandbo.sandbox.my.salesforce.com/0058a00000KgiirAAB\"\n},\n\"violationTime\": \"22 Jun 2022 at 6:34AM UTC\"\n}\n```\n\n#### Manual Remediation\n\n```\n{\n\t\"eventType\": \"remediation\",\n\t\"message\": \"mohit+prod@nightfall.ai deleted finding(s).\",\n\t\"remediationMetadata\": {\n\t\t\"ActionUser\": \"mohit+prod@nightfall.ai\",\n\t\t\"actionType\": \"delete\",\n\t\t\"fields\": \"description\",\n\t\t\"objectName\": \"Case\",\n\t\t\"remediationType\": \"manual\",\n\t\t\"success\": true,\n\t\t\"unchangedFields\": \"\"\n\t},\n\t\"remediationTime\": \"22 Jun 2022 at 6:38AM UTC\",\n\t\"service\": \"Salesforce\",\n\t\"timestamp\": \"2022-06-22T06:38:07Z\",\n\t\"violationID\": \"CRY7XI\"\n}\n```\n\n#### Automated Remediation\n\n```\n{\n\t\"eventType\": \"remediation\",\n\t\"message\": \"mohit+prod@nightfall.ai deleted finding(s).\",\n\t\"remediationMetadata\": {\n\t\t\"ActionUser\": \"mohit+prod@nightfall.ai\",\n\t\t\"actionType\": \"delete\",\n\t\t\"fields\": \"description\",\n\t\t\"objectName\": \"Case\",\n\t\t\"remediationType\": \"manual\",\n\t\t\"success\": true,\n\t\t\"unchangedFields\": \"\"\n\t},\n\t\"remediationTime\": \"22 Jun 2022 at 6:38AM UTC\",\n\t\"service\": \"Salesforce\",\n\t\"timestamp\": \"2022-06-22T06:38:07Z\",\n\t\"violationID\": \"CRY7XI\"\n}\n```\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/salesforce/faqs.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:30:40.166Z","2026-08-04T18:30:40.214Z","23a01944-7475-4551-88ac-007f413d6711",[],[],[],"help.nightfall.ai / notion / policies / risk_score.md","helpnightfallai-notion-policies-risk-scoremd","https://help.nightfall.ai/notion/policies/risk_score.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/notion/policies/risk_score.md).\n\n# Risk Score for Notion\n\nIn this final stage, you assign a name to the policy, verify your configurations, and create the policy. \n\n1. Enter a name for the policy.\n2. (Optional) Enter a description for the policy. \n3. Choose the Policy risk score. By default the risk score is set to **Nightfall Risk Score**. You can set it to **Custom Risk score**, and select one of the risk levels, if required. To learn more about Risk scoring, refer to the [Name and Risk Score](/detection_platform/policies/risk_score.md#risk-scoring) document.\n4. Click **Next**.\n\n

\n\n5. Verify if all the policy configurations are set up as per your requirements.\n6. (Optional) Click back or click on any specific stage to modify any of the policy configurations.\n7. Click **Submit**.\n\n

\n\n3. Apply filters to view only Notion Events.\n\n

\n\nOnce you filter the Events to view only the Notion Events, you can refer to the [Data Detection and Response Events](/dashboard/sdp_events.md#event-list-view) section to learn more about the available options. \n\n4. Click on any of the Events to view details of an Event. You may click anywhere in the row of an Event that you wish to inspect. Details will be present via a side panel.\n\n

\n\nOn the Event detail view, you can view the applicable actions from the actions section at the bottom.\n\n## Event Actions\n\nNightfall allows you to take various action on Events. When you take an action on an Event, the status of the Event changes accordingly. To learn more about Event status, refer to the [Event Status](/dashboard/sdp_events/status.md) document.\n\nIn Notion, you can take actions either from the Event list view page or the Event detail view page. On the Event list view page, you can click the ellipsis menu to view the available list of actions. \n\n

\n\nOn the Event detail view, you can view the applicable actions from the actions section at the bottom.\n\n

\n\nTo view the complete list of actions, applicable to all the integrations, you can refer to the [Applying Actions on Events](/dashboard/sdp_events/event_actions.md) document. \n\nThe list of actions supported for Notion are as follows. Some of these actions are common to other integrations as well. \n\n- **Copy Event Link**: The action copies the link to the Event. You can save or send this link to directly open the Event. This action is available only on the Event detail view.\n- **View in Notion**: This action redirects to the sensitive data in the source Notion page. While this action is available only on the Event detail view, please note that relevant access to the source of sensitive data in Notion should be present.\n- **Ignore**: The ignore action flags Nightfall to ignore all the findings in the Event and may be taken if you find the findings false positive. This action marks the Event as resolved and moves it to the Resolved section. You can undo this action. \n- **Acknowledge**: You can take this action to notify other users that you have looked into this Event and will take suitable action in future. \n- **Notify Email**: This action notifies the end user who added the sensitive data file to the OneDrive about the event, through email.\n- **Notify Slack**: This action notifies the end user who added the sensitive data file to the OneDrive about the event, through Slack.\n- **Send to JIRA**: This action creates a JIRA ticket for the Event. You can pick a project and Issue type while creating the JIRA ticket and can assign the JIRA ticket to the end-user.\n- **Redact**: This action redacts the sensitive data present in the Notion page. \n- **Remove Access**: This action removes the page from the web and/or removes guest access to the page. \n- **Delete Attachment**: This action deletes the sensitive data present in the attachments of a Notion page.\n- **Resolve**: This action must be taken when the sensitive data is removed completely. This action resolves the Event.\n\n{% hint style=\"info\" %}\nTo learn more about how Nightfall handles Deduplication and Auto Resolution of Notion Events, see [Deduplication and Automatic Resolution of Events](/dashboard/sdp_events/deduplication.md#notion).\n{% endhint %}\n\n## Email Notification\n\n- If you have configured Email Notification in [Admin Alerting](https://help.nightfall.ai/nightfall-ai/notion/configuring-policies/advanced-settings#admin-alerting), Nightfall admins receive the Email notification. This Email allows admins to take actions from within the Email. \n- If you have configured Email Notification in the Automation section of [End user notification](https://help.nightfall.ai/nightfall-ai/notion/configuring-policies/advanced-settings#end-user-notification) settings, end users receive an email from Nightfall. This Email allows end users to take actions from within the Email. \n\n

\n\nIf you have selected Slack as an End-user remediation channel, end-users can perform the above tasks from Slack as well. \n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/notion/policies/events.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:33:22.699Z","2026-08-04T18:33:53.778Z","fa3c8d40-622c-45ba-90c5-42bad03b2130",[],[],[],"help.nightfall.ai / notion / policies / detection_rules.md","helpnightfallai-notion-policies-detection-rulesmd","https://help.nightfall.ai/notion/policies/detection_rules.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/notion/policies/detection_rules.md).\n\n# Configure Detection Rules for Notion\n\nIn this section, you can select the Detection rules for the policy and If not already created, you can create detection rules. To learn more about how to configure detection rules, see [Configuring Detection Rules](https://help.nightfall.ai/nightfall-ai/nightfall-for-slack/installation-instructions-nightfall-for-slack-1/configuring-detection-rules).\n\nTo select detection rules, select a detection rule from the list of rules that are displayed and then select one of the following options.\n\n- **All Detection Rules**: Select this option to include all the detection rules in the policy.\n- **Selected Detection Rules**: Select this option to include only that detection rule in the policy that you selected above.\n- **Unselected Detection Rules**: Select this option to include all the other detection rules in the policy, that you did not select above.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/notion/policies/detection_rules.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:33:22.540Z","2026-08-04T18:33:22.572Z","3377c7b9-2f75-49c0-a907-9c5b75fd7632",[],[],[],"help.nightfall.ai / notion / policies / advanced_settings.md","helpnightfallai-notion-policies-advanced-settingsmd","https://help.nightfall.ai/notion/policies/advanced_settings.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/notion/policies/advanced_settings.md).\n\n# Configure Advanced Settings for Notion\n\nThis stage allows you to select notification channels if a policy violation occurs. The advanced settings page consists of the following configurations. \n\n[#admin-alerting](#admin-alerting \"mention\"): This section describes the process of setting alerts for Nightfall administrators when a policy violation is detected.\n\n[#automated-actions](#automated-actions \"mention\"): This section describes the automated actions that can be taken when a policy violation is detected.\n\n[#end-user-notification](#end-user-notification \"mention\"): This section describes the process of setting alerts for end users (a person whose action caused a violation) when a policy violation is detected.\n\n## Admin Alerting\n\n{% hint style=\"info\" %}\nThe alert configurations configured in this section describe the process of creating alerts at the policy level. Policy-level alerts apply only to the policy on which they are configured. To configure an alert on all the Slack policies, you must configure alerts at the integration level. To learn more about how to configure integration-level policies for Slack integration, read [this document](https://help.nightfall.ai/nightfall-ai/notion/configuring-integration-alerts).\n{% endhint %}\n\nThe steps to configure alert channels for policy-level integration are the same as in the case of integration-level alerts. You can refer to [this document](https://help.nightfall.ai/nightfall-ai/notion/configuring-integration-alerts#configure-alerts-at-the-integration-level) for steps.\n\n## Automated Actions\n\nThis section describes the various actions that Nightfall takes automatically when a violation is detected. You must turn on the toggle switch to enable an action. All the automated actions are permanent and cannot be reversed once applied. You can also set the timeline as to when an action must be taken (immediately after detecting a violation or after some time).\n\nThe various automated actions are described as follows.\n\n- **Redact**: This action redacts all the sensitive information found in the content of a Notion page. You can turn on the toggle switch to enable this action. \\\n \\\n You must also select the timeline as to when this action must be taken after a policy violation is detected. You can either choose to take the action immediately after detecting a violation or after a few minutes, hours, or days. \n- **Delete Attachment**: This action deletes any attachments in the Notion pages that contain sensitive information. You can turn on the toggle switch to enable this action. \\\n \\\n You must also select the timeline as to when this action must be taken after a policy violation is detected. You can either choose to take the action immediately after detecting a violation or after a few minutes, hours, or days. \n- **Mark as Private**: This action modifies the status of the Notion page that contains sensitive information. You can either choose to unpublish the webpage or remove guest users from your Notion account, thus ensuring that none of the people from outside your organization are able to view sensitive information on your Notion page.\\\n \\\n You must also select the timeline as to when this action must be taken after a policy violation is detected. You can either choose to take the action immediately after detecting a violation or after a few minutes, hours, or days. \n\n

\n\n### Conflict Management in Automated Actions\n\nConflicts can arise in two main scenarios:\n\n1. All the automated actions are configured in a single policy.\n2. Multiple policies with different automated actions were violated simultaneously within the same file, message or record. \n\nWhen conflicts occur, Nightfall implements the most severe automated action. The priority order to manage conflicts in Notion is as follows.\n\n1. Delete Attachment\n2. Redact\n3. Remove Access\n\n**Conflict resolution**:\n\n- **Delete Attachment** takes precedence over all other actions if an attachment contains sensitive data.\n- For conflicts between **Redact** and **Remove Access**:\n - **Unpublished pages**: Only **Redact** is applied\n - **Published pages**: Both **Redact** and **Remove Access** are implemented. The page is unpublished, and sensitive data is redacted in the internal Notion page.\n\n## End User Notification\n\nThis section allows you to configure notifications to be sent to the end user whose actions triggered the violation. \n\n- **Custom Message**: Enter a custom message to be sent to the end user. This message is sent in an Email. You can modify the default message provided by Nightfall and draft your message. The total character length allowed is 1000 characters. You can also add hyperlinks in the custom message. The syntax is \\. For example, to hyperlink [https://www.nightfall.ai](https://www.nightfall.ai/) with the text **Nightfall website**, you must write <[https://www.nightfall.ai](https://www.nightfall.ai/) | Nightfall website> .\n- **Automation**: You can either select Email, Slack, or both as an automated notification method. You must turn the toggle switch to use this option. Based on the options selected, end-users receive notification on their Email account associated with Zendesk, or Slack account configured.\n\n## End User Remediation\n\nEnd-User remediation (also known as Human Firewall) allows you to configure remediation measures that end users can take when a violation is detected on their Zendesk ticket. You must turn on the toggle switch to use this option. The various available options are as follows.\n\n- **Redact:** This action redacts all the sensitive information found in the Zendesk ticket's comments. To allow end-users to implement this action, you must disable it from the [#automated-actions](#automated-actions \"mention\") section. \n- **Delete Attachment**: This action deletes any attachments in the Zendesk ticket's comments that contain sensitive information. To allow end-users to implement this action, you must disable it from the [#automated-actions](#automated-actions \"mention\") section.\n- **Mark as Private:** This action modifies the permission of the comment (on which sensitive information is detected) from public to internal note. To allow end-users to implement this action, you must disable it from the [#automated-actions](#automated-actions \"mention\") section.\n- **Report as False Positive with Business Justification**: This option allows end users to report false positive alerts and provide a business justification as to why the alert is considered to be false positive. \n- **Report as False Positive**: This option allows end users to report false positive alerts.\n- **When a Violation is Reported as False Positive**: You can use this option to set actions to be taken when a violation is reported as false positive by the end-user. You can either set the remediation to be automatic or manual. \n- **Remind Every (until Violation expires)**: You can use this option to set a reminder for the end-user to take action on the violation. You can choose to remind the end user every 24, 48, or 72 hours.\n\n

\n\nWhen you configure alert settings at the integration level, the alert settings apply to all the policies, created for the Notion DLP integration. However, when you configure alert settings specifically for a policy, which is created in the Notion DLP integration, the alert settings are applicable only for that specific policy. \n\nThis document explains how to configure alerts at the integration level. To learn about how to configure alerts at the policy level, read [this document](/gmail/policies/advanced_settings.md#admin-alerting).\n\n## Prerequisites\n\n- To use Slack as an alert platform, you must first perform the required Slack configurations. You can refer to [this document](https://help.nightfall.ai/nightfall-ai/detection/setting-up-slack-as-an-alert-channel-in-nightfall) to learn more about how to configure Slack as an Alert platform. \n- To use Webhook as an alert platform, you must first perform the required Webhook configurations. You can refer to [this document](https://help.nightfall.ai/nightfall-ai/operationalizing-dlp/integrating-with-security-tools/integrating-with-siem#configuring-outgoing-webhooks)[ ](https://help.nightfall.ai/nightfall-ai/operationalizing-dlp/integrating-with-security-tools/integrating-with-siem#configuring-outgoing-webhooks)to learn more about how to configure Webhook as an Alert platform. \n- To use JIRA as an alert platform, you must have the DLP for the JIRA app installed from the [Atlassian Marketplace](https://marketplace.atlassian.com/apps/1226823/dlp-for-jira-nightfall-ai?tab=overview\\&hosting=cloud). You can read more about the DLP for JIRA integration [here](https://help.nightfall.ai/nightfall-ai/nightfall-for-jira/getting-started/installing-nightfall-for-jira). \n\n## Configure Alerts at the Integration Level \n\nYou can configure alerts at the integration level once you have installed the Nightfall for Notion DLP integration. \n\nTo configure alerts at the integration level:\n\n1. Navigate to the Notion DLP integration\n2. Scroll down to the **Alerting** section.\n3. You can configure one or multiple alert channels. \n\n### Configuring Slack as an Alert Channel\n\n1. To configure Slack as an alert channel, click **+ Slack channel**.\n\n

\n\n2. In the **Slack alert channel** field, enter the name of the Slack channel in which you wish to receive the alerts. \n3. Click **Save**. \n\n

\n\nA confirmation pop-up box is displayed to confirm if the Slack channel (entered in the second step) must be used only for Notion DLP integration or all the Nightfall integrations. \n\n4. Select **No, only integration level** to use the Slack channel only for Notion DLP, or select **Yes, please** to use the selected Slack channel for all the Nightfall integrations. \n\n

\n\n### Configuring Email as an Alert Channel\n\n1. Click **+ Email**.\n\n

\n\n2. Enter the Email ID of the recipient who should receive the notifications**.** \n3. Click **Save.** \n\n

\n\nA confirmation pop-up box is displayed to confirm if the Email ID (entered in the second step) must be used only for Notion DLP integration or all the Nightfall integrations. \n\n4. Select **No, only integration level** to use the Slack channel only for Notion DLP, or select **Yes, please** to use the selected Slack channel for all the Nightfall integrations. \n\n

\n\n### Configuring Webhook as an Alert Channel\n\n1. Click **+ Webhook**.\n2. Enter the Webhook URL.\n3. Click **Test**. If the test result is not successful, check the Webhook URL.\n4. (Optional) Click **Add Header** to add headers. \n5. Click **Save**.\n\n

\n\n{% hint style=\"info\" %}\nWhen you configure alerts to a Webhook, Nightfall AI sends occasional posts to:\n\n- To validate that the Webhook is properly configured before the policy is saved.\n- Periodically thereafter to ensure that the Webhook is still valid.\n\nThe response to the test Webhooks is `200` status code if successful.\n\nAn example of Webhook request is as follows.\n\n

{\n  \"service\": \"nightfall\",\n  \"test\": true,\n  \"timestamp\": \"2024-03-07T23:18:39Z\"\n}\n

\n\nThis is part of alert event consumption and can be ignored. \n{% endhint %}\n\n### **Configuring JIRA as an Alert Channel**\n\n1. Click **+ Jira Ticket.**\n2. Select a JIRA project from the **Jira Project** drop-down menu.\n3. Select an issue type from the **Issue Type** drop-down menu. \n4. (Optional) Add comments to be added in the JIRA ticket. \n5. Click **Save changes**.\n\n

\n\nA confirmation pop-up box is displayed to confirm if the JIRA settings configured for the Notion DLP integration must be applied to all the other Nightfall integrations too. \n\n6. Select **No, only integration level** to use the configurations only for Notion DLP, or select **Yes, please** to use the selected JIRA configurations for all the Nightfall integrations. \n\n

\n\n## Configure End-User Notification\n\nWhen an Event is triggered, Nightfall sends a notification to the end-user whose actions triggered the Event. While notifying the end-user, Nightfall also sends a text message. You can draft the text message to be sent to the end-user. This message applies to all the policies. Click **Save changes** once done.\n\n

\n\n6. Click **See All** to view all the Connections available in Notion (This option ensures that the Nightfall connection is displayed).\n\n

\n\n7. Click **Connect** on the Nightfall widget.\n\n

\n\n8. Click **Connect to Nightfall**.\n\n

\n\n9. A pop-up will appear that will be logged into your Nightfall instance. Click **Connect**.\n\n

\n\nA pop-up will appear that will be logged into your Nightfall instance. Click **Connect**.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/notion/installation.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:30:48.237Z","2026-08-04T18:31:19.483Z","a4295220-393a-4927-9c70-16b9593d5d97",[],[],[],"help.nightfall.ai / notion / getting_started.md","helpnightfallai-notion-getting-startedmd","https://help.nightfall.ai/notion/getting_started.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/notion/getting_started.md).\n\n# Getting Started\n\nNotion is a collaboration tool used for multiple tasks like note-taking, brainstorming ideas, project management, and so on. Since Notion can be used for multiple purposes and content created in Notion can be shared over the web, sensitive data like PII, credentials, and secrets could sprawl into Notion at an alarming rate. \n\nThis document explains how you can prevent sensitive data from being leaked through the Notion platform by using the Nightfall Notion integration.\n\n
\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/notion/getting_started.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:30:47.799Z","2026-08-04T18:30:47.829Z","e16de27a-0172-42ea-97be-3d7ad56e202b",[],[],[],"help.nightfall.ai / nightfall_settings / users_roles.md","helpnightfallai-nightfall-settings-users-rolesmd","https://help.nightfall.ai/nightfall_settings/users_roles.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/nightfall_settings/users_roles.md).\n\n# Users and Roles\n\nThe User management page allows you to add or remove users to the Nightfall application. A Nightfall admin has the privileges to add or remove users to the Nightfall console. To perform user and Roles related activities, you must navigate to the Users and Roles page.\n\nTo navigate to the Users and Roles page, \n\n1. Click the **Settings** icon.\n\n

\n\n2. Click **Users & roles**.\n\n

\n\nThe Users & roles page is as follows.\n\n

\n\n## Adding Users\n\nTo add new users to Nightfall, you must invite them. The steps are as follows.\n\n1. Click **+ Invite User**.\n\n

\n\n2. Enter the name of the user in the Name field.\n3. Enter the email ID of the user in the Email field.\n4. Select a role for the user from the role drop-down menu. Refer to the [Role Based Access Control (RBAC)](/nightfall_settings/role_based_access_control.md) document to learn more about user roles. \n5. Click **Invite**.\n\n

\n\nThe invited user receives an invite email. They must click the link and set a password to activate their account. \n\n

\n\nUsers who successfully activate their account are displayed as active users and their status is displayed as **Active** under the Status column. A user who does not accept the invite is displayed as **Expired** under the Status column. \n\n

\n\nAdmins can resend the invite email to Expired users by clicking the ellipsis menu. \n\n

\n\nAs you can see in the above image, Admins can also edit or delete users from the Nightfall app from the ellipsis menu. \n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/nightfall_settings/users_roles.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:32:18.827Z","2026-08-04T18:32:57.796Z","6faaaaa8-8d6a-4863-95a1-1e9ea6ad4148",[],[],[],"help.nightfall.ai / nightfall_settings / users_roles / authentication_options.md","helpnightfallai-nightfall-settings-users-roles-authentication-optionsmd","https://help.nightfall.ai/nightfall_settings/users_roles/authentication_options.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/nightfall_settings/users_roles/authentication_options.md).\n\n# Authentication Options\n\n## Creating a Strong Password\n\nPlease secure your Nightfall account with a strong password upon creation.\n\n**Password creation guidelines**\n\n- No more than 2 identical characters in a row\n- Special characters (!@#$%^&\\*)\n- Lower case (a-z), upper case (A-Z), and numbers (0-9)\n- Must have a minimum of 8 characters\n\n## Enabling SAML SSO\n\nSAML SSO Setup is now available for almost any SAML SSO identity provider (Okta, Azure, etc).\n\nTo enable SAML SSO, please reach out to your Customer Success Manager at Nightfall. They will require the following information from you:\n\n- Sign In URL\n- X509 Signing Certificate\n- Sign Out URL\n- A list of users (first name, last name, and email address) to whom you would like to give Nightfall accounts\n\n{% hint style=\"warning\" %}\nIf using Azure, Nightfall is required to provide the Post-Back URL and Entity ID **before** you provide the data shown above.\n{% endhint %}\n\nOnce you have provided those details, your Success Manager will schedule a configuration session with you to finalize the setup.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/nightfall_settings/users_roles/authentication_options.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:37:40.639Z","2026-08-04T18:37:40.825Z","585198d5-7d76-47ec-9931-e769360bd8cc",[],[],[],"help.nightfall.ai / nightfall_settings / role_based_access_control / system_administrator.md","helpnightfallai-nightfall-settings-role-based-access-control-system-administratormd","https://help.nightfall.ai/nightfall_settings/role_based_access_control/system_administrator.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/nightfall_settings/role_based_access_control/system_administrator.md).\n\n# System Administrator Role\n\nUsers with the System administrator role have access to the whole Nightfall application. There is no restricted resource from the system administrator user. Users with System adminstrator roles can create API keys for Firewall for AI. They can also add or remove users from the Nightfall app and edit a user's current role. System administrators also have full access to the Nightfall settings configurations. \n\nThe Nightfall app view for a user with this role is as shown in the following image. \n\n

\n\n## Permissions Associated with System Administrator Role\n\nA user with the System Administrator role can perform all the tasks as in case of a [Security Operations Manager Role](/nightfall_settings/role_based_access_control/security_operations_manager.md). Additionally, the following tasks can also be performed. \n\n### Firewall for AI Keys\n\nWith the **API Keys** permission, users can create new API keys and delete existing API keys. Users can also view or regenerate the webhook signing key. \n\n

\n\n### User Management\n\nWith the User Management permission, users can add, edit or delete users from the Nightfall app. Admin users can also modify the roles of existing users. \n\n

\n\n### Alert Management\n\nThe **alert management** permission allows users to configure alert platforms. These alert platforms can be used as notification channels while configuring integrations or creating policies for an integration.\n\n

\n\n### Directory Sync\n\nThe Directory Sync permission allows users to configure directory sync services to configure policies related to Google Drive and Microsoft. \n\n

\n\n### Billing\n\nThe Billing page allows users to view their current plan and other details related to the current plan. Users can also view the integrations also view the Nightgall products being used by the organization. \n\n

\n\nAs mentioned above, apart from the above permissions, administrator user has access to all the other sections of Nightfall app which are accessible to a user with the [Security Operations Manager Role](/nightfall_settings/role_based_access_control/security_operations_manager.md). \n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/nightfall_settings/role_based_access_control/system_administrator.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:35:31.790Z","2026-08-04T18:36:36.200Z","d7417123-b347-4960-85a7-9a57bd8988ff",[],[],[],"help.nightfall.ai / nightfall_settings / role_based_access_control / security_operations_manager.md","helpnightfallai-nightfall-settings-role-based-access-control-security-operations-managermd","https://help.nightfall.ai/nightfall_settings/role_based_access_control/security_operations_manager.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/nightfall_settings/role_based_access_control/security_operations_manager.md).\n\n# Security Operations Manager Role\n\nThe Security Operations Manager role allows users to view Dashboards and create reports, view and create custom detectors, work on various Nightfall integrations, handle DLP violations, exfiltration, and Posture Management events, and create and edit policies. \n\nThe Nightfall app view for a user with this role is as shown in the following image. \n\n

\n\n## Permissions Associated with Security Operations Manager Role\n\nA user with Security Operations Manager Role has the following permissions.\n\n### View Dashboard and Create Reports\n\nWith the **Dashboard** and **Reportin**g permissions, users to view data on the Dashboard, apply filters to the dashboard data, and also generate reports from the Dashboard data. \n\n

\n\n### Take Actions on DLP Violations\n\nWith the **DLP Violations** permission, users can take appropriate actions on the DLP violations. They can also share the violation data and export it as a CSV file.\n\n

\n\n### View the DLP Violations Content \n\nWith the **Content Preview** permission, users can preview the content of the DLP Violations page. The sensitive data is not redacted for this role.\n\n

\n\n### Exfiltration/Posture Management and Encryption Events\n\nWith the **Exfiltration** permission, users can filter event data, share event data, view historic events data, and take actions on Posture management, Exfiltration, and encryption events. \n\n

\n\n### Detectors\n\nWith the **Detectors** permission, users can view all the detectors, view detectors that belong to a specific category, filter the list of detectors, search a detector, and copy the UUID of a detector. Users with this role can also create custom detectors.\n\n

\n\n### Detection Rules\n\nWith the **Detection Rules** Permission, users can view and modify detection rules. Furthermore, this permission also allows users to create new detection rule and add detectors to it. \n\n

\n\n### Policies\n\nThe **DLP policies** permission allows users to create, edit, and delete the DLP policies. The **Exfiltration/Posture management** permission allow users to create, edit, and delete the exfiltration, Posture management, and Firewall for AI policies. Users can also search and filter policies. \n\n

\n\n### App Management and App Alert Management\n\nWith the **App management** permission, users can manage connections to various existing Nightfall integrations and create new instance of connections with Nightfall integrations. With the **App Alert Management** permission, users can add, edit, or delete notification channels for each integration. \n\n

\n\n## Permissions Associated with Security Events Manager Role\n\nA user with Security Events Manager Role has the following permissions.\n\n### View Dashboard and Create Reports\n\nWith the **Dashboard** and **Reportin**g permissions, users to view data on the Dashboard, apply filters to the dashboard data, and also generate reports from the Dashboard data. \n\n

\n\n### View the DLP Violations Content\n\nWith the **Content Preview** permission, users can preview the content of the DLP Violations page. The sensitive data is not redacted for this role.\n\n

\n\n{% hint style=\"info\" %}\n\n1. The main point of difference between the Security analyst role and the Security events manager role is that users with the Security analyst role can view redacted content of DLP violations page.However, content is not redacted for the Security Events manager role. \n2. The common feature between a user with Security analyst role and a user with Security events manager role is that the download button on the Events detail view page is active for both. However, they cannot downlaod files containing sensitive data. \n {% endhint %}\n\n### Exfiltration/Posture Management and Encryption Events\n\nWith the **Exfiltration** permission, users can filter event data, share event data, view historic events data, and take actions on Posture management, Exfiltration, and encryption events. \n\n

\n\n### View Detectors\n\nWith the **Detectors** permission, users can view all the detectors, view detectors that belong to a specific category, filter the list of detectors, search a detector, and copy the UUID of a detector. \n\n

\n\n## Permissions Associated with Security Analyst Role\n\nA user with Security Analyst Role has the following permissions\n\n### View Dashboard and Create Reports\n\nWith the **Dashboard** and **Reportin**g permissions, users to view data on the Dashboard, apply filters to the dashboard data, and also generate reports from the Dashboard data. \n\n

\n\n### Preview the DLP Violations Content\n\nWith the **Content Preview** permission, users can preview the content of the DLP Violations page. The sensitive data is redacted. Also, Security analysts cannot download the file containing sensitive data (even if the download button is active).\n\n

\n\n{% hint style=\"info\" %}\nThe main point of difference between the Security analyst role and the Security events manager role is that users with the Security analyst role can view redacted content of DLP violations page. However, content is not redacted for users with the Security Events manager role. \n{% endhint %}\n\n### Exfiltration/Posture Management and Encryption Events\n\nWith the **Exfiltration** permission, users can filter event data, share event data, view historic events data, and take actions on Posture management, Exfiltration, and encryption events. \n\n

\n\n## Permissions Associated with Policy Manager Role\n\nA user with Policy Manager Role has the following permissions.\n\n### App Management and App Alert Management\n\nWith the **App management** permission, users can manage connections to various existing Nightfall integrations and create new instance of connections with Nightfall integrations. With the **App Alert Management** permission, users can add, edit, or delete notification channels for each integration. \n\n### Detectors\n\nWith the **Detectors** permission, users can view all the detectors, view detectors that belong to a specific category, filter the list of detectors, search a detector, and copy the UUID of a detector. Users with this role can also create custom detectors.\n\n

\n\n2. Click the **Users & roles** tab.\n\n

\n\nYou can view the list of Users and the roles assigned to each user. \n\n

\n\nClick the **Roles** tab to access the Roles page.\n\n

\n\nThe Roles page displays the Role name, Permissions assigned to a role and the number of users to whom the role is assigned, as shown in the following image.\n\n

\n\nYou can click the **View permission details** button to expand the complete list of permissions associated with a Role.\n\n

\n\n{% hint style=\"warning\" %}\nCurrently, you can assign only a maximum of one role to a user. Also, you cannot create custom Roles and must use the out of the box Roles provided by Nightfall.\n{% endhint %}\n\n## Roles and Permissions\n\nNightfall provides you with five Roles. Each of the five Roles is associated with multiple permissions. The following table lists each role and the permissions associated with the Role. \n\n| Role | Permissions |\n| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Security Analyst |

|\n| Policy Manager |

|\n| Security Events Manager |

|\n| Security Operations Manager |

|\n| System Administrator |

|\n\nYou can learn more about each of the role from the following links.\n\n[Security Analyst Role](/nightfall_settings/role_based_access_control/security_analyst.md)\n\n[Policy Manager Role](/nightfall_settings/role_based_access_control/policy_manager.md)\n\n[Security Events Manager Role](/nightfall_settings/role_based_access_control/security_events_manager.md)\n\n[Security Operations Manager Role](/nightfall_settings/role_based_access_control/security_operations_manager.md)\n\n[System Administrator Role](/nightfall_settings/role_based_access_control/system_administrator.md)\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/nightfall_settings/role_based_access_control.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:31:21.242Z","2026-08-04T18:32:18.243Z","b647dcca-53b2-48b9-bf95-e2ef6441802c",[],[],[],"help.nightfall.ai / nightfall_settings / directory_sync / okta.md","helpnightfallai-nightfall-settings-directory-sync-oktamd","https://help.nightfall.ai/nightfall_settings/directory_sync/okta.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/nightfall_settings/directory_sync/okta.md).\n\n# Add Okta to Nightfall\n\nThis document explains the process of adding your Okta tenant to Nightfall to enable Directory Sync. Once you add Okta to Nightfall, you can sync users and user groups data from your Okta account to Nightfall. To get an overview of the Directory Sync feature in Nightfall, you can read [this article](/nightfall_settings/directory_sync.md) and then proceed with this document. \n\nIn this document you are basically authorizing the Nightfall application in Okta. The authorization process involves two steps. In the first step, you authorize the Nightfall app in the Okta console. This process generates an Okta domain, client ID and client secret. You must copy these values. In the second step, you must paste these values in the Nightfall console to complete the process. \n\n## Prerequisites\n\n- You must have admin access to your Okta account. \n\n## Integrating Nightfall in Okta\n\n1. Log in to your Okta account with admin credentials and navigate to the admin console. \n2. In the left pane, expand **Applications** and select **API Service Integrations**.\n\n

\n\n3. Click **Add Integration**.\n4. Select the **Nightfall AI** integration. \n\n

\n\n5. Click **Install & Authorize**.\n\n

\n\n6. The client secret is generated. Click **Copy to clipboard** and store this secret securely. You cannot view this secret again. \n7. Click **Done**. \n\n

\n\n7. Copy the values in the **Okta Domain** and **Client ID** fields. \n\n

\n\n## Configuring Okta in Nightfall\n\n1. Log in to your Nightfall console.\n2. In the left pane, click the **Settings** menu.\n3. Click the **Directory Sync** tab.\n\n

\n\n4. Click **Add directory**. \n\n

\n\n{% hint style=\"info\" %}\nIf you have already created IdP with Google Workspace or Microsoft Entra, you can view the list of IdP(s). In this case, you must click the **+ Add Directory** button. \n{% endhint %}\n\n5. Click **Set up** on the Okta widget. \n\n

\n\n6. Paste the **Okta Domain**, **Client ID,** and **Client Secret** values, obtained in the previous section. \n7. Click **Connect** (This button is activated only after you enter the values as mentioned in the previous step).\n\n

\n\n6. A dialogue box with successful connection message is displayed. Click **Finish** to complete the process. \n\n

\n\nYou can view the connection details as shown in the following image. Click **+ Add directory** to authorize the Nightfall app on additional Okta domains. \n\n \n\n

\n\n3. Click **Add Directory**. \n\n

\n\n4. Select **Azure Entra** as the identity provider. \n\n

\n\n5. Click **Connect**. \n\n

\n\n6. Enter Email or phone number associated with your Microsoft Azure account. \n7. Click **Next**.\n\n

\n\n8. Enter your password and click **Sign In.**\n\nWhen you sign in as an Azure admin, you can consent the installation of Nightfall IDP yourself. You can view the following screen. You must click **Accept**. \n\n

\n\nOnce you approve the request, the installation proceeds. Once the installation is completed, you can see the following screen. You must click **Setup Complete**.\n\n

\n\nAfter the setup is complete, the first sync may take 15 to 30 min to complete. While the first sync is in progress you would see \"pending\" under status. Once the sync is complete, the status would transition from \"pending\" to \"synced\" and you can view the number of active users, inactive users and groups discovered. \n\n

\n\n{% hint style=\"info\" %}\nActive users in Azure are the users who actively log in to Azure and perform various tasks. \n\nInactive users are dormant users who have not logged in to their Azure account for a while. You can refer to this [Microsoft document](https://learn.microsoft.com/en-us/entra/identity/monitoring-health/howto-manage-inactive-user-accounts) to learn more about managing inactive users.\n{% endhint %}\n\nNightfall syncs with your Identity and Access Provider every four hours. Also, you can manually sync once every hour. To sync data manually, click the ellipsis menu and select **Refresh.**\n\n

\n\nCurrently, once registered you cannot unregister an Identity and Access Provider from Nightfall. If you do wish to unregister your Identity and Access Provider, please contact Nightfall support.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/nightfall_settings/directory_sync/microsoft_entra_id.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:37:41.872Z","2026-08-04T18:38:26.991Z","865ed4ae-8c75-4d64-ab6a-49abd3979129",[],[],[],"help.nightfall.ai / nightfall_settings / directory_sync.md","helpnightfallai-nightfall-settings-directory-syncmd","https://help.nightfall.ai/nightfall_settings/directory_sync.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/nightfall_settings/directory_sync.md).\n\n# Directory Sync\n\nThis document explains how to integrate Nightfall with your identity providers (IdPs) like Microsoft Entra ID, Google Workspace Directory, and Okta Service. This integration simplifies policy management in Nightfall allowing you to include or exclude users and user groups, by leveraging existing user information for easier administration within Nightfall and other SaaS products.\n\n## Advantages of Integration\n\n- **Simplified Policy Management**: Nightfall automatically synchronises user and group information from your IDps, eliminating the need for manual user inclusions or exclusions in policies. This continuous sync ensures your policies always reflect the latest user directory information, streamlining management and reducing administrative overhead.\n- **Tailored Policies with User Groups**: Leverage existing user groups defined in your IdPs to easily create granular DLP policies within Nightfall. Assign specific access and permission levels to different user groups, ensuring data security and compliance across various SaaS applications like Microsoft Teams, OneDrive, and Google Drive.\n- **Dynamic User Management**: As users are added or removed from your IdP directory, Nightfall automatically reflects these changes, updating your DLP policies. This ensures your policies remain accurate and relevant, eliminating the need for manual updates.\n\n## Configuring Directory Sync\n\nThe Directory Sync feature allows you to connect your user directories (Microsoft Entra ID and Google Workspace) with Nightfall. This sync is essential for enabling functionalities within Nightfall's SaaS apps like Microsoft 365 Teams, OneDrive for Business, Google Drive, and other apps.\n\n- **Microsoft Teams Direct Message Monitoring (Azure Entra ID):** To monitor direct messages in Microsoft Teams for potential data leaks, Nightfall requires access to your Microsoft Entra ID account. Syncing your Entra ID account grants Nightfall a list of active users and groups, facilitating the monitoring of user communication and data flow.\n- **OneDrive for Business**: To monitor user OneDrive for potentially sensitive data leaks Nightfall requires access to your Microsoft OneDrive for Business account. Syncing your Entra ID account grants Nightfall a list of active users and groups, facilitating the monitoring of user One Drives.\n\n**Supported Identity Providers**\n\nNightfall currently integrates with the following IDps:\n\n- [Microsoft Entra ID](/nightfall_settings/directory_sync/microsoft_entra_id.md)\n- [Google Workspace Directory Service](/nightfall_settings/directory_sync/google_workspace.md)\n- [Okta ](https://help.nightfall.ai/nightfall-ai/nightfall-settings/directory-sync/adding-okta-to-nightfall)\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/nightfall_settings/directory_sync.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:32:59.076Z","2026-08-04T18:32:59.113Z","9942b9ff-a77b-49a0-9eb7-9695e68b1972",[],[],[],"help.nightfall.ai / nightfall_settings / directory_sync / google_workspace.md","helpnightfallai-nightfall-settings-directory-sync-google-workspacemd","https://help.nightfall.ai/nightfall_settings/directory_sync/google_workspace.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/nightfall_settings/directory_sync/google_workspace.md).\n\n# Google Workspace Directory Service\n\nThis document explains the process of adding your Google Workspace tenant to Nightfall to enable Directory Sync. Once you add Google Workspace to Nightfall, you can sync users and user groups data from Google Workspace to Nightfall. To get an overview of the Directory Sync feature in Nightfall, you can read [this article](/nightfall_settings/directory_sync.md) and then proceed with this document. \n\nTo install Google Directory:\n\n1. Click the **Settings** button in Nightfall. \n\n

\n\n2. Click the **Directory Sync** tab.\n\n

\n\n3. Click **Add directory**. \n\n

\n\n4. Select **Google Workspace** as the identity provider. \n\n

\n\n5. Copy the **Client ID** and **OAuth Scope ID**. Store these values in a secure place. You require them in the further steps. \n\n

\n\n6. Login to your Google Workspace with an admin account.\n7. Click the menu icon.\n8. Select **Admin**.\n\n

\n\n9. In the Admin console left pane, expand **Security** and then expand **Access and data control**.\n10. Click **API controls**.\n\n

\n\n11. Click **MANAGE DOMAIN WIDE DELEGATION** under **Domain wide delegation**.\n\n

\n\n12. Click **Add New**.\n\n

\n\n13. Paste the **Client ID** copied from the Nightfall app, in the **Client ID** field.\n14. Paste the **Scopes ID** copied from the Nightfall app, under **OAuth Scope** field**.** Use comma to add multiple scope IDs. \n15. Click **AUTHORIZE.** \n\n

\n\n16. Return to the Nightfall app and click **Continue**.\n\n

\n\n17. Click **Connect**.\n\n

\n\nOnce the setup is completed, Nightfall displays the list of active and inactive users in your Google Workspace. Nightfall syncs with your Identity and Access Provider every four hours. Also, you can manually sync once every hour. To sync data manually, click the ellipsis menu and select **Refresh.**\n\n

\n\nCurrently, once registered you cannot unregister an Identity and Access Provider from Nightfall. If you wish to unregister your Identity and Access Provider, please contact Nightfall support.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/nightfall_settings/directory_sync/google_workspace.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:38:27.130Z","2026-08-04T18:39:45.193Z","3ea1cb2e-6652-4f3b-8b5d-aea7f438aeff",[],[],[],"help.nightfall.ai / nightfall_settings / customer-referral-program.md","helpnightfallai-nightfall-settings-customer-referral-programmd","https://help.nightfall.ai/nightfall_settings/customer-referral-program.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/nightfall_settings/customer-referral-program.md).\n\n# Customer Referral Program\n\nShare your love for Nightfall and earn rewards. You'll receive $1000 for each successful referral. \n\n**How It Works:** \n\nHave a friend or colleague who could benefit from modern, all-in-one data loss prevention? Here’s how you can both earn rewards:\n\n1. **Share the referral link**\n\nSpread the word by sharing our referral page via email or social media: \n\n[**https://www.nightfall.ai/referral**](https://www.nightfall.ai/referral)\n\n2. **Submit details** \n\nMake sure your referral includes your name, email, and company when they fill out the referral form.\n\n3. **Earn rewards**\n\nWhen your referral becomes a Nightfall customer, you’ll get a $1000 Visa gift card, and they’ll receive 10% off their first year with Nightfall.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/nightfall_settings/customer-referral-program.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:33:00.262Z","2026-08-04T18:33:00.291Z","0907d9b7-dca6-49d9-bcfc-7468653d947d",[],[],[],"help.nightfall.ai / nightfall_settings / custom-branding.md","helpnightfallai-nightfall-settings-custom-brandingmd","https://help.nightfall.ai/nightfall_settings/custom-branding.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/nightfall_settings/custom-branding.md).\n\n# Custom Branding\n\n## Overview\n\nAdd your organization's logo to all Nightfall email notifications by using the custom branding feature. After you upload your logo, it appears on:\n\n- Admin alert emails across all sensitive data protection, posture management and exfiltration prevention \n- End-user email notification about sensitive data exposure, posture or exfiltration prevention\n- Encrypted emails sent to recipients either via on-demand or automated encryption\n\n## Important notes\n\n- Once you upload a logo, custom branding is automatically enabled\n- To disable custom branding, delete your uploaded logo\n- When no custom logo is present, Nightfall's default logo appears on all emails\n\n## Add your organization's logo\n\n1. Select **Settings**\n2. Select the **Custom Branding** tab\n3. In the Custom Logo dialog box, select **Upload a logo**.\n4. Select your organization's logo file.\n5. Click **Save**.\n\nTo use the custom branding feature, you must upload your organization logo. Once you upload the logo, all the email notifications are delivered with the logo. You cannot disable this feature once you upload a logo. To disable this feature, you must delete the logo. Once you delete a logo, the Nightfall logo is appended to all the communication emails. \n\n
\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/nightfall_settings/custom-branding.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:32:59.401Z","2026-08-04T18:32:59.551Z","ab7002ba-6a22-4b3b-ab89-e687d80eafc7",[],[],[],"help.nightfall.ai / nightfall-for-anthropic-claude / policy-incidents.md","helpnightfallai-nightfall-for-anthropic-claude-policy-incidentsmd","https://help.nightfall.ai/nightfall-for-anthropic-claude/policy-incidents.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/nightfall-for-anthropic-claude/policy-incidents.md).\n\n# Policy Incidents\n\n- Violations appear on the **Detection & Response** page, filterable by `Channel = Claude (Compliance API)`.\n- Each incident shows the matching content (prompt text, completion text, or file content) with findings highlighted. Credentials are redacted with `████).`\n- Status is `IN_PROGRESS` until an analyst acts on the incident. This matches Nightfall's standard async-violation behavior.\n- The **Claude Activity** view shows admin events (logins, member changes, API-key creation, configuration changes) from your Claude organization. These events are written to the Nightfall audit log and forwarded to SIEM. They never appear as incidents.\n\n### Scope and limitations\n\nRead this section before deploying so expectations match reality.\n\n- **Monitor-only on this channel.** The Compliance API is post-hoc, so Nightfall sees content after it has been submitted to Claude. Inline pre-submit blocking on Claude is handled by the Nightfall endpoint agent on Claude Desktop, Claude Code, and the browser tab. (Link to endpoint-agent help doc.)\n- **Claude Enterprise only.** Claude Team plan is not exposed by the Compliance API.\n- **No model-inference coverage on the Claude Platform.** The Compliance API does not expose model-inference content. For real-time scanning and blocking on Claude Code (IDE and CLI), see the Nightfall AI Agent Security integration based on Claude Code Hooks and OpenTelemetry. (Link to AI Agent Security help doc.)\n- **No coverage of Claude on Amazon Bedrock or Google Vertex AI.**\n- **No ACL or permission graph.** Identity governance over Claude (who can access which project) lives with Okta and SailPoint.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/nightfall-for-anthropic-claude/policy-incidents.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:30:42.010Z","2026-08-04T18:30:42.036Z","0ec196c4-6c7e-488e-997f-2234b37b4711",[],[],[],"help.nightfall.ai / nightfall-for-anthropic-claude / nightfall-for-claude-enterprise-compliance-api.md","helpnightfallai-nightfall-for-anthropic-claude-nightfall-for-claude-enterprise-compliance-apimd","https://help.nightfall.ai/nightfall-for-anthropic-claude/nightfall-for-claude-enterprise-compliance-api.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/nightfall-for-anthropic-claude/nightfall-for-claude-enterprise-compliance-api.md).\n\n# Nightfall for Claude Enterprise (Compliance API)\n\nNightfall connects to your Claude Enterprise organization through Anthropic's Compliance API and treats Claude Enterprise as a monitored SaaS surface, the same way it treats Slack, Microsoft 365, Google Workspace, and the rest of your connectors. This is the fourth Claude surface Nightfall covers; the other three (described in Section 8) handle inline blocking and runtime audit. The Compliance API integration adds the server-side, organization-level monitor and audit layer.\n\n- Scans Claude Enterprise chat conversations and uploaded files for sensitive data: PII, PHI, PCI, secrets, source code, and any custom detector you have already built.\n- Surfaces violations in the standard Detection & Response page using existing policies and detection rules. No new console.\n- Monitor-only on this surface. Admin alerts (Slack, email, webhook, SIEM), optional end-user notification, and a full audit trail. The Compliance API is post-hoc, so no inline block is possible on this channel. Inline block on Claude continues to happen at the endpoint (Claude Desktop and the Claude web tab) and at the Hooks layer (Claude Code IDE and CLI). See Section 8.\n- Coverage scope of _this_ integration, explicitly: Claude Enterprise chat conversations and uploaded files only. Not Claude Team. Not Claude on Bedrock or Vertex AI. Not model-inference content delivered through the Claude Platform. (Nightfall's runtime Claude coverage, listed in Section 8, handles the surfaces this integration does not.)\n\n### Prerequisites\n\n- Claude Enterprise plan with admin access to the Claude admin console.\n- A Nightfall account with Detection & Response enabled.\n- A Compliance Access Key generated from the Claude admin console. See Anthropic's guide for generating one.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/nightfall-for-anthropic-claude/nightfall-for-claude-enterprise-compliance-api.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:30:41.600Z","2026-08-04T18:30:41.630Z","69a5b0d9-d1b3-4fce-b1c6-ffac2324c606",[],[],[],"help.nightfall.ai / nightfall-for-anthropic-claude / install-nightfall-for-claude-enterprise.md","helpnightfallai-nightfall-for-anthropic-claude-install-nightfall-for-claude-enterprisemd","https://help.nightfall.ai/nightfall-for-anthropic-claude/install-nightfall-for-claude-enterprise.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/nightfall-for-anthropic-claude/install-nightfall-for-claude-enterprise.md).\n\n# Install Nightfall for Claude Enterprise\n\n1. In Nightfall, go to **Integrations**, then **Add Integration**, then **Claude Enterprise**.\n2. Paste your Compliance Access Key from the Claude admin console. (Link out: Anthropic's article on generating a Compliance Access Key.)\n3. Confirm the OAuth scopes Nightfall requests:\n 1. `compliance:conversations:read`\n 2. `compliance:files:read`\n 3. `compliance:projects:read`\n 4. `compliance:audit_logs:read`\n\n`[verify]` Exact scope names with Anthropic before publishing this section. Tracked as Phase 0 open question 1 in the PRD.\n\n4. Choose the content surfaces you want in scope:\n 1. Conversation messages (user prompts and assistant completions)\n 2. Uploaded files\n5. Save the connector. Confirm status reads `healthy`. First ingest begins immediately.\n\nIf the status reads `degraded`, `failed`, or `rate_limited`, click **Reconnect** and re-grant. If the failure persists, contact Nightfall support.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/nightfall-for-anthropic-claude/install-nightfall-for-claude-enterprise.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:30:41.741Z","2026-08-04T18:30:41.780Z","38e76c45-d64e-48c4-bb27-561e12a06dca",[],[],[],"help.nightfall.ai / nightfall-for-anthropic-claude / configure-policies-for-claude-enterprise.md","helpnightfallai-nightfall-for-anthropic-claude-configure-policies-for-claude-enterprisemd","https://help.nightfall.ai/nightfall-for-anthropic-claude/configure-policies-for-claude-enterprise.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/nightfall-for-anthropic-claude/configure-policies-for-claude-enterprise.md).\n\n# Configure Policies for Claude Enterprise\n\n### Create a Detection & Response policy for Claude\n\n1. Go to **Detection & Response**, then **Policies**, then **New Policy**.\n2. Set **Channel = Claude (Compliance API)**.\n3. Pick detection rules from your existing library: PII, PHI, PCI, secrets, source code, custom regex, or custom named-entity detectors.\n4. Optional: scope by Claude user email or Claude project ID. Empty scope means all users and all projects in the connected Claude organization.\n5. Configure actions:\n\n- **Alert admin:** Slack, email, webhook, SIEM destinations (same set as your other connectors).\n - **Notify end user:** optional.\n - **Tag for review:** optional.\n - **Block** is not available on this channel. The UI explains why and links to the Nightfall endpoint agent for inline blocking on Claude Desktop, Claude Code, and the Claude browser tab.\n\n6. Save the policy. It begins matching against newly ingested Claude content within one polling cycle.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/nightfall-for-anthropic-claude/configure-policies-for-claude-enterprise.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:30:41.880Z","2026-08-04T18:30:41.906Z","73ee32e0-a070-41ba-9335-79b91a73288b",[],[],[],"help.nightfall.ai / nightfall-for-anthropic-claude / comprehensive-claude-coverage.md","helpnightfallai-nightfall-for-anthropic-claude-comprehensive-claude-coveragemd","https://help.nightfall.ai/nightfall-for-anthropic-claude/comprehensive-claude-coverage.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/nightfall-for-anthropic-claude/comprehensive-claude-coverage.md).\n\n# Comprehensive Claude Coverage\n\n### Comprehensive Claude coverage - the other three Nightfall integrations\n\nThese are separate Nightfall products and integrations, not the Compliance API. Together with this integration, they give a Claude customer end-to-end coverage with one set of detection rules and one console.\n\n| Surface | Integration | What it does | Enforcement |\n| ------------------------------------------ | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- |\n| Claude Desktop, Claude web tab | **Nightfall endpoint agent** | Scans file uploads and clipboard pastes for sensitive content; runs Lineage Source Tracking so a corporate Google Drive, SharePoint, or GitHub origin is recognized | **Inline block** (pre-submit) |\n| Claude Code (IDE and CLI) | **Nightfall AI Agent Security (Hooks)** | Scans prompts, MCP tool calls, tool responses, and shell commands; detects secrets, PII, PCI, PHI, IP, and prompt injection | **Inline block** (real-time) |\n| Claude Cowork | **Nightfall AI Agent Security (OpenTelemetry)** | Session-level audit trail of cost, token usage, and tool invocations exported over OTel | **Audit** (session-level) |\n| Claude Enterprise chats and uploaded files | **Claude Compliance API integration** _(this doc)_ | Server-side scan of chat conversations and uploaded files; runs the same detector set used everywhere else in Nightfall | **Monitor + audit** (post-hoc, org-wide) |\n\nPick the integration that matches the control you need. Most customers run all four: the endpoint agent and Hooks layer block before sensitive data reaches Claude on the surfaces where blocking is possible; the OpenTelemetry trail audits Claude Cowork sessions; and this Compliance API integration adds the server-side, organization-level record that compliance and SOC teams can pull for SOX, HIPAA, and SOC 2 evidence regardless of which device, project, or workspace the activity originated from. All four feed the same Detection & Response policy library and surface incidents in the same workflow.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/nightfall-for-anthropic-claude/comprehensive-claude-coverage.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:30:42.136Z","2026-08-04T18:30:42.169Z","092f669e-74bd-4367-a9c8-fa756650571b",[],[],[],"help.nightfall.ai / microsoft-exchange / getting_started.md","helpnightfallai-microsoft-exchange-getting-startedmd","https://help.nightfall.ai/microsoft-exchange/getting_started.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/microsoft-exchange/getting_started.md).\n\n# Getting Started\n\nNightfall DLP for Microsoft Exchange Online (aka Microsoft Exchange) offers a cloud-native data leak protection solution that monitors presence of sensitive data in MS Outlook. \n\nNightfall DLP for Exchange provides a seamless approach to monitor emails sent using Microsoft Outlook. Nightfall DLP scans messages in the mails for sensitive data. Additionally, Nightfall also allows notifications to be sent to the Nightfall administrators and Exchange users thus enabling them to take follow up steps in alignment with the organization's requirements. \n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/microsoft-exchange/getting_started.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:16:30.697Z","2026-08-04T17:16:30.722Z","f56b05a5-f250-4ace-8781-6e1b5281746f",[],[],[],"help.nightfall.ai / microsoft-exchange / exchange_online.md","helpnightfallai-microsoft-exchange-exchange-onlinemd","https://help.nightfall.ai/microsoft-exchange/exchange_online.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/microsoft-exchange/exchange_online.md).\n\n# Nightfall for Microsoft Exchange\n\nNightfall for Microsoft Exchange prevents sensitive content that is shared through Microsoft Outlook. Sensitive information and specific types of data like social security numbers, credit card numbers, or passwords are scanned and prevented from unintentional leakage.\n\nNightfall for Microsoft Exchange scans all data that is exchanged over emails and prevents sensitive information (such as credit card numbers or health records) from being leaked. \n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/microsoft-exchange/exchange_online.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:16:31.736Z","2026-08-04T17:16:31.773Z","0f8397ff-4cd5-45b8-94d8-dc6efeb8dfa4",[],[],[],"help.nightfall.ai / microsoft-exchange-1 / getting_started.md","helpnightfallai-microsoft-exchange-1-getting-startedmd","https://help.nightfall.ai/microsoft-exchange-1/getting_started.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/microsoft-exchange-1/getting_started.md).\n\n# Getting Started\n\nNightfall DLP for Microsoft SharePoint offers a cloud-native data leak protection solution that monitors presence of sensitive data in MS SharePoint. \n\nNightfall DLP for SharePoint provides a seamless approach to monitor your data in Microsoft SharePoint. Nightfall DLP scans content in SharePoint for sensitive data. Additionally, Nightfall also allows notifications to be sent to the Nightfall administrators and SharePoint users thus enabling them to take follow up steps in alignment with the organization's requirements. \n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/microsoft-exchange-1/getting_started.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:16:32.236Z","2026-08-04T17:16:32.266Z","b8ce07b3-dc09-4e7d-b3bc-117e3fc8b975",[],[],[],"help.nightfall.ai / microsoft-365 / onedrive.md","helpnightfallai-microsoft-365-onedrivemd","https://help.nightfall.ai/microsoft-365/onedrive.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/microsoft-365/onedrive.md).\n\n# Nightfall for OneDrive\n\nNightfall for OneDrive allows you to monitor your files and folders in the Microsoft OneDrive application. You can use this integration to check if any sensitive data exists in your OneDrive account. If sensitive data is found, you can configure appropriate steps to secure your OneDrive. \n\n## Prerequisites to Monitor OneDrive\n\nAs a prerequisite, to use the Nightfall for OneDrive integration, you must configure the Directory Sync feature in Nightfall. This configuration fetches details of users in your Azure Entra account and the default OneDrives associated with each user which can be monitored by Nightfall. To learn more about configuring the Directory Sync feature, you can refer to [this document](https://help.nightfall.ai/nightfall-ai/nightfall-settings/directory-sync/adding-microsoft-entra-id-to-nightfall).\n\n## Configuring OneDrive App\n\nOnce you set up the Directory Sync feature, you must configure the OneDrive app. The Steps for the same are as follows. \n\n1. Navigate to **Microsoft 365** integration under **My Integrations**.\n\n

\n\n2. Click **+ Add Tenant**. \n\n

\n\n3. Click **Connect** to initiate the authentication of your Microsoft Azure Entra account.\n\n

\n\n4. Enter your Azure login credentials. \n5. Click **Accept**. \n\n

\n\n6. Ensure that the Teams check box is selected. If you wish to use Microsoft for OneDrive, you can also select the check box for OneDrive. \n7. Click Save **Changes**.\n\n

\n\n8. Click **Finish.**\n\n

\n\nYou can see that the apps selected in step 6 (Teams, OneDrive) are now connected. \n\n

\n\nIf you have not connected either the OneDrive or the Teams application in step 6, the **Connect** button is displayed against the app. You can click the **Update App Selection** button to connect to the app. \n\n

\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/microsoft-365/onedrive.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:15:44.137Z","2026-08-04T17:16:30.166Z","70bd279d-0215-4c4e-aa60-38bbf9b138ed",[],[],[],"help.nightfall.ai / microsoft-365 / microsoft_teams.md","helpnightfallai-microsoft-365-microsoft-teamsmd","https://help.nightfall.ai/microsoft-365/microsoft_teams.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/microsoft-365/microsoft_teams.md).\n\n# Nightfall for Microsoft Teams\n\nNightfall for Microsoft Teams prevents sensitive content that is shared through Microsoft Teams. Sensitive information and specific types of data like social security numbers, credit card numbers, or passwords are scanned and prevented from unintentional leakage.\n\nNightfall for Microsoft Teams scans all messages and documents that are exchanged over Channels (Private, Public, and Shared) and prevents sensitive information (such as credit card numbers or health records) from being leaked. Scans will include archived items, but not deleted items.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/microsoft-365/microsoft_teams.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:15:43.134Z","2026-08-04T17:15:43.170Z","721b2274-a40e-4d6d-b076-bfc0875194bf",[],[],[],"help.nightfall.ai / microsoft-365 / getting_started.md","helpnightfallai-microsoft-365-getting-startedmd","https://help.nightfall.ai/microsoft-365/getting_started.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/microsoft-365/getting_started.md).\n\n# Getting Started\n\nNightfall DLP for Microsoft 365 (M365) offers a cloud-native data leak protection solution that monitors presence of sensitive data across the following M365 services - Exchange Online, Sharepoint Online, OneDrive for Business, and MS Teams. \n\nNightfall DLP for M365 provides a seamless approach to monitor User OneDrives, Teams Channels and Teams Chats. Nightfall DLP scans messages in Team channels / chats and scans files in user's OneDrives. Further, Nightfall also allows notifications to be sent to the Nightfall administrators and M365 users and enables them to take followup steps in alignment with the organization's requirements. \n\nThe following steps need to be completed to enable Nightfall DLP workflows for OneDrive for Business and MS Teams,\n\n1. Setup of directory sync, and\n2. Registration of the M365 endpoint with Nightfall\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/microsoft-365/getting_started.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:15:42.752Z","2026-08-04T17:15:42.777Z","228a9a7d-85f1-4034-a814-45b7c49ccbc8",[],[],[],"help.nightfall.ai / llms.txt","helpnightfallai-llmstxt","https://help.nightfall.ai/llms.txt","# Nightfall Documentation\n\n## Data Detection and Response\n\n- [Welcome to Nightfall Documentation](https://help.nightfall.ai/welcome-to-nightfall-documentation.md): Nightfall Documentation landing page\n- [Release Notes 2025-2026](https://help.nightfall.ai/release_notes/nightfall_new_features.md): This document lists all the features released by Nightfall in 2025 and 2026.\n- [Release Notes 2021-2024](https://help.nightfall.ai/release_notes/release_notes_old.md): Nightfall Release Notes for the features released in 2024, 2023, 2022, and 2021.\n- [Why Cloud DLP?](https://help.nightfall.ai/nightfall_introduction/cloud_dlp.md): Advantages of a Cloud DLP and introduction to Nightfall cloud DLP\n- [Introduction to Nightfall](https://help.nightfall.ai/nightfall_introduction/nightfall_overview.md): An introduction to the Nightfall Cloud DLP\n- [Nightfall Overview](https://help.nightfall.ai/nightfall_introduction/overview.md): Learn more about Nightfall Cloud DLP from this brief document\n- [Cloud-native DLP vs. CASB](https://help.nightfall.ai/nightfall_introduction/cloud_dlp_casb.md): A comparison between Cloud-native DLP and CASB\n- [How Nightfall Works](https://help.nightfall.ai/nightfall_introduction/overview_nightfall.md): Learn more about the Nightfall Cloud DLP\n- [Reasons to Choose Nightfall](https://help.nightfall.ai/nightfall_introduction/why_choose_nightfall.md): Understand the reasons to choose Nightfall DLP.\n- [Benefits of Nightfall](https://help.nightfall.ai/nightfall_introduction/benefits.md): Learn how Nightfall benefits your organization\n- [How Nightfall Fits into Compliance Frameworks](https://help.nightfall.ai/nightfall_compliance/compliance_with_nightfall.md): Learn how Nightfall AI-powered data leak prevention (DLP) for SaaS and Cloud can help organizations maintain compliance with various global compliance frameworks across different industries.\n- [ISO 27001 Compliance + DLP](https://help.nightfall.ai/nightfall_compliance/iso-27001.md): Learn more about ISO 27001 and how Nightfall helps you with it.\n- [SOC 2 Compliance + DLP](https://help.nightfall.ai/nightfall_compliance/soc2.md): Learn more about SOC 2 compliance and how Nightfall helps with it.\n- [PCI Compliance + DLP](https://help.nightfall.ai/nightfall_compliance/pci.md): Learn more about PCI compliance and how Nightfall helps with it.\n- [PHI Detector - More on Nightfall's HIPAA Compliance Detector](https://help.nightfall.ai/nightfall_compliance/phi_hipaa.md): Learn how to ensure HIPAA compliance in your collaborative cloud applications\n- [Installing Nightfall](https://help.nightfall.ai/get_started/installation.md): Learn how to onboard and start using the Nightfall AI platform.\n- [Overview](https://help.nightfall.ai/detection_platform/overview.md): An introduction to the Nightfall Detection Platform.\n- [Detectors](https://help.nightfall.ai/detection_platform/detectors.md): Learn about Nightfall detectors.\n- [Choosing a Nightfall Detector](https://help.nightfall.ai/detection_platform/choosing_detectors.md): Learn about various factors to be considered while choosing a Nightfall detector.\n- [Compliance Use Cases](https://help.nightfall.ai/detection_platform/choosing_detectors/compliance_use_cases.md): Organizational compliance is one of the leading drivers that require DLP tooling such as Nightfall. These are the recommended configurations for each compliance framework.\n- [Data Protection Use Cases](https://help.nightfall.ai/detection_platform/choosing_detectors/data_protection_use_cases.md): Organizations may need to protect specific data types either by contractual obligation or to protect intellectual property. These are the recommended configurations to protect these data types.\n- [Nightfall Detector Glossary](https://help.nightfall.ai/detection_platform/detection_glossary.md): Learn about the various out-of-the-box detectors provided by Nightfall.\n- [Secrets Detection](https://help.nightfall.ai/detection_platform/detection_glossary/secrets_detection.md): Learn about Nightfall secret detection.\n- [Creating Custom Detectors](https://help.nightfall.ai/detection_platform/custom_detectors.md): Learn how to create custom detectors in Nightfall.\n- [Creating Dictionary Detector](https://help.nightfall.ai/detection_platform/custom_detectors/dictionary_detector.md): Learn how to create a Dictionary detector in Nightfall.\n- [Create File Type Detector](https://help.nightfall.ai/detection_platform/custom_detectors/file_type_detector.md): Learn how to create a File Type detector in Nightfall.\n- [Create File Fingerprint Detector](https://help.nightfall.ai/detection_platform/custom_detectors/file_fingerprint_detector.md): Learn how to create a File Fingerprint detector in Nightfall.\n- [Create Regular Expression Detector](https://help.nightfall.ai/detection_platform/custom_detectors/regexp_detector.md): Learn how to create a Regular Expression detector in Nightfall.\n- [Create Microsoft Purview Sensitivity Labels (MIP) detector](https://help.nightfall.ai/detection_platform/custom_detectors/create-microsoft-purview-sensitivity-labels-mip-detector.md): Scan Microsoft Purview Sensitivity Labels with Custom Regex Detectors\n- [Create an Entity Detector using a Prompt](https://help.nightfall.ai/detection_platform/custom_detectors/create-an-entity-detector-using-a-prompt.md): ⭐ Define a detector to detect custom sensitive entities using natural language instead of regex\n- [Create a Prompt-based File Classifier](https://help.nightfall.ai/detection_platform/custom_detectors/create-a-prompt-based-file-classifier.md): Define a file classifier using natural language. No training required.\n- [Extend a Nightfall Detector](https://help.nightfall.ai/detection_platform/custom_detectors/extend_nightfall_detector.md): Learn how you can extend the functionality of an existing Nightfall detector.\n- [Create Detection Rules](https://help.nightfall.ai/detection_platform/create_detection_rules.md): Learn the process of creating detection rules in Nightfall.\n- [Detection Platform Overview](https://help.nightfall.ai/detection_platform/overview_platform.md): Understand how detection works in Nightfall.\n- [Evaluating Detection](https://help.nightfall.ai/detection_platform/evaluate_nightfall_detection.md): Learn how to evaluate detection rules in Nightfall.\n- [Creating Policies](https://help.nightfall.ai/detection_platform/policies.md): Learn how to create policies in Nightfall.\n- [Selecting Integration](https://help.nightfall.ai/detection_platform/policies/integration.md)\n- [Scope of the Policy](https://help.nightfall.ai/detection_platform/policies/scope.md)\n- [Detection Rules](https://help.nightfall.ai/detection_platform/policies/detection_rules.md)\n- [Advanced Settings](https://help.nightfall.ai/detection_platform/policies/advanced_settings.md)\n- [Name and Risk Score](https://help.nightfall.ai/detection_platform/policies/risk_score.md)\n- [Historical Scan Detection Rules](https://help.nightfall.ai/detection_platform/historical_scan.md)\n- [Regex Library](https://help.nightfall.ai/detection_platform/regex_library.md): Regular expressions for unique situations\n- [Detection Platform FAQs](https://help.nightfall.ai/detection_platform/faq.md)\n- [How can I reduce false positives in my findings?](https://help.nightfall.ai/detection_platform/faq/reduce_false_positives.md): Tips for improving finding accuracy.\n- [What do different “Confidence Levels” mean?](https://help.nightfall.ai/detection_platform/faq/confidence_levels.md): Learn how Nightfall assigns confidence levels to sensitive data classifications.\n- [What file types will Nightfall scan for sensitive data? What are the limitations?](https://help.nightfall.ai/detection_platform/faq/file_types_scanned.md): Nightfall scans for sensitive data in a broad range of file types\n- [How do I use Context Rules?](https://help.nightfall.ai/detection_platform/faq/context_rules.md): Customize finding confidence to suit your business logic\n- [How do I use Exclusion Rules?](https://help.nightfall.ai/detection_platform/faq/exclusion_rules.md): Exclude certain tokens from detection to suit your business logic\n- [Does Nightfall have a regex library I can choose from?](https://help.nightfall.ai/detection_platform/faq/regex_library.md): Select from an aggregated library of regexes\n- [Why does Nightfall sometimes miss to report SSN, credit card number, and so on?](https://help.nightfall.ai/detection_platform/faq/report_ssn.md): Learn about typical cases of Nightfall\n- [Why does the Password Detector Report False Positive Zoom Password Findings?](https://help.nightfall.ai/detection_platform/faq/false_positive.md): Zoom Password Findings\n- [Detection Rules](https://help.nightfall.ai/nightfall_policy_templates/detection_rules.md): Use pre-defined templates to get started quickly with policies.\n- [Sample Datasets](https://help.nightfall.ai/nightfall_policy_templates/sample_data.md): Use sample data sets provided by Nightfall to test Nightfall's detection capabilities.\n- [Nightfall Dashboard](https://help.nightfall.ai/dashboard/overview.md): Learn how to use the Nightfall Dashboard.\n- [Data Detection and Response Events](https://help.nightfall.ai/dashboard/sdp_events.md): Learn about the Events page in Nightfall\n- [Filtering Events](https://help.nightfall.ai/dashboard/sdp_events/filtering.md): Filter Nightfall Events based on parameters.\n- [Event Filter Operators](https://help.nightfall.ai/dashboard/sdp_events/filter_operators.md): Learn more about the search operators provided by Nightfall, to filter Events.\n- [Applying Actions on Events](https://help.nightfall.ai/dashboard/sdp_events/event_actions.md): Learn how to apply actions on Nightfall Events.\n- [Applying Bulk Actions on Events](https://help.nightfall.ai/dashboard/sdp_events/bulk_actions.md): Learn how to apply bulk actions on Nightfall Events.\n- [Event Status](https://help.nightfall.ai/dashboard/sdp_events/status.md): Learn more about various status of Nightfall Events.\n- [Deduplication and Automatic Resolution of Events](https://help.nightfall.ai/dashboard/sdp_events/deduplication.md): This document explains the Deduplication and Auto resolve features for Nightfall Events.\n- [Nightfall Alert Platforms](https://help.nightfall.ai/nightfall_alert_platform/overview.md): Learn about the Nightfall alert platforms\n- [Setting up Slack as an Alert Platform](https://help.nightfall.ai/nightfall_alert_platform/alerting_to_slack.md): Learn how to use Slack as an alert platform in Nightall.\n- [Setting up Jira as an Alert Platform](https://help.nightfall.ai/nightfall_alert_platform/alerting_to_jira.md): Learn how to use Jira as an alert platform in Nightall.\n- [Setting up MS Teams as an Alert Platform](https://help.nightfall.ai/nightfall_alert_platform/alerting_to_ms_teams.md): Learn how to use MS Teams as an alert platform in Nightall.\n- [Playbook](https://help.nightfall.ai/operationalizing_nightfall_dlp/playbook.md): Learn how to operationalize NIghtfall Playbook.\n- [Informing & Coaching Business Users](https://help.nightfall.ai/operationalizing_nightfall_dlp/coach_users.md): Learn the process of informing and teaching users about Nightfall platform.\n- [Alert Management Guiding Principles](https://help.nightfall.ai/operationalizing_nightfall_dlp/alert_guiding_principles.md): Follow Nightfall's best practices for Alert Management and Remediation\n- [Integrating with Security Tools](https://help.nightfall.ai/operationalizing_nightfall_dlp/security_tools_integration.md): Learn how you can integrate Nightfall with various security tools.\n- [Integrating with SIEM](https://help.nightfall.ai/operationalizing_nightfall_dlp/security_tools_integration/siem.md): Learn how to integrate Nightfall with a SIEM or push violations downstream to any alert drain, SOAR tool, BI tool, and more.\n- [Integrating with Microsoft Sentinel](https://help.nightfall.ai/operationalizing_nightfall_dlp/security_tools_integration/siem/microsoft_sentinel.md): Learn how to integrate Nightfall with Microsoft Sentinel.\n- [Creating Dashboards for Nightfall Alerts in Splunk](https://help.nightfall.ai/operationalizing_nightfall_dlp/security_tools_integration/splunk.md): Learn how to start creating a dashboard of Nightfall alerts/actions in your Splunk Enterprise/Splunk Cloud environment.\n- [Creating Dashboards for Nightfall Alerts in Sumo Logic](https://help.nightfall.ai/operationalizing_nightfall_dlp/security_tools_integration/sumo_logic.md): Learn how to start creating a dashboard of Nightfall alerts/actions in your Sumo Logic environment.\n- [Sending Alerts to Microsoft Teams](https://help.nightfall.ai/operationalizing_nightfall_dlp/security_tools_integration/ms_teams.md): Learn how to configure Nightfall to send alerts to Microsoft Teams using email.\n- [Frequently Asked Questions (FAQs) for End-Users](https://help.nightfall.ai/operationalizing_nightfall_dlp/faqs_end_users.md): Nightfall FAQs for end-users\n- [Nightfall Integrations](https://help.nightfall.ai/nightfall_integrations.md): Links to all the Nightfall integrations\n- [Nightfall for Slack: Quick Start](https://help.nightfall.ai/slack/quickstart.md): Learn how to set up your integration with Slack so that you can scan and protect sensitive data across your Slack workspace.\n- [Getting Started With Nightfall for Slack](https://help.nightfall.ai/slack/getting_started.md): Get started with installing and integrating Nightfall for Slack.\n- [Requirements](https://help.nightfall.ai/slack/getting_started/requirements.md): Make sure the following requirements are fulfilled before you get started.\n- [Requirements for Nightfall DLP for Slack Enterprise](https://help.nightfall.ai/slack/getting_started/requirements/slack_enterprise.md): Understand the requirements for Nightfall DLP for Slack Enterprise.\n- [Requirements for Nightfall DLP for Slack Pro and Slack Business+](https://help.nightfall.ai/slack/getting_started/requirements/slack_pro.md): Understand the requirements for Nightfall DLP for Slack Pro.\n- [Installing Nightfall for Slack](https://help.nightfall.ai/slack/getting_started/install.md): Learn how to install Nightfall for Slack\n- [Installing Nightfall DLP for Slack Enterprise](https://help.nightfall.ai/slack/getting_started/install/slack_enterprise.md): Learn the process of installing Nightfall DLP for Slack enterprise.\n- [Installing Nightfall DLP for Slack Pro and Business+](https://help.nightfall.ai/slack/getting_started/install/slack_pro.md): Learn the process of installing Nightfall DLP for Slack Pro and Slack Business+.\n- [Configure Alerts for Slack](https://help.nightfall.ai/slack/integration_alerts.md): Learn the process of configuring alerts for Slack.\n- [Configuring Policies for Slack Pro and the Slack Business+ Editions](https://help.nightfall.ai/slack/slack_pro_policy.md): Learn how to configure Nightfall policies for Slack Pro and Slack Business+\n- [Slack Pro and Business+ App Selection](https://help.nightfall.ai/slack/slack_pro_policy/integration.md): Learn the process of selecting the Slack integration while creating a Nightfall policy.\n- [Configure Scope for Slack Pro and Slack Business+](https://help.nightfall.ai/slack/slack_pro_policy/scope.md): Learn the process of configuring the Scope in the Slack Pro and Business+ editions while creating a Nightfall policy.\n- [Configure Detection Rules for Slack Pro and Slack Business+](https://help.nightfall.ai/slack/slack_pro_policy/detection_rules.md): Learn the process of selecting the Detection rules in the Slack Pro and Business+ editions while creating a Nightfall policy.\n- [Configure Automated Actions in Slack Pro and Slack Business+](https://help.nightfall.ai/slack/slack_pro_policy/automated_actions.md): Learn the process of configuring automated actions in the Slack Pro and Business+ editions while creating a Nightfall policy.\n- [Configure Advanced Settings in Slack Pro and Slack Business+](https://help.nightfall.ai/slack/slack_pro_policy/advanced_settings.md): Learn the process of configuring the advanced settings in the Slack Pro and Business+ editions while creating a Nightfall policy.\n- [Risk Configuration in Slack DLP for Slack Pro and Slack Business+ Editions](https://help.nightfall.ai/slack/slack_pro_policy/policy_risk.md): Learn the process of configuring the Risk Score and naming the policy while creating a Nightfall policy for the Slack Pro and Slack Business+ editions.\n- [Manage Events for Slack](https://help.nightfall.ai/slack/slack_pro_policy/events.md): Learn how to handle Nightfall Events that were created as a result of sensitive data leak in the Nightfall for Slack Pro and Slack Business+ editions.\n- [Configuring Policies for the Slack Enterprise Edition](https://help.nightfall.ai/slack/enterprise_policy.md): Learn the process of creating of Nightfall policies for the Slack Enterprise edition.\n- [Slack App Selection](https://help.nightfall.ai/slack/enterprise_policy/integration.md): Learn the process of selecting the Slack Enterprise integration while creating a Nightfall policy.\n- [Configure Scope for Slack Enterprise](https://help.nightfall.ai/slack/enterprise_policy/scope.md): Learn the process of configuring the Scope section while creating a Nightfall policy for the Slack Enterprise edition.\n- [Select Detection Rules for Slack Enterprise](https://help.nightfall.ai/slack/enterprise_policy/detection_rules.md): Learn the process of selecting detection rules while creating a Nightfall policy for the Slack Enterprise edition.\n- [Configure Automated Actions in Slack Enterprise](https://help.nightfall.ai/slack/enterprise_policy/automated_actions.md): Learn the process of configuring automated actions while creating a Nightfall policy for the Slack Enterprise edition.\n- [Configure Advanced Settings for Slack Enterprise](https://help.nightfall.ai/slack/enterprise_policy/advanced_settings.md): Learn the process of configuring advanced settings while creating a Nightfall policy for the Slack Enterprise edition.\n- [Risk Configuration for Slack Enterprise](https://help.nightfall.ai/slack/enterprise_policy/risk_configuration.md): Learn the process of configuring the Risk Score and naming the policy while creating a Nightfall policy for the Slack enterprise edition.\n- [Manage Events for Slack Enterprise](https://help.nightfall.ai/slack/enterprise_policy/events.md): Learn how to handle Nightfall Events that were created as a result of sensitive data leak in the Slack Enterprise.\n- [FAQs](https://help.nightfall.ai/slack/slack-faqs.md)\n- [Can I redact sensitive message content in Slack?](https://help.nightfall.ai/slack/slack-faqs/redact_sensitive_data.md): Redacting Sensitive Messages in Slack\n- [Nightfall for Slack Pro vs Enterprise](https://help.nightfall.ai/slack/slack-faqs/pro_vs_enterprise.md): Understand the differences between Slack pro and Slack enterprise editions.\n- [Upgrading from Slack Pro to Enterprise](https://help.nightfall.ai/slack/slack-faqs/pro_vs_enterprise/upgrading-pro-to-enterprise.md): Learn how to migrate from Slack Pro to Slack Enterprise edition\n- [Can we customize the alert messages sent in Slack?](https://help.nightfall.ai/slack/slack-faqs/slack_alert_customization.md): Learn how to customize the alert messages sent in Slack alerts\n- [Can I Disable Detection in Private Channels or DMs?](https://help.nightfall.ai/slack/slack-faqs/detection_disable.md): Turn off the Nightfall bot in secure private communications\n- [What types of channels does Nightfall scan? Does Nightfall scan shared channels?](https://help.nightfall.ai/slack/slack-faqs/types_of_channels_scanned.md)\n- [I am unable to view a sensitive message or file from the Nightfall alert channel.](https://help.nightfall.ai/slack/slack-faqs/alert_message_blocked.md): Learn why you might not be able to view sensitive messages or files in Nightfall alert channel.\n- [Upon Slack installation, why am I seeing a 400 error mentioning a \"Restricted Action\"?](https://help.nightfall.ai/slack/slack-faqs/slack_400_error.md): Understand why Channel Management Restrictions in your Slack Workspace settings may be causing Slack 400 error.\n- [I send a sensitive message, edit it, and then admin applies the Redact action. What is the outcome?](https://help.nightfall.ai/slack/slack-faqs/multiple_actions.md): Learn what happens when both, end-user and admin apply action on sensitive data.\n- [How do I re-install Nightfall DLP for Slack Pro Edition?](https://help.nightfall.ai/slack/slack-faqs/reinstall_slack_pro.md): Learn the process of reinstalling Slack pro edition.\n- [How do I re-install Nightfall DLP for Slack Enterprise Edition?](https://help.nightfall.ai/slack/slack-faqs/reinstall_slack_enterprise.md): Learn the process of reinstalling Slack enterprise edition.\n- [Our Slack Admin has Quit. Will it impact Nightfall Scan?](https://help.nightfall.ai/slack/slack-faqs/our-slack-admin-has-quit.-will-it-impact-nightfall-scan.md)\n- [Getting Started](https://help.nightfall.ai/github/getting_started.md): Learn the basics of Nightfall DLP for GitHub.\n- [Requirements](https://help.nightfall.ai/github/getting_started/requirements.md): Make sure the following requirements are fulfilled before you get started with the installation of Nightfall DLP for GitHub.\n- [Install Nightfall for GitHub](https://help.nightfall.ai/github/getting_started/installation.md): Learn how to install Nightfall DLP for GitHub.\n- [Configure Alerts for GitHub](https://help.nightfall.ai/github/getting_started/integration_alerts.md): Understand the process of configuring integration alerts for Nightfall for GitHub.\n- [Configure Policies for GitHub](https://help.nightfall.ai/github/policies.md): Learn how to configure a detection policy for Nightfall DLP for GitHub\n- [GitHub App Selection](https://help.nightfall.ai/github/policies/integration.md): Learn how you can select the GitHub integration in a Nightfall policy.\n- [Configure Scope for GitHub](https://help.nightfall.ai/github/policies/scope.md): Learn the process of configuring the Scope section while creating a Nightfall policy in Nightfall or GitHub.\n- [Use Regular Expressions to Exclude GitHub Directories](https://help.nightfall.ai/github/policies/scope/github_regexp.md): Learn how to use regular expressions to exclude specific GitHub repositories, while configuring the scope section in Nightfall for GitHub.\n- [Configure Detection Rules for GitHub](https://help.nightfall.ai/github/policies/detection_rules.md): Learn the process of selecting detection rules while creating a Nightfall policy in Nightfall for GitHub.\n- [Configure Advanced Settings for GitHub](https://help.nightfall.ai/github/policies/advanced_settings.md): Learn the process of configuring advanced settings while creating a Nightfall policy in Nightfall for GitHub.\n- [Configure Risk Score for GitHub](https://help.nightfall.ai/github/policies/risk_score.md): Learn the process of configuring the Risk Score and naming the policy while creating a Nightfall policy in Nightfall for GitHub.\n- [Manage GitHub Events](https://help.nightfall.ai/github/events.md): Learn how to handle Nightfall Events that were created as a result of sensitive data leak in GitHub.\n- [Remediation on Nightfall for Github](https://help.nightfall.ai/github/remediation.md): Sensitive data like credentials pose a large risk when found in code repos. Read our guide to remediating these DLP risks in GitHub.\n- [Getting Started](https://help.nightfall.ai/google-drive/getting_started.md): Learn how to get started with Nightfall DLP for Google Drive.\n- [Requirements](https://help.nightfall.ai/google-drive/getting_started/requirements.md): Learn what requirements must be fulfilled to install Nightfall for Google Drive.\n- [Install Nightfall for Google Drive](https://help.nightfall.ai/google-drive/getting_started/installation.md): Learn how to install Nightfall for Google Drive.\n- [Enable Google Drive Labels](https://help.nightfall.ai/google-drive/getting_started/labels.md): Learn how you can enable Google Drive Labels in Nightfall for Google Drive.\n- [Configure Alerts for Google Drive](https://help.nightfall.ai/google-drive/getting_started/integration_alerts.md): Learn the process of configuring integration level alerts in Nightfall for Google Drive.\n- [Configure Policies for Google Drive](https://help.nightfall.ai/google-drive/policies.md): Learn to configure Nightfall policies to monitor sensitive data from your Google Drive instances.\n- [Google Drive App Selection](https://help.nightfall.ai/google-drive/policies/integration.md): Learn how you can select the Google Drive integration in a Nightfall policy.\n- [Configure Scope for Google Drive](https://help.nightfall.ai/google-drive/policies/scope.md): Learn how you can configure the Scope section in a policy, created in Nightfall for Google Drive.\n- [Configure Detection Rules for Google Drive](https://help.nightfall.ai/google-drive/policies/detection_rules.md): Learn how to select the required detection rules while creating a Nightfall policy for Google Drive.\n- [Configure Advanced Settings for Google Drive](https://help.nightfall.ai/google-drive/policies/advanced_settings.md): Learn how to configure the advanced settings section in a Nightfall policy for the Google Drive.\n- [Risk Score for Google Drive](https://help.nightfall.ai/google-drive/policies/configure_risk.md): Learn how to configure risk score and name a Nightfall policy created for the Google Drive.\n- [Manage Google Drive Events](https://help.nightfall.ai/google-drive/policies/events.md): Learn how to handle Nightfall Events that were created as a result of sensitive data leak in the Google Drive.\n- [Getting Started](https://help.nightfall.ai/confluence/getting_started.md): Learn how to get started with Confluence.\n- [Install Nightfall for Confluence](https://help.nightfall.ai/confluence/installation.md): Learn how to install Nightfall DLP for Confluence.\n- [Configure Alerts for Confluence](https://help.nightfall.ai/confluence/installation/integration_alerts.md): Learn how you can configure the integration level alerts in Confluence\n- [Configuring Policies for Confluence](https://help.nightfall.ai/confluence/policies.md): Learn how to configure policies in Nightfall DLP for Confluence.\n- [Confluence App Selection](https://help.nightfall.ai/confluence/policies/integration.md): Learn how to select the Confluence integration while creating a policy in Nightfall.\n- [Configure Scope for Confluence](https://help.nightfall.ai/confluence/policies/scope.md): Learn how you can configure the Scope section in a Nightfall for Confluence policy.\n- [Configure Detection Rules for Confluence](https://help.nightfall.ai/confluence/policies/detection_rules.md): Learn how you can select the required detection rules while creating a policy in Nightfall for Confluence.\n- [Configure Advanced Settings for Confluence](https://help.nightfall.ai/confluence/policies/advanced_settings.md): Learn how to configure advanced settings in Nightfall for Confluence.\n- [Configure Risk Score for Confluence](https://help.nightfall.ai/confluence/policies/risk_score.md): Learn how you can configure risk score and name a policy in Nightfall for Confluence.\n- [Manage Confluence Events](https://help.nightfall.ai/confluence/policies/events.md): Learn how to handle Nightfall Events that were created as a result of sensitive data leak in Confluence.\n- [FAQs](https://help.nightfall.ai/confluence/faqs.md): FAQs on Nightfall for Confluence\n- [Page Restrictions](https://help.nightfall.ai/confluence/faqs/page-restrictions.md): Note the current issue that we have with scanning for Confluence pages with Page Restrictions set\n- [Getting Started](https://help.nightfall.ai/jira/getting_started.md): Learn how to get started with Nightfall DLP for Jira.\n- [Install Nightfall for Jira](https://help.nightfall.ai/jira/installation.md): Step by step instructions on installing the Nightfall for JIRA integration\n- [Configuring Alerts for Jira](https://help.nightfall.ai/jira/installation/integration_alerts.md): Learn how you can configure integration level alerts in Nightfall for Jira.\n- [Configure Policies in Nightfall for Jira](https://help.nightfall.ai/jira/policies.md): Learn how to configure policies in Nightfall for Jira.\n- [Jira App Selection](https://help.nightfall.ai/jira/policies/integration.md): Learn how you can select the Jira integration while creating a policy in Nightfall.\n- [Configure Scope in Nightfall for JIRA](https://help.nightfall.ai/jira/policies/scope.md): Learn how you can configure the Scope section while creating a policy in Nightfall for JIRA.\n- [Select Detection Rules in Nightfall for JIRA](https://help.nightfall.ai/jira/policies/detection_rules.md): Learn how you can select the required detection rules while creating a policy in Nightfall for JIRA.\n- [Configuring Advanced Settings in Nightfall for JIRA](https://help.nightfall.ai/jira/policies/advanced_settings.md): Learn how you can configure the advanced settings section in a Nightfall policy created for the Nightfall for JIRA integration.\n- [Configure Risk Score for Jira](https://help.nightfall.ai/jira/policies/risk_score.md): Learn how you can configure risk score and name a policy in Nightfall for Jira.\n- [Manage Jira Events](https://help.nightfall.ai/jira/policies/events.md): Learn how to handle Nightfall Events that were created as a result of sensitive data leak in the JIRA DLP.\n- [Getting Started](https://help.nightfall.ai/microsoft-365/getting_started.md): Learn the basics of Nightfall DLP for Microsoft 365\n- [Microsoft 365 Requirements](https://help.nightfall.ai/microsoft-365/getting_started/requirements.md): Make sure the following requirements are fulfilled before you get started with Microsoft 365.\n- [Setting up Directory Sync](https://help.nightfall.ai/microsoft-365/getting_started/directory_sync.md): Learn how you can setup directory sync for Microsoft 365.\n- [Setting up Microsoft Tenant](https://help.nightfall.ai/microsoft-365/getting_started/microsoft_tenant_setup.md): Learn how to setup Microsoft Tenant for Nightfall\n- [Update App Selection for a Registered Tenant](https://help.nightfall.ai/microsoft-365/getting_started/microsoft_tenant_setup/update_app_selections.md): Learn how you can update the app selection in Microsoft 365.\n- [Nightfall for OneDrive](https://help.nightfall.ai/microsoft-365/onedrive.md)\n- [Configure Alerts for OneDrive](https://help.nightfall.ai/microsoft-365/onedrive/integration_alerts.md): Learn how to configure integration level alerts in Nightfall for OneDrive.\n- [Nightfall Policies for OneDrive](https://help.nightfall.ai/microsoft-365/onedrive/policies.md): Learn how to configure OneDrive policies\n- [OneDrive App Selection](https://help.nightfall.ai/microsoft-365/onedrive/policies/integration.md): Learn how you can select the OneDrive integration while creating a Nightfall policy.\n- [Configure Scope for OneDrive](https://help.nightfall.ai/microsoft-365/onedrive/policies/scope.md): Learn how to configure the scope section in Nightfall policies created for Microsoft OneDrive.\n- [Configure Detection Rules for OneDrive](https://help.nightfall.ai/microsoft-365/onedrive/policies/detection_rules.md): Learn how to configure the detection rules section in Nightfall policies created for Microsoft OneDrive.\n- [Configure Advanced Settings for OneDrive](https://help.nightfall.ai/microsoft-365/onedrive/policies/advanced_settings.md): Learn how to configure the advanced setting section in Nightfall policies created for Microsoft OneDrive.\n- [Risk Score for OneDrive Policies](https://help.nightfall.ai/microsoft-365/onedrive/policies/risk_score.md): Learn how to configure risk score and name a Nightfall policy created for Microsoft OneDrive.\n- [Manage OneDrive Events](https://help.nightfall.ai/microsoft-365/onedrive/policies/events.md): Learn how to handle Nightfall Events that were created as a result of sensitive data leak in the Microsoft OneDrive.\n- [Nightfall for Microsoft Teams](https://help.nightfall.ai/microsoft-365/microsoft_teams.md): Learn how to get started with Nightfall for Microsoft Teams\n- [Configure Alerts for Microsoft Teams](https://help.nightfall.ai/microsoft-365/microsoft_teams/integration_alerts.md): Learn how you can configure integration level alerts in Microsoft Teams.\n- [Configure Policies for Microsoft Teams](https://help.nightfall.ai/microsoft-365/microsoft_teams/policies.md): Learn how to configure a detection policy for Nightfall for Microsoft Teams.\n- [Select Integration in Microsoft Teams](https://help.nightfall.ai/microsoft-365/microsoft_teams/policies/integration.md): Learn how you can select the MS Teams integration in a Nightfall policy.\n- [Configure Scope for Microsoft teams](https://help.nightfall.ai/microsoft-365/microsoft_teams/policies/scope.md): Learn how to configure the Scope section for Microsoft Teams.\n- [Scope for Personal Chats](https://help.nightfall.ai/microsoft-365/microsoft_teams/policies/scope/personal_chats.md): Learn how to configure the Scope section for personal chats in Microsoft Teams policy.\n- [Scope for MS Teams Channels](https://help.nightfall.ai/microsoft-365/microsoft_teams/policies/scope/channels.md): Learn how to configure the Scope section for personal chats in Microsoft Teams policy.\n- [Configure Detection Rules in Microsoft Teams DLP](https://help.nightfall.ai/microsoft-365/microsoft_teams/policies/detection_rules.md): Learn how to configure the detection rules section in Nightfall policies created for Microsoft Teams DLP.\n- [Configure Advanced Settings in Microsoft Teams](https://help.nightfall.ai/microsoft-365/microsoft_teams/policies/advanced_settings.md): Learn how to configure the advanced setting section in Nightfall policies created for Microsoft Teams.\n- [Risk Score in Microsoft Teams Policies](https://help.nightfall.ai/microsoft-365/microsoft_teams/policies/risk_score.md): Learn how to configure risk score and name a Nightfall policy created for Microsoft Teams DLP.\n- [Manage Microsoft Teams Events](https://help.nightfall.ai/microsoft-365/microsoft_teams/policies/events.md): Learn how to handle Nightfall Events that were created as a result of sensitive data leak in the Microsoft Teams.\n- [Getting Started](https://help.nightfall.ai/microsoft-exchange/getting_started.md): Learn the basics of Nightfall DLP for Microsoft Exchange\n- [Microsoft Exchange Requirements](https://help.nightfall.ai/microsoft-exchange/getting_started/requirements.md): Make sure the following requirements are fulfilled before you get started with Microsoft Exchange.\n- [Setting up Directory Sync](https://help.nightfall.ai/microsoft-exchange/getting_started/directory_sync.md): Learn how you can setup directory sync for Microsoft Exchange.\n- [Installing Microsoft Exchange](https://help.nightfall.ai/microsoft-exchange/getting_started/installing-microsoft-exchange.md)\n- [Create Connectors](https://help.nightfall.ai/microsoft-exchange/getting_started/installing-microsoft-exchange/create-connectors.md)\n- [Create Rules](https://help.nightfall.ai/microsoft-exchange/getting_started/installing-microsoft-exchange/create-rules.md)\n- [Create MX Record](https://help.nightfall.ai/microsoft-exchange/getting_started/installing-microsoft-exchange/create-mx-record.md)\n- [Nightfall for Microsoft Exchange](https://help.nightfall.ai/microsoft-exchange/exchange_online.md): Learn how to get started with Nightfall for Exchange\n- [Configure Alerts for Exchange](https://help.nightfall.ai/microsoft-exchange/exchange_online/integration_alerts.md): Learn how you can configure integration level alerts in Exchange.\n- [Configure Policies for Exchange](https://help.nightfall.ai/microsoft-exchange/exchange_online/policies.md): Learn how to configure a detection policy for Nightfall for Exchange.\n- [Select Integration in Exchange](https://help.nightfall.ai/microsoft-exchange/exchange_online/policies/integration.md): Learn how you can select the Exchange integration in a Nightfall policy.\n- [Configure Scope for Exchange](https://help.nightfall.ai/microsoft-exchange/exchange_online/policies/scope.md): Learn how to configure the Scope section for Exchange.\n- [Configure Detection Rules in Exchange](https://help.nightfall.ai/microsoft-exchange/exchange_online/policies/detection_rules.md): Learn how to configure the detection rules section in Nightfall policies created for Exchange\n- [Configure Advanced Settings in Exchange](https://help.nightfall.ai/microsoft-exchange/exchange_online/policies/advanced_settings.md): Learn how to configure the advanced settings section in Nightfall policies created for MS Exchange.\n- [Risk Score in Exchange](https://help.nightfall.ai/microsoft-exchange/exchange_online/policies/risk_score.md): Learn how to configure risk score and name a Nightfall policy created for Exchange\n- [Manage Exchange Events](https://help.nightfall.ai/microsoft-exchange/exchange_online/policies/events.md): Learn how to handle Nightfall Events that were created as a result of sensitive data leak in Microsoft Exchange.\n- [Getting Started](https://help.nightfall.ai/microsoft-exchange-1/getting_started.md): Learn the basics of Nightfall DLP for Microsoft SharePoint\n- [Microsoft SharePoint Requirements](https://help.nightfall.ai/microsoft-exchange-1/getting_started/requirements.md): Make sure the following requirements are fulfilled before you get started with Microsoft SharePoint.\n- [Setting up Directory Sync](https://help.nightfall.ai/microsoft-exchange-1/getting_started/directory_sync.md): Learn how you can setup directory sync for Microsoft SharePoint.\n- [Installing Microsoft SharePoint](https://help.nightfall.ai/microsoft-exchange-1/getting_started/installing-microsoft-sharepoint.md): Learn how to install Nightfall for Microsoft SharePoint\n- [Nightfall for Microsoft SharePoint](https://help.nightfall.ai/microsoft-exchange-1/exchange_online.md): Learn how to get started with Nightfall for SharePoint\n- [Configure Alerts for SharePoint](https://help.nightfall.ai/microsoft-exchange-1/exchange_online/integration_alerts.md): Learn how you can configure integration level alerts in SharePoint.\n- [Configure Policies for SharePoint](https://help.nightfall.ai/microsoft-exchange-1/exchange_online/policies.md): Learn how to configure a detection policy for Nightfall for SharePoint.\n- [Select Integration in SharePoint](https://help.nightfall.ai/microsoft-exchange-1/exchange_online/policies/integration.md): Learn how you can select the SharePoint integration in a Nightfall policy.\n- [Configure Scope for SharePoint](https://help.nightfall.ai/microsoft-exchange-1/exchange_online/policies/scope.md): Learn how to configure the Scope section for SharePoint.\n- [Configure Detection Rules in SharePoint](https://help.nightfall.ai/microsoft-exchange-1/exchange_online/policies/detection_rules.md): Learn how to configure the detection rules section in Nightfall policies created for SharePoint\n- [Configure Advanced Settings in SharePoint](https://help.nightfall.ai/microsoft-exchange-1/exchange_online/policies/advanced_settings.md): Learn how to configure the advanced settings section in Nightfall policies created for MS SharePoint.\n- [Risk Score in SharePoint](https://help.nightfall.ai/microsoft-exchange-1/exchange_online/policies/risk_score.md): Learn how to configure risk score and name a Nightfall policy created for SharePoint\n- [Manage SharePoint Events](https://help.nightfall.ai/microsoft-exchange-1/exchange_online/policies/events.md): Learn how to handle Nightfall Events that were created as a result of sensitive data leak in Microsoft SharePoint.\n- [Overview](https://help.nightfall.ai/gmail/overview.md): An introduction to Nightfall DLP for Gmail\n- [Install Nightfall DLP for Gmail](https://help.nightfall.ai/gmail/installation.md): Learn how to install the Nightfall DLP for Gmail.\n- [Configure Content Compliance Rules](https://help.nightfall.ai/gmail/installation/content_compliance_rules.md): Learn how to configure Content Compliance rules in the Google Workspace.\n- [Create Content Compliance Rule - Monitoring](https://help.nightfall.ai/gmail/installation/content_compliance_rules/monitroring.md): Learn how to create a monitoring content compliance rule in the Google Workspace.\n- [Create Content Compliance Rule - Monitoring](https://help.nightfall.ai/gmail/installation/content_compliance_rules/monitroring-1.md): Learn how to create a monitoring content compliance rule in the Google Workspace.\n- [Configure Content Compliance Rule - Quarantine](https://help.nightfall.ai/gmail/installation/content_compliance_rules/quarantine.md): Learn how to create a quarantime content compliance rule in the Google Workspace.\n- [Configure Routing Rules - SMTP Relay Settings](https://help.nightfall.ai/gmail/installation/content_compliance_rules/smtp_relay_settings.md): Learn how to configure the routing rules for SMTP relay settings in the Google Workspace.\n- [Configure Alerts for Gmail](https://help.nightfall.ai/gmail/integration_alerts.md): Learn how to configure integration level alerts in Nightfall DLP for Gmail.\n- [Nightfall Policies for Gmail](https://help.nightfall.ai/gmail/policies.md): Learn about the Gmail policies in Nightfall DLP for Gmail.\n- [Gmail App Selection](https://help.nightfall.ai/gmail/policies/integration.md): Learn how you can select the Gmail integration in a Nightfall policy.\n- [Configure Scope for Gmail](https://help.nightfall.ai/gmail/policies/scope.md): Learn how to configure the Scope section for Gmail.\n- [Configure Detection Rules for Gmail](https://help.nightfall.ai/gmail/policies/detection_rules.md): Learn how to configure the detection rules section in Nightfall policies created for Gmail.\n- [Configure Advanced Settings for Gmail](https://help.nightfall.ai/gmail/policies/advanced_settings.md): Learn how to configure the advanced settings section in Nightfall policies created for the Gmail DLP.\n- [Configure Risk Score for Gmail](https://help.nightfall.ai/gmail/policies/risk_score.md): Learn how to configure risk score and name a Nightfall policy created for Gmail.\n- [Manage Gmail Events](https://help.nightfall.ai/gmail/policies/events.md): Learn how to handle Nightfall Events that were created as a result of sensitive data leak in the Gmail DLP.\n- [Remediation on Nightfall for Gmail](https://help.nightfall.ai/gmail/remediation.md): Learn how to remediate events in Nightfall for Gmail.\n- [Overview](https://help.nightfall.ai/salesforce/overview.md): Learn how to get started with Nightfall DLP for Salesforce.\n- [Getting Started](https://help.nightfall.ai/salesforce/getting-started.md): A walk through of how to install Nightfall's DLP solution for Salesforce.\n- [Install Nightfall DLP for Salesforce](https://help.nightfall.ai/salesforce/getting-started/installation.md): Learn how to install Nightfall DLP for Salesforce.\n- [Upgrade Nightfall DLP for Salesforce](https://help.nightfall.ai/salesforce/getting-started/upgrade.md): Learn how you can upgrade the Nightfall DLP package, installed in a Salesforce org.\n- [Configure Alerts for Salesforce](https://help.nightfall.ai/salesforce/getting-started/integration_alerts.md): Learn how you can configure integration level alerts in Salesforce.\n- [Nightfall Policies for Salesforce](https://help.nightfall.ai/salesforce/policies.md): Learn how you can create policies for the Nightfall DLP for Salesforce.\n- [Salesforce App Selection](https://help.nightfall.ai/salesforce/policies/integration.md): Learn how you can select the Salesforce integration in a Nightfall policy.\n- [Configure Scope for Salesforce](https://help.nightfall.ai/salesforce/policies/scope.md): Learn how to configure the Scope section in the Nightfall DLP for Salesforce.\n- [Configure Detection Rules for Salesforce](https://help.nightfall.ai/salesforce/policies/detection_rules.md): Learn how to configure the detection rules section in Nightfall policies created for Salesforce.\n- [Configure Advanced Settings for Salesforce](https://help.nightfall.ai/salesforce/policies/advanced_settings.md): Learn how to configure the advanced settings section in Nightfall policies created for the Salesforce DLP.\n- [Risk Score for Salesforce](https://help.nightfall.ai/salesforce/policies/risk_score.md): Learn how to configure risk score and name a Nightfall policy created for Salesforce.\n- [Manage Salesforce Events](https://help.nightfall.ai/salesforce/policies/events.md): Learn how to handle Nightfall Events that were created as a result of sensitive data leak in the Salesforce.\n- [High-Risk Salesforce Objects and Fields for Data Loss Prevention (DLP)](https://help.nightfall.ai/salesforce/policies/high-risk-salesforce-objects-and-fields-for-data-loss-prevention-dlp.md): Prioritize unstructured and custom Salesforce fields to detect PII, PCI, PHI, Financial Data, IP/Confidential Data, and Secrets.\n- [FAQs](https://help.nightfall.ai/salesforce/faqs.md): Frequently Asked Questions for Nightfall DLP for Salesforce\n- [Getting Started](https://help.nightfall.ai/zendesk/getting_started.md): This guide will help you to get started with installing and integrating Nightfall DLP for Zendesk.\n- [Requirements](https://help.nightfall.ai/zendesk/getting_started/requirements.md): Make sure the following requirements are fulfilled before you get started.\n- [Install Nightfall DLP for Zendesk](https://help.nightfall.ai/zendesk/getting_started/installation.md): Learn how you can install the Nightfall DLP for Zendesk.\n- [Configure Alerts for Zendesk](https://help.nightfall.ai/zendesk/getting_started/integration_alerts.md): Learn how you can configure the integration level alerts in Nightfall DLP for Zendesk.\n- [Configure Policies for Zendesk](https://help.nightfall.ai/zendesk/policies.md): Learn how to set up Nightfall policies for Zendesk\n- [Zendesk App Selection](https://help.nightfall.ai/zendesk/policies/integration.md): Learn how you can select the Zendesk integration in a Nightfall policy.\n- [Configure Scope for Zendesk](https://help.nightfall.ai/zendesk/policies/scope.md): Learn how to configure the Scope section for Zendesk.\n- [Configure Detection Rules for Zendesk DLP](https://help.nightfall.ai/zendesk/policies/detection_rules.md): Learn how to configure the detection rules section in Nightfall policies created for Zendesk.\n- [Configure Advanced Settings in Zendesk](https://help.nightfall.ai/zendesk/policies/advanced_settings.md): Learn how to configure the advanced settings section in Nightfall policies created for the Zendesk.\n- [Risk Score for Zendesk](https://help.nightfall.ai/zendesk/policies/risk_score.md): Learn how to configure risk score and name a Nightfall policy created for Zendesk\n- [Manage Zendesk Events](https://help.nightfall.ai/zendesk/policies/events.md): Learn how to handle Nightfall Events that were created as a result of sensitive data leak in the Zendesk.\n- [Nightfall for Claude Enterprise (Compliance API)](https://help.nightfall.ai/nightfall-for-anthropic-claude/nightfall-for-claude-enterprise-compliance-api.md)\n- [Install Nightfall for Claude Enterprise](https://help.nightfall.ai/nightfall-for-anthropic-claude/install-nightfall-for-claude-enterprise.md)\n- [Configure Policies for Claude Enterprise](https://help.nightfall.ai/nightfall-for-anthropic-claude/configure-policies-for-claude-enterprise.md)\n- [Policy Incidents](https://help.nightfall.ai/nightfall-for-anthropic-claude/policy-incidents.md)\n- [Comprehensive Claude Coverage](https://help.nightfall.ai/nightfall-for-anthropic-claude/comprehensive-claude-coverage.md)\n- [Frequently Asked Questions (FAQs)](https://help.nightfall.ai/nightfall-for-anthropic-claude/frequently-asked-questions-faqs.md)\n- [Getting Started](https://help.nightfall.ai/notion/getting_started.md): Learn the basics of Nightfall DLP for Notion.\n- [Requirements](https://help.nightfall.ai/notion/getting_started/requirements.md): Understand the Prerequisites to install the Nightfall DLP for Notion.\n- [Steps](https://help.nightfall.ai/notion/getting_started/steps.md): Learn the steps to get the Notion up and running.\n- [Install Nightfall for Notion](https://help.nightfall.ai/notion/installation.md): Learn how you can install the Nightfall DLP for Notion.\n- [Verification of Notion Installation](https://help.nightfall.ai/notion/installation/verification.md): Learn how you can verify the connection to the installed Notion instance.\n- [Configure Alerts for Notion](https://help.nightfall.ai/notion/integration_alerts.md): Learn how you can configure the integration level alerts for Notion.\n- [Configure Policies for Notion](https://help.nightfall.ai/notion/policies.md): Learn how you can create policies for the Nightfall DLP for Notion.\n- [Notion App Selection](https://help.nightfall.ai/notion/policies/integration.md): Learn how you can select the Notion integration in a Nightfall policy.\n- [Configure Detection Rules for Notion](https://help.nightfall.ai/notion/policies/detection_rules.md): Learn how to configure the detection rules section in Nightfall policies created for Notion.\n- [Configure Advanced Settings for Notion](https://help.nightfall.ai/notion/policies/advanced_settings.md): Learn how to configure the advanced settings section in Nightfall policies created for Notion.\n- [Risk Score for Notion](https://help.nightfall.ai/notion/policies/risk_score.md): Learn how to configure risk score and name a Nightfall policy created for the Notion DLP.\n- [Manage Notion Events](https://help.nightfall.ai/notion/policies/events.md): Learn how to handle Nightfall Events that were created as a result of sensitive data leak in the Notion.\n- [Users and Roles](https://help.nightfall.ai/nightfall_settings/users_roles.md): Learn more about users and roles in Nightfall settings.\n- [Authentication Options](https://help.nightfall.ai/nightfall_settings/users_roles/authentication_options.md): Learn the available authentication options.\n- [Role Based Access Control (RBAC)](https://help.nightfall.ai/nightfall_settings/role_based_access_control.md): Learn how the role based access control(RBAC) works in Nightfall.\n- [Security Analyst Role](https://help.nightfall.ai/nightfall_settings/role_based_access_control/security_analyst.md): Learn the various permissions available to the security analyst role in Nightfall.\n- [Policy Manager Role](https://help.nightfall.ai/nightfall_settings/role_based_access_control/policy_manager.md): Learn the various permissions available to the policy manager role in Nightfall.\n- [Security Events Manager Role](https://help.nightfall.ai/nightfall_settings/role_based_access_control/security_events_manager.md): Learn the various permissions available to the security events manager role in Nightfall.\n- [Security Operations Manager Role](https://help.nightfall.ai/nightfall_settings/role_based_access_control/security_operations_manager.md): Learn the various permissions available to the security operations manager role in Nightfall.\n- [System Administrator Role](https://help.nightfall.ai/nightfall_settings/role_based_access_control/system_administrator.md): Learn the various permissions available to the system administrator role in Nightfall.\n- [Directory Sync](https://help.nightfall.ai/nightfall_settings/directory_sync.md): Learn how you can leverage the directory sync feature in Nightfall.\n- [Add Microsoft Entra ID to Nightfall](https://help.nightfall.ai/nightfall_settings/directory_sync/microsoft_entra_id.md): Learn how to sync your Microsoft Entra ID's data to Nightfall.\n- [Google Workspace Directory Service](https://help.nightfall.ai/nightfall_settings/directory_sync/google_workspace.md): Learn how to sync your Google Workspace data to Nightfall.\n- [Add Okta to Nightfall](https://help.nightfall.ai/nightfall_settings/directory_sync/okta.md): Learn how to sync your Okta data to Nightfall.\n- [Custom Branding](https://help.nightfall.ai/nightfall_settings/custom-branding.md)\n- [Customer Referral Program](https://help.nightfall.ai/nightfall_settings/customer-referral-program.md)\n- [Frequently Asked Questions (FAQs)](https://help.nightfall.ai/faqs.md): A list of common queries which users get while using Nightfall and their responses.\n- [How long does it take to deploy Nightfall?](https://help.nightfall.ai/faqs/nightfall_deployment_time.md): Learn about the time taken to deploy Nightfall.\n- [How do I deploy Nightfall?](https://help.nightfall.ai/faqs/deploy_nightfall.md): Learn the process of Nightfall deployment.\n- [What are some unique points about Nightfall that I should know?](https://help.nightfall.ai/faqs/differentiators.md): Learn some unique points about Nightfall which differentiate it from the competitors.\n- [Which languages does Nightfall support?](https://help.nightfall.ai/faqs/supported_languages.md): Use this to understand the language nuances when using Nightfall for text recognition and classification.\n- [How does Nightfall yield time savings for my team?](https://help.nightfall.ai/faqs/reduced_tco.md): Learn how Nightfall can save your team's time in managing sensitive data.\n- [Nightfall vs Legacy DLP: What's the difference?](https://help.nightfall.ai/faqs/nightfall_vs_legacy_dlp.md): Learn the difference between Nightfall DLP and legacy DLP solutions.\n- [How does Nightfall make my organization more secure?](https://help.nightfall.ai/faqs/eliminate_data_exposure.md): Learn how Nightfall can secure your organization from sensitive data leaks.\n- [Nightfall vs CASB: What's the difference?](https://help.nightfall.ai/faqs/nightfall_vs_casb.md): Learn the differences between Nightfall DLP and cloud access security broker (CASB).\n- [Nightfall vs E-Discovery: What's the difference?](https://help.nightfall.ai/faqs/nightfall-vs-e-discovery.md): Learn the differences between Nightfall DLP and E-discovery\n- [How does Nightfall classify data?](https://help.nightfall.ai/faqs/data_classification.md): Learn how Nightfall classifies data.\n- [What types of data does Nightfall classify?](https://help.nightfall.ai/faqs/nightfall_data_types_classification.md): Learn the types of data that Nightfall can classify.\n- [Does Nightfall scan unstructured data?](https://help.nightfall.ai/faqs/unstructured_data_scan.md): Learn how Nightfall scans unstructured data.\n- [Does Nightfall require data to be already tagged?](https://help.nightfall.ai/faqs/data_tagging.md): Learn if Nightfall can handle data that is not tagged\n- [How do I learn more about and test out Nightfall?](https://help.nightfall.ai/faqs/contact_sales.md): Learn how you can contact Nightfall sales team.\n- [Using Service Accounts with Nightfall](https://help.nightfall.ai/faqs/service_accounts.md): Learn if you can use service accounts for authentication in the Nightfall integrations.\n- [Which permissions are required for each integration?](https://help.nightfall.ai/faqs/permissions.md): Learn the permissions required for each Nightfall integration.\n- [Where can I find active user counts for each SaaS application protected by Nightfall?](https://help.nightfall.ai/faqs/active_users.md): Learn how you search for active user count for each SaaS application protected by Nightfall.\n- [In the Atlassian Marketplace, why does it show that the Nightfall app is not approved in security?](https://help.nightfall.ai/faqs/atlassian_marketplace.md): Learn why the Atlassian Marketplace says that the Nightfall app is not approved.\n- [How can I estimate the data volume that Nightfall needs to scan?](https://help.nightfall.ai/faqs/estimate_data_to_be_scanned.md): Learn how you can estimate the amount of data that needs to be scanned by Nightfall.\n- [How can I check the Platform Status of Nightfall](https://help.nightfall.ai/faqs/platform_status.md): Learn how to view the current status of your Nightfall platform.\n- [Contact Nightfall](https://help.nightfall.ai/contact-us.md): Learn how you can contact Nightfall.\n- [Nightfall Page Redirects](https://help.nightfall.ai/nightfall-page-redirects.md)\n\n## Posture Management\n\n- [Nightfall Posture Management](https://help.nightfall.ai/data-security-posture-management/nightfall-posture-management.md)\n- [Nightfall Security Posture Management](https://help.nightfall.ai/data-security-posture-management/nightfall-security-posture-management.md)\n- [Installing Nightfall for Google Drive](https://help.nightfall.ai/data-security-posture-management/nightfall-for-google-drive/installing-nightfall-for-google-drive.md)\n- [Configuring Integration Alerts](https://help.nightfall.ai/data-security-posture-management/nightfall-for-google-drive/configuring-integration-alerts.md)\n- [Configuring Google Drive Policies](https://help.nightfall.ai/data-security-posture-management/nightfall-for-google-drive/configuring-google-drive-policies.md)\n- [Integration](https://help.nightfall.ai/data-security-posture-management/nightfall-for-google-drive/configuring-google-drive-policies/integration.md)\n- [Scope](https://help.nightfall.ai/data-security-posture-management/nightfall-for-google-drive/configuring-google-drive-policies/scope.md)\n- [Trigger](https://help.nightfall.ai/data-security-posture-management/nightfall-for-google-drive/configuring-google-drive-policies/trigger.md)\n- [Automated Actions](https://help.nightfall.ai/data-security-posture-management/nightfall-for-google-drive/configuring-google-drive-policies/automated-actions.md)\n- [Creating Policy](https://help.nightfall.ai/data-security-posture-management/nightfall-for-google-drive/configuring-google-drive-policies/creating-policy.md)\n- [Remediation for Google Drive](https://help.nightfall.ai/data-security-posture-management/nightfall-for-google-drive/remediation-for-google-drive.md)\n- [Posture Management Events Page](https://help.nightfall.ai/data-security-posture-management/nightfall-for-google-drive/posture-management-events-page.md)\n\n## Data Exfiltration Prevention\n\n- [Nightfall Data Exfiltration Prevention](https://help.nightfall.ai/data-exfiltration-prevention/nightfall-data-exfiltration-prevention.md)\n- [What is Data Exfiltration](https://help.nightfall.ai/data-exfiltration-prevention/nightfall_exfiltration.md)\n- [Nyx – AI-powered DLP Copilot](https://help.nightfall.ai/data-exfiltration-prevention/nightfall_copilot_nyx/nyx-ai-powered-dlp-copilot.md): Learn about Nyx. Nightfall's AI-powered Copilot.\n- [Exfiltration Events](https://help.nightfall.ai/data-exfiltration-prevention/dashboard-and-events/exfiltration-events.md): Learn the details available on the Nightfall Exfiltration Events page\n- [Installing Nightfall for Google Drive](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_google_drive/installation.md)\n- [Configuring Integration Alerts](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_google_drive/integration_alerts.md)\n- [Configuring Google Drive Policies](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_google_drive/policies.md)\n- [Google Drive App Selection](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_google_drive/policies/integration.md)\n- [Scope](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_google_drive/policies/scope.md)\n- [Trigger](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_google_drive/policies/trigger.md)\n- [Automated Actions](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_google_drive/policies/automated_actions.md)\n- [Creating Policy](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_google_drive/policies/policy_creation.md)\n- [Remediation for Google Drive Exfiltration](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_google_drive/remediation.md)\n- [Endpoint Exfiltration Prevention](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/endpoint-exfiltration-prevention.md)\n- [Additional Methods to Install Nightfall AI Extension](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/additional-methods-to-install-nightfall-ai-extension.md): This explains the other methods of deployment available for the Nightfall AI extension, separate from the Nightfall AI Agent.\n- [Install Nightfall AI Extension via Google Workspace Admin](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/additional-methods-to-install-nightfall-ai-extension/install-nightfall-ai-extension-via-google-workspace-admin.md): If an organization is utilizing Google Workspace to deploy extensions to Chrome, two options are provided to deploy the Nightfall extension and avoid conflicts on the machine.\n- [Install Nightfall AI Extension via a Common MDM Profile](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/additional-methods-to-install-nightfall-ai-extension/install-nightfall-ai-extension-via-a-common-mdm-profile.md): This walkthrough adds the Nightfall Profile Chrome ExtensionSettings to an existing custom macOS profile.\n- [Manually Install the Nightfall Safari Extension](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/additional-methods-to-install-nightfall-ai-extension/manually-install-the-nightfall-safari-extension.md)\n- [Install Nightfall AI Agent for Mac](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/installation_mac.md)\n- [Manual Installation](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/installation_mac/manual_installation.md)\n- [Nightfall macOS Agent Deployment: JAMF MDM](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/installation_mac/jamf_installation.md)\n- [Nightfall macOS Agent Deployment: JumpCloud MDM](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/installation_mac/nightfall-macos-agent-deployment-jumpcloud-mdm.md)\n- [Nightfall macOS Agent Deployment: Iru (Kandji) MDM](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/installation_mac/kandji_installation.md): This document explains the process of installing Nightfall AI agent using the Kandji MDM.\n- [Nightfall macOS Agent Deployment: Mosyle MDM](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/installation_mac/nightfall-macos-agent-deployment-mosyle-mdm.md): Below is a step-by-step guide to deploy the Nightfall Endpoint DLP agent for macOS using Mosyle MDM.\n- [Nightfall macOS Agent Deployment: PDQ SimpleMDM](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/installation_mac/nightfall-macos-agent-deployment-pdq-simplemdm.md): Below is a step-by-step guide to deploy the Nightfall Endpoint DLP agent for macOS using PDQ's SimpleMDM.\n- [Nightfall macOS Agent Deployment: Rippling MDM](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/installation_mac/rippling_installation.md): This document explains the process of installing Nightfall AI agent using the Rippling MDM.\n- [Nightfall macOS Agent Deployment: Workspace ONE UEM](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/installation_mac/nightfall-macos-agent-deployment-workspace-one-uem.md): Below is a step-by-step guide to deploy the Nightfall Endpoint agent for macOS using Workspace ONE UEM.\n- [Install Nightfall AI Agent for Windows OS](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/install-nightfall-ai-agent-for-windows-os.md)\n- [Manual Installation](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/install-nightfall-ai-agent-for-windows-os/manual-installation.md): Learn how to install the Nightfall agent on Microsoft Windows OS manually.\n- [Nightfall Windows Agent Deployment: JumpCloud MDM](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/install-nightfall-ai-agent-for-windows-os/nightfall-windows-agent-deployment-jumpcloud-mdm.md): Instructions on how to install the Nightfall agent on Microsoft Windows using the JumpCloud MDM.\n- [Nightfall Windows Agent Deployment: Microsoft Intune](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/install-nightfall-ai-agent-for-windows-os/nightfall-windows-agent-deployment-microsoft-intune.md): Learn how to install the Nightfall Agent for Windows using Intune as a Line-of-Business (LOB) app.\n- [Nightfall Windows Agent Deployment: MSI](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/install-nightfall-ai-agent-for-windows-os/nightfall-windows-agent-deployment-msi.md): This guide explains multiple ways to deploy the Nightfall Agent (NightfallAgent.msi) with the required API\\_KEY and COMPANY\\_ID parameters.\n- [Nightfall Windows Agent Deployment: Rippling MDM](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/install-nightfall-ai-agent-for-windows-os/nightfall-windows-agent-deployment-rippling-mdm.md): Learn how to install the Nightfall agent on Microsoft Windows OS using the Rippling MDM.\n- [Nightfall Windows Agent Deployment: Workspace ONE UEM](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/install-nightfall-ai-agent-for-windows-os/nightfall-windows-agent-deployment-workspace-one-uem.md): Below is a step-by-step guide to deploy the Nightfall Endpoint DLP agent for Windows using Workspace ONE UEM.\n- [Nightfall Windows Agent Deployment: SCCM](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/install-nightfall-ai-agent-for-windows-os/nightfall-windows-agent-deployment-sccm.md): A step-by-step guide to deploy the Nightfall endpoint agent and the AI-coding-assistant hooks (Claude Code, Cursor, VS Code + GitHub Copilot) to Windows devices using SCCM/MECM.\n- [Configuring Integration Alerts](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/integration_alerts.md)\n- [Configuring Policies](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies.md)\n- [MAC/Windows App Selection](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/integration.md)\n- [Scope](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/scope.md)\n- [Trigger](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/trigger.md)\n- [Browser Uploads](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/trigger/browser-uploads.md)\n- [Clipboard Paste](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/trigger/clipboard-paste.md)\n- [Uploads, Paste to Desktop Apps](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/trigger/uploads-paste-to-desktop-apps.md)\n- [Session Detection: Corporate and Personal Account Filtering](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/trigger/session-detection-corporate-and-personal-account-filtering.md)\n- [Cloud Sync App Uploads](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/trigger/cloud-sync-app-uploads.md)\n- [Removable Media](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/trigger/removable-media.md)\n- [Git Push Monitoring](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/trigger/git-push-monitoring.md)\n- [Printer Support](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/trigger/printer-support.md)\n- [Advanced Settings](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/advanced_settings.md): Learn about the advanced setting options present in the Nightfall exfiltration policy for MAC devices.\n- [Admin Alerting](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/advanced_settings/alerting.md): Learn how to configure admin alerts in Nightfall exfiltration policies.\n- [Automated Actions](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/advanced_settings/automated_action.md): Learn more about how automated actions work in a Nightfall exfiltration policy.\n- [Temporary Exception Requests - User Justification and Override Workflow](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/advanced_settings/automated_action/temporary-exception-requests-user-justification-and-override-workflow.md)\n- [End-User Notifications](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/advanced_settings/enduser_notification.md): Learn how to configure end user notifications in Nightfall exfiltration policies.\n- [Creating Policy](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/create_policy.md)\n- [Remediation for MAC OS Policies](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/remediation.md)\n- [Frequently Asked Questions (FAQs)](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/frequently-asked-questions-faqs.md)\n- [Remediation for Windows OS Policies](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/remediation-for-windows-os-policies.md)\n- [Recommended Policy Configurations](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/policies/recommended-policy-configurations.md)\n- [Endpoints - Device List Page](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_endpoint/endpoints-device-list-page.md)\n- [Nightfall Exfiltration for Salesforce](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_salesforce/overview.md)\n- [Configuring Integration Alerts](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_salesforce/integration_alerts.md)\n- [Configuring Salesforce Exfiltration Policies](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_salesforce/policies.md)\n- [Salesforce App Selection](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_salesforce/policies/integration.md)\n- [Scope](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_salesforce/policies/scope.md)\n- [Trigger](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_salesforce/policies/trigger.md)\n- [Advanced Settings](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_salesforce/policies/advanced_settings.md)\n- [Creating Policy](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_salesforce/policies/create_policy.md)\n- [Remediation for Salesforce Exfiltration](https://help.nightfall.ai/data-exfiltration-prevention/exfiltration_salesforce/policies/remediation.md)\n- [AI Governance](https://help.nightfall.ai/data-exfiltration-prevention/ai-agent-security/ai-governance.md)\n- [MCP Server Visibility](https://help.nightfall.ai/data-exfiltration-prevention/ai-agent-security/ai-governance/mcp-server-visibility.md)\n- [Auditability and Control](https://help.nightfall.ai/data-exfiltration-prevention/ai-agent-security/ai-governance/auditability-and-control.md)\n- [Setup & Installation](https://help.nightfall.ai/data-exfiltration-prevention/ai-agent-security/ai-governance/auditability-and-control/setup-and-installation.md)\n- [Nightfall Hooks for Cursor](https://help.nightfall.ai/data-exfiltration-prevention/ai-agent-security/ai-governance/auditability-and-control/setup-and-installation/nightfall-hooks-for-cursor.md)\n- [Nightfall Hooks for Claude Code](https://help.nightfall.ai/data-exfiltration-prevention/ai-agent-security/ai-governance/auditability-and-control/setup-and-installation/nightfall-hooks-for-claude-code.md)\n- [Nightfall Hooks for VS Code Copilot](https://help.nightfall.ai/data-exfiltration-prevention/ai-agent-security/ai-governance/auditability-and-control/setup-and-installation/nightfall-hooks-for-vs-code-copilot.md)\n- [Claude Cowork (OpenTelemetry)](https://help.nightfall.ai/data-exfiltration-prevention/ai-agent-security/ai-governance/auditability-and-control/setup-and-installation/claude-cowork-opentelemetry.md)\n- [Hooks vs. Open Telemetry](https://help.nightfall.ai/data-exfiltration-prevention/ai-agent-security/ai-governance/auditability-and-control/hooks-vs.-open-telemetry.md)\n- [Creating an AI Agent Security Policy](https://help.nightfall.ai/data-exfiltration-prevention/ai-agent-security/ai-governance/auditability-and-control/creating-an-ai-agent-security-policy.md)\n- [Investigating AI Agent Security Incidents](https://help.nightfall.ai/data-exfiltration-prevention/ai-agent-security/ai-governance/auditability-and-control/investigating-ai-agent-security-incidents.md)\n- [Forensics Search](https://help.nightfall.ai/data-exfiltration-prevention/forensic-search/forensics-search.md): Perform insider risk investigations and threat hunting across all detected data exfiltration events — not only policy-triggered alerts.\n- [App Intelligence](https://help.nightfall.ai/data-exfiltration-prevention/app-intelligence/app-intelligence.md): Identify, classify, and assess risk for SaaS and AI applications used across your environment.\n\n## Data Encryption\n\n- [Nightfall Data Encryption](https://help.nightfall.ai/data-encryption/nightfall-data-encryption.md)\n- [Encryption FAQs](https://help.nightfall.ai/data-encryption/encryption-faqs.md)\n- [Data Encryption for Gmail - Overview](https://help.nightfall.ai/data-encryption/gmail/data-encryption-for-gmail-overview.md)\n- [Installing Nightfall DLP](https://help.nightfall.ai/data-encryption/gmail/installing-nightfall-dlp.md)\n- [Installing Nightfall DLP on Individual Devices](https://help.nightfall.ai/data-encryption/gmail/installing-nightfall-dlp/installing-nightfall-dlp-on-individual-devices.md)\n- [Installing Nightfall DLP Across Organization](https://help.nightfall.ai/data-encryption/gmail/installing-nightfall-dlp/installing-nightfall-dlp-across-organization.md)\n- [Creating Policies for Encryption](https://help.nightfall.ai/data-encryption/gmail/creating-policies-for-encryption.md)\n- [Integration](https://help.nightfall.ai/data-encryption/gmail/creating-policies-for-encryption/integration.md)\n- [Scope](https://help.nightfall.ai/data-encryption/gmail/creating-policies-for-encryption/scope.md)\n- [Advanced Settings](https://help.nightfall.ai/data-encryption/gmail/creating-policies-for-encryption/advanced-settings.md)\n- [Creating Policy](https://help.nightfall.ai/data-encryption/gmail/creating-policies-for-encryption/creating-policy.md)\n- [Remediation for Data Encryption](https://help.nightfall.ai/data-encryption/gmail/creating-policies-for-encryption/remediation-for-data-encryption.md)\n- [Encryption Policy FAQs](https://help.nightfall.ai/data-encryption/gmail/creating-policies-for-encryption/encryption-policy-faqs.md)\n- [Nightfall Encryption - Sender Experience](https://help.nightfall.ai/data-encryption/gmail/nightfall-encryption-sender-experience.md)\n- [Nightfall Encryption - Recipient Experience](https://help.nightfall.ai/data-encryption/gmail/nightfall-encryption-recipient-experience.md)\n- [Encryption Events Page](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page.md)\n\n## Developer APIs\n\n- [Welcome to Developer APIs Documentation](https://help.nightfall.ai/developer-api/welcome-to-developer-apis-documentation.md)\n- [Overview](https://help.nightfall.ai/developer-api/introduction/overview.md)\n- [Quickstart](https://help.nightfall.ai/developer-api/introduction/quickstart.md)\n- [Authentication and Security](https://help.nightfall.ai/developer-api/introduction/authentication_security.md)\n- [Pricing](https://help.nightfall.ai/developer-api/introduction/pricing.md)\n- [Entities and Terms to Know](https://help.nightfall.ai/developer-api/key-concepts/key_terms.md)\n- [Setting Up Nightfall](https://help.nightfall.ai/developer-api/key-concepts/setup.md)\n- [Creating API Key](https://help.nightfall.ai/developer-api/key-concepts/setup/api_key.md)\n- [Creating Policies](https://help.nightfall.ai/developer-api/key-concepts/setup/policies.md)\n- [Alerting](https://help.nightfall.ai/developer-api/key-concepts/alerting.md)\n- [Scanning Text](https://help.nightfall.ai/developer-api/key-concepts/text_scan.md)\n- [Scanning Files](https://help.nightfall.ai/developer-api/key-concepts/file_scan.md)\n- [Supported File Types](https://help.nightfall.ai/developer-api/key-concepts/file_scan/supported_file_types.md)\n- [File Scanning and Webhooks](https://help.nightfall.ai/developer-api/key-concepts/file_scan/webhooks.md)\n- [Uploading and Scanning API Calls](https://help.nightfall.ai/developer-api/key-concepts/file_scan/scan_api_calls.md)\n- [Special File Types](https://help.nightfall.ai/developer-api/key-concepts/file_scan/special_file_types.md)\n- [Specialized File Detectors](https://help.nightfall.ai/developer-api/key-concepts/file_scan/special_file_detectors.md)\n- [Webhooks and Asynchronous Notifications](https://help.nightfall.ai/developer-api/key-concepts/file_scan/webhooks_async_notifications.md)\n- [Accessing Your Webhook Signing Key](https://help.nightfall.ai/developer-api/key-concepts/file_scan/webhooks_async_notifications/webhook_signing_key.md)\n- [Creating a Webhook Server](https://help.nightfall.ai/developer-api/key-concepts/file_scan/webhooks_async_notifications/webhook_server.md)\n- [Scanning Features](https://help.nightfall.ai/developer-api/key-concepts/scanning_features.md)\n- [Using Pre-Configured Detection Rules](https://help.nightfall.ai/developer-api/key-concepts/scanning_features/pre_configured_detection_rules.md)\n- [Scanning Images for patterns using Custom Regex Detectors](https://help.nightfall.ai/developer-api/key-concepts/scanning_features/pre_configured_detection_rules/scanning-images-for-patterns-using-custom-regex-detectors.md)\n- [Creating an Inline Detection Rule](https://help.nightfall.ai/developer-api/key-concepts/scanning_features/inline_detection_rules.md)\n- [Using Exclusion Rules](https://help.nightfall.ai/developer-api/key-concepts/scanning_features/exclusion_rules.md)\n- [Using Context Rules](https://help.nightfall.ai/developer-api/key-concepts/scanning_features/context_rules.md)\n- [Using Redaction](https://help.nightfall.ai/developer-api/key-concepts/scanning_features/redaction.md)\n- [Using Policies to Send Alerts](https://help.nightfall.ai/developer-api/key-concepts/scanning_features/send_alerts_using_policies.md)\n- [Detecting Secrets](https://help.nightfall.ai/developer-api/key-concepts/scanning_features/secrets_detection.md)\n- [PHI Detection Rules](https://help.nightfall.ai/developer-api/key-concepts/scanning_features/phi_detection_rules.md)\n- [Test Datasets](https://help.nightfall.ai/developer-api/key-concepts/test_datasets.md)\n- [Errors](https://help.nightfall.ai/developer-api/key-concepts/errors.md)\n- [Nightfall Playground](https://help.nightfall.ai/developer-api/key-concepts/nightfall_playground.md)\n- [DLP APIs - Firewall for AI Platform](https://help.nightfall.ai/developer-api/nightfall_apis/dlp.md)\n- [Rate Limits for Firewall APIs](https://help.nightfall.ai/developer-api/nightfall_apis/dlp/rate_limits.md)\n- [DLP APIs - Native SaaS Apps](https://help.nightfall.ai/developer-api/nightfall_apis/saas.md)\n- [Rate Limits for Native SaaS app APIs](https://help.nightfall.ai/developer-api/nightfall_apis/saas/rate-limits-for-native-saas-app-apis.md)\n- [Policy Update APIs](https://help.nightfall.ai/developer-api/nightfall_apis/scope_update.md)\n- [Exfiltration Prevention APIs](https://help.nightfall.ai/developer-api/nightfall_apis/exfiltration-prevention-apis.md)\n- [Posture Management APIs](https://help.nightfall.ai/developer-api/nightfall_apis/posture-management-apis.md)\n- [SaaS App and Device Management APIs](https://help.nightfall.ai/developer-api/nightfall_apis/saas-app-and-device-management-apis.md)\n- [AI Governance API's](https://help.nightfall.ai/developer-api/nightfall_apis/ai-governance-apis.md)\n- [Nightfall Model Context Protocol (MCP) Server](https://help.nightfall.ai/developer-api/nightfall_apis/nightfall-model-context-protocol-mcp-server.md)\n- [Getting Started](https://help.nightfall.ai/developer-api/nightfall_apis/nightfall-model-context-protocol-mcp-server/getting-started.md)\n- [Available Tools](https://help.nightfall.ai/developer-api/nightfall_apis/nightfall-model-context-protocol-mcp-server/available-tools.md)\n- [Common Use Cases](https://help.nightfall.ai/developer-api/nightfall_apis/nightfall-model-context-protocol-mcp-server/common-use-cases.md)\n- [Query Examples](https://help.nightfall.ai/developer-api/nightfall_apis/nightfall-model-context-protocol-mcp-server/query-examples.md)\n- [Best Practices - Security Investigation Workflows](https://help.nightfall.ai/developer-api/nightfall_apis/nightfall-model-context-protocol-mcp-server/best-practices-security-investigation-workflows.md)\n- [Troubleshooting](https://help.nightfall.ai/developer-api/nightfall_apis/nightfall-model-context-protocol-mcp-server/troubleshooting.md)\n- [Support & Resources](https://help.nightfall.ai/developer-api/nightfall_apis/nightfall-model-context-protocol-mcp-server/support-and-resources.md)\n- [Overview](https://help.nightfall.ai/developer-api/nightfall_sdk/overview.md)\n- [Overview](https://help.nightfall.ai/developer-api/language_specific_guides/overview.md)\n- [Python](https://help.nightfall.ai/developer-api/language_specific_guides/python.md)\n- [Ruby](https://help.nightfall.ai/developer-api/language_specific_guides/ruby.md)\n- [Java](https://help.nightfall.ai/developer-api/language_specific_guides/java.md)\n- [Overview](https://help.nightfall.ai/developer-api/nightfall-use-cases/overview.md)\n- [Building Endpoint DLP to Detect PII on Your Machine in Real-Time](https://help.nightfall.ai/developer-api/nightfall-use-cases/endpoint_dlp.md)\n- [Deploy a File Scanner for Sensitive Data in 40 Lines of Code](https://help.nightfall.ai/developer-api/nightfall-use-cases/file_scanner.md)\n- [Using Scan API (with Python)](https://help.nightfall.ai/developer-api/nightfall-use-cases/scan_api.md)\n- [FAQs](https://help.nightfall.ai/developer-api/faqs.md)\n- [What Can I do with the Firewall for AI](https://help.nightfall.ai/developer-api/faqs/uses.md)\n- [How quickly can I get started with Firewall for AI?](https://help.nightfall.ai/developer-api/faqs/get_started.md)\n- [What types of data can I scan with API?](https://help.nightfall.ai/developer-api/faqs/data_scan.md)\n- [What types of detectors are supported out of the box?](https://help.nightfall.ai/developer-api/faqs/detector_types.md)\n- [Can I customize or bring my own detectors?](https://help.nightfall.ai/developer-api/faqs/customize_detectors.md)\n- [What is the pricing model?](https://help.nightfall.ai/developer-api/faqs/pricing_model.md)\n- [How do I know my data is secure?](https://help.nightfall.ai/developer-api/faqs/secure_data_confirmation.md)\n- [How do I get in touch with you?](https://help.nightfall.ai/developer-api/faqs/contact_nightfall.md)\n- [Can I test out the detection and my own detection rules before writing any code?](https://help.nightfall.ai/developer-api/faqs/playground.md)\n- [How does Nightfall support custom data types?](https://help.nightfall.ai/developer-api/faqs/custom_data_types.md)\n- [How does Nightfall's Firewall for AI differs from other solutions?](https://help.nightfall.ai/developer-api/faqs/unique_features.md)\n- [Contact Us](https://help.nightfall.ai/developer-api/contact_nightfall_team.md)\n- [Nightfall MCP Documentation](https://help.nightfall.ai/developer-api/nightfall-mcp-documentation.md)\n\n## Data Classification and Discovery\n\n- [Data Discovery and Classification](https://help.nightfall.ai/audit/data-discovery-and-classification.md)\n- [Introduction to Nightfall Audit](https://help.nightfall.ai/audit/nightfall-audits/introduction-to-nightfall-audit.md)\n- [Overview](https://help.nightfall.ai/audit/google-drive-audit/overview.md)\n- [Select Integration](https://help.nightfall.ai/audit/google-drive-audit/select-integration.md)\n- [Select Scope](https://help.nightfall.ai/audit/google-drive-audit/select-scope.md)\n- [Detection Rules](https://help.nightfall.ai/audit/google-drive-audit/detection-rules.md)\n- [Automated Actions](https://help.nightfall.ai/audit/google-drive-audit/automated-actions.md)\n- [Review Configurations](https://help.nightfall.ai/audit/google-drive-audit/review-configurations.md)\n- [Analyzing Google Drive Audit Results](https://help.nightfall.ai/audit/google-drive-audit/analyzing-google-drive-audit-results.md)\n- [Overview](https://help.nightfall.ai/audit/github-audit/overview.md)\n- [Select Integration](https://help.nightfall.ai/audit/github-audit/select-integration.md)\n- [Configure Scope](https://help.nightfall.ai/audit/github-audit/configure-scope.md)\n- [Select Detection Rules](https://help.nightfall.ai/audit/github-audit/select-detection-rules.md)\n- [Review Configurations](https://help.nightfall.ai/audit/github-audit/review-configurations.md)\n- [Overview](https://help.nightfall.ai/audit/salesforce-audit/overview.md)\n- [Salesforce Integration](https://help.nightfall.ai/audit/salesforce-audit/salesforce-integration.md)\n- [Configure Scope](https://help.nightfall.ai/audit/salesforce-audit/configure-scope.md)\n- [Detection Rules](https://help.nightfall.ai/audit/salesforce-audit/detection-rules.md)\n- [Automated Actions](https://help.nightfall.ai/audit/salesforce-audit/automated-actions.md)\n- [Review Configurations](https://help.nightfall.ai/audit/salesforce-audit/review-configurations.md)\n- [Analyzing Salesforce Audit Results](https://help.nightfall.ai/audit/salesforce-audit/analyzing-salesforce-audit-results.md)\n- [Overview](https://help.nightfall.ai/audit/onedrive-audit/overview.md)\n- [OneDrive Integration](https://help.nightfall.ai/audit/onedrive-audit/onedrive-integration.md)\n- [Configure Scope](https://help.nightfall.ai/audit/onedrive-audit/configure-scope.md)\n- [Detection Rules](https://help.nightfall.ai/audit/onedrive-audit/detection-rules.md)\n- [Automated Actions](https://help.nightfall.ai/audit/onedrive-audit/automated-actions.md)\n- [Review Configurations](https://help.nightfall.ai/audit/onedrive-audit/review-configurations.md)\n- [Analyzing OneDrive Audit Results](https://help.nightfall.ai/audit/onedrive-audit/analyzing-onedrive-audit-results.md)\n\n## Frequently Asked Questions (FAQs)\n\n- [Nightfall FAQs](https://help.nightfall.ai/frequently-asked-questions-faqs/nightfall-faqs.md)\n- [End User FAQs](https://help.nightfall.ai/frequently-asked-questions-faqs/security-faqs/end-user-faqs.md)\n- [Email Encryption - Sender FAQs](https://help.nightfall.ai/frequently-asked-questions-faqs/sender-faqs/email-encryption-sender-faqs.md)\n- [Email Encryption - Receiver FAQs](https://help.nightfall.ai/frequently-asked-questions-faqs/email-encryption-receiver-faqs.md)\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information, you can query the documentation dynamically by asking a question.\nPerform an HTTP GET request on a page URL with the `ask` query parameter:\n\n```\nGET https://help.nightfall.ai/welcome-to-nightfall-documentation.md?ask=\n```\n\nThe question should be specific, self-contained, and written in natural language.\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:12:28.820Z","2026-08-04T18:29:08.729Z","a07277ab-60ad-4415-a794-bc5eeab94854",[],[],[],"help.nightfall.ai / jira / policies.md","helpnightfallai-jira-policiesmd","https://help.nightfall.ai/jira/policies.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/jira/policies.md).\n\n# Configure Policies in Nightfall for Jira\n\nDLP policies are a set of rules that include specific conditions, actions, and exceptions that monitor and filter data. These policies also enable you to remediate any leakage of sensitive information from within your organization.\n\n- You can set up policies to scan data that is sent through some or all applications within your organization. \n- You can configure policies and choose to not apply them all the time.\n\nBefore you define a policy, or a set of policies, we recommend that you define the objectives of each policy, which can then be fulfilled when you configure the policy.\n\nHere are a few important questions to ask before configuring your policies:\n\n- What data do you plan to monitor?\n- Where within the organization do you want to monitor?\n- What should be the scope of each policy?\n- What conditions must apply for the policy to match?\n- What exceptions/exclusions can be allowed?\n- What remediation actions should the policy take?\n\nYou can now configure policies on the Jira integration to determine which projects must be monitored, and which ones excluded. You can also automate the remediation actions that you want Nightfall to perform on a policy violation.\n\nConfiguring DLP policies on Jira involves the following steps:\n\n{% content-ref url=\"/pages/RjzQqPKXTY0L8GL907Rn\" %}\n[Jira App Selection](/jira/policies/integration.md)\n{% endcontent-ref %}\n\n{% content-ref url=\"/pages/nR1jTLykftn1dNAAULiD\" %}\n[Configure Scope in Nightfall for JIRA](/jira/policies/scope.md)\n{% endcontent-ref %}\n\n{% content-ref url=\"/pages/WasLjQx2N75IWIfWg7aK\" %}\n[Select Detection Rules in Nightfall for JIRA](/jira/policies/detection_rules.md)\n{% endcontent-ref %}\n\n{% content-ref url=\"/pages/9F5IpAoG68qYzlE7mm61\" %}\n[Configuring Advanced Settings in Nightfall for JIRA](/jira/policies/advanced_settings.md)\n{% endcontent-ref %}\n\n{% content-ref url=\"/pages/kW6kAJt9KUcoYqhcBBGG\" %}\n[Configure Risk Score for Jira](/jira/policies/risk_score.md)\n{% endcontent-ref %}\n\n{% content-ref url=\"/pages/XdZfSEHx7rxDygIkRbdY\" %}\n[Manage Jira Events](/jira/policies/events.md)\n{% endcontent-ref %}\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/jira/policies.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:15:42.292Z","2026-08-04T17:15:42.321Z","d8b257be-9ad8-4113-a876-03234396d676",[],[],[],"help.nightfall.ai / jira / installation.md","helpnightfallai-jira-installationmd","https://help.nightfall.ai/jira/installation.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/jira/installation.md).\n\n# Install Nightfall for Jira\n\nThis document explains the process of installing Nightfall for Jira. \n\n## Prerequisites\n\nThe installation of Jira integration requires you to have the following prerequisites\n\n- An Atlassian tenant with Jira enabled. \n- Standard Atlassian user account used as a Service Account - A regular Atlassian user account (has a password, can log into the Atlassian UI) that is shared or dedicated for system use rather than belonging to a specific person.\n - Has a password and can log in via the browser\n - Has its own dedicated email (e.g., [`nightfall-jira@company.com`](mailto:nightfall-jira@company.com) or an AD account)\n - ❌ Not Supported - Atlassian Service Account (Programmatic)\n\n Atlassian's native \"service account\" feature, designed for programmatic access only.\n\n - No password - cannot log in via the browser UI\n - Cannot complete Nightfall's OAuth consent screen\n - Also lacks the `issue:redact` scope, so Jira historical redaction would not work even if supported\n - Cannot be created programmatically (must be created manually in Atlassian Admin)\n- You must have access and must be logged in to the Atlassian account. \n\n## How Nightfall Uses the Connected Account\n\n| **Function** | **Credentials Used** |\n| ---------------------------------------------- | ---------------------------------------- |\n| OAuth flow - discovering Jira/Confluence sites | Installing user (service account) |\n| All DLP scanning | Nightfall App credentials - NOT the user |\n| Jira historical redaction API | Installing user (service account) |\n| All other APIs | Nightfall App credentials |\n\n**Key implication:** Revoking the service account's Atlassian permissions will NOT affect scanning. It only affects Jira historical redaction, which falls back to replacing text with `[Sensitive Data Removed]` instead of native API-based redaction.\n\n## Recommended Setup: Service Account Installation\n\nFollow these steps for a **fresh installation** or when **re-authorizing** to switch from an individual account to a service account.\n\n**Step 1 - Create the Atlassian Service Account**\n\nCreate a dedicated Atlassian user account to serve as the service account:\n\n1. Use a shared mailbox or AD account email (e.g., `nightfall-jira@company.com`)\n2. This must be a **standard Atlassian user account** - it needs a password and must be able to log into Atlassian via the browser\n3. Assign it the necessary Jira/Confluence admin permissions to complete the OAuth flow\n\n**Step 2 - Add the Service Account as a Nightfall System Administrator**\n\n> This step is critical. It ensures that the service account email (not a personal admin's email) is shown in Nightfall's Integrations page.\n\n1. Log into the Nightfall console as a current admin\n2. Go to **Settings → Users**\n3. Invite the service account email (e.g., `nightfall-jira@company.com`) and assign the **System Administrator** role\n4. Have the service account complete the Nightfall invitation/login flow\n\n**Step 3 - Install / Re-authorize Jira Using the Service Account**\n\nUse an **incognito/private browser window** for the entire flow to avoid conflicts with any personally logged-in Atlassian accounts.\n\n1. Open an incognito tab\n2. **Log into Jira/Atlassian** with the service account credentials\n3. **In the same incognito tab**, open the Nightfall console and log in as the **service account user** (the System Administrator added in Step 2)\n4. Navigate to **Configuration → Integrations → Jira**\n5. Click **\"+ Add Site\"**\n6. Select your Atlassian site from the dropdown\n7. Click **\"Accept\"** to grant Nightfall permissions\n8. Click the **Jira icon** to open the Atlassian Marketplace\n9. Select **\"Get it now\"** on the DLP for Jira app page\n10. Choose your site and click **\"Install app\"** → confirm **\"Get it now\"**\n\nAfter installation, Nightfall automatically configures the integration and shows an \"Alert Destination\" label.\n\n**Step 4 - Verify**\n\nIn Nightfall Console → Integrations → Jira, confirm:\n\n1. The **email shown** matches the service account email (e.g., `nightfall-jira@company.com`)\n2. The site appears with \"Alert Destination\" status\n\nIf the email shown matches the service account - setup is complete and correct.\n\nWhen you return to the Nightfall application, the appearance of the JIRA icon changes once the **DLP for Jira** app is installed. This confirms the successful installation of the **DLP for Jira** app. \n\n{% hint style=\"info\" %}\n**Important**\n\nOnce you install the DLP for Jira application on an Atlassian account, Nightfall automatically configures the Alert platform with this Jira account. You can confirm this by navigating to **Settings** -> **Alert platforms** in Nightfall.\n{% endhint %}\n\n

\n\nIn the Atlassian integration page, there is a phrase attached to this Atlassian account known as **Alert Destination** which also confirms that this Jira is used as an Alert platform.\n\n

\n\nWhen you install **DLP for Jira** on another Atlassian account, the alert destination automatically shifts to the new Atlassian account on which the DLP for Jira is recently installed.\n\n## Re-authorizing an Existing Connection (No Fresh Install Needed)\n\nIf the integration already exists but was set up with an individual admin account, you can switch to a service account without disconnecting or reinstalling.\n\n1. Complete Steps 1 and 2 above (create service account + add to Nightfall as System Admin)\n2. Open an incognito tab; log into Jira with the service account\n3. Open Nightfall console in the same tab; log in as the service account Nightfall user\n4. Go to **Integrations → Jira → click \"+ Add Site\"**\n5. Complete the OAuth flow with the service account\n\nThe credentials are **overwritten in-place**. No disruption to policies, violations, or scanning.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/jira/installation.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:15:32.515Z","2026-08-04T17:15:41.191Z","32396a9e-28dc-4ce2-ba29-9262639aca4b",[],[],[],"help.nightfall.ai / jira / getting_started.md","helpnightfallai-jira-getting-startedmd","https://help.nightfall.ai/jira/getting_started.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/jira/getting_started.md).\n\n# Getting Started\n\nNightfall DLP for Jira offers a cloud-native data leak protection solution that monitors and protects any sensitive data from leaking.\n\nNightfall can scan all Jira item types (Tickets, Attachments, and Comments). Scans will include archived items, but not deleted items. Only fields of type free-text fields are scanned: \n\n- Summary (title)\n- Description (body)\n- Labels\n- All custom fields \n\nFields such as Assignee, Reporter, etc are not scanned.\n\nGo through the following steps before you can configure policies on your implementation of Nightfall DLP for Jira.\n\n- [Install Nightfall for Jira](/jira/installation.md)\n- [Configure Policies in Nightfall for Jira](/jira/policies.md)\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/jira/getting_started.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:15:29.974Z","2026-08-04T17:15:30.014Z","b610f6b5-87ea-40e6-affc-289aa7c43b1d",[],[],[],"help.nightfall.ai / google-drive / policies.md","helpnightfallai-google-drive-policiesmd","https://help.nightfall.ai/google-drive/policies.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/google-drive/policies.md).\n\n# Configure Policies for Google Drive\n\nDLP policies are a set of rules that include specific conditions, actions, and exceptions that monitor and filter data. DLP policies also enable you to remediate any leakage of sensitive information from within your organization.\n\n- You can set up policies to scan data that is sent through some or all applications within your organization. \n- You can configure policies and choose to not apply them all the time.\n\nBefore you define a policy, or a set of policies, we recommend that you define the objectives of each policy, which can then be fulfilled when you configure the policy.\n\nHere are a few important questions to ask before configuring your policies:\n\n- What data do you plan to monitor?\n- Where within the organization do you want to monitor?\n- What should be the scope of each policy?\n- What conditions must apply for the policy to match?\n- What exceptions/exclusions can be allowed?\n- What remediation actions should the policy take?\n\nYou can now configure policies on the Google Drive integration to determine which drives and files must be monitored, and which ones excluded. You can also automate the remediation actions that you want Nightfall to perform on a policy violation.\n\nPolicy configuration consists of the following steps. \n\n- [Google Drive App Selection](/google-drive/policies/integration.md)\n- [Configure Scope for Google Drive](/google-drive/policies/scope.md)\n- [Configure Detection Rules for Google Drive](/google-drive/policies/detection_rules.md)\n- [Configure Advanced Settings for Google Drive](/google-drive/policies/advanced_settings.md)\n- [Risk Score for Google Drive](/google-drive/policies/configure_risk.md)\n- [Manage Google Drive Events](/google-drive/policies/events.md)\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/google-drive/policies.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:14:21.595Z","2026-08-04T18:41:20.001Z","1d010fd6-a188-4742-8e8b-d5b4db0d4670",[],[],[],"help.nightfall.ai / google-drive / getting_started.md","helpnightfallai-google-drive-getting-startedmd","https://help.nightfall.ai/google-drive/getting_started.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/google-drive/getting_started.md).\n\n# Getting Started\n\nNightfall's Data Detection & Response solution for Google Drive automatically detects and secures sensitive data in Google Drive while preventing inappropriate sharing. Monitors all data in Google Drive in real-time and scans historical files, with direct API integration.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/google-drive/getting_started.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:14:19.283Z","2026-08-04T17:14:19.324Z","41e22eb5-a5e3-494b-ac6b-8c19b7009705",[],[],[],"help.nightfall.ai / gmail / remediation.md","helpnightfallai-gmail-remediationmd","https://help.nightfall.ai/gmail/remediation.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/gmail/remediation.md).\n\n# Remediation on Nightfall for Gmail\n\nThis document explains the impact on end-users and Google Workspace admins when the automated actions in Gmail DLP (Block, Quarantine, or Encrypt) are implemented. \n\nTo learn more about configuring automated actions for Gmail DLP, see, [Automated actions](/gmail/policies/advanced_settings.md#automated-actions).\n\n## Block\n\nWhen an Email is blocked, the end user receives an Email from Nightfall that informs them that their Email was blocked. End users receive this email from . Apart from this email, end users also get the original Email which was blocked.\n\nThe Email looks as follows. \n\n

\n\nThe status of the Event is also automatically changed to Blocked when the Email is blocked.\n\n## Quarantine\n\nWhen an email is quarantined, it is stored separately in a secure Gmail server. A Google Workspace admin must visit the server, review the quarantined email, and decide as to whether the email must be allowed to travel to the recipient or be blocked. \n\nTo access the quarantine emails:\n\n1. Login to your Google Workspace with an admin account.\n2. Click the menu icon.\n3. Select **Admin**.\n\n

\n\n4. In the left menu, expand **Apps** and then expand **Google Workspace**.\n5. Click **Gmail**.\n\n

\n\n6. Scroll down and click **Manage quarantines**.\n\n

\n\n7. Click **GO TO ADMIN QUARANTINE**.\n\n

\n\nThe list of all the quarantined emails is displayed. \n\n

\n\nClick any email to expand it. You can view three options. \n\n- **SHOW ORIGINAL** - This option displays the full email.\n- **ALLOW** - This option releases the email from quarantine and sends it to the recipient. You must select this option if you are confident that the sensitive data detected by Nightfall is false positive.\n- **DENY** - This option blocks the email and does not send it to the recipient. You must select this option if you are confident that the sensitive data detected by Nightfall is actually sensitive.\n\n

\n\n## Encrypt\n\nWhen an Email is encrypted, an additional event is created in the [Nightfall data encryption](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page), apart from the regular event created in Nightfall detection and response. The email is delivered to the recipient. An event is logged in Nightfall Nightfall detection and response with the Status **Encrypted**. \n\n## Understanding Gmail DLP Events\n\nWhen an end user violates a policy in Gmail DLP, an Event is generated based on the notification settings configured by you in the policy configurations. To learn more about Events, see [Data Detection and Response Events](/dashboard/sdp_events.md).\n\nTo view the Events from the Nightfall Console:\n\n1. Click **Detection and Response** from the left pane.\n2. (Optional) Modify the days filter to view Events prior to last 7 days. By default the Events recorded in the **Last 7 Days** are displayed.\n3. Apply filters to view only the Gmail DLP Events.\n\n

\n\nOnce you filter the Events to view only the Confluence Events, you can refer to the [Data Detection and Response Events](/dashboard/sdp_events.md#event-list-view) section to learn more about the available options. \n\n4. Click on any of the Events to view details of an Event. You may click anywhere in the row of an Event that you wish to inspect. Details will be present via a side panel.\n\n## Event Actions\n\nNightfall allows you to take various action on Events. When you take an action on an Event, the status of the Event changes accordingly. To learn more about Event status, refer to the [Event Status](/dashboard/sdp_events/status.md) document.\n\nIn Gmail, you can take actions either from the Event list view page or the Event detail view page. On the Event list view page, you can click the ellipsis menu to view the available list of actions. \n\n

\n\nOn the Event detail view, you can view the applicable actions from the actions section at the bottom.\n\nTo view the complete list of actions, applicable to all the integrations, you can refer to the [Applying Actions on Events](/dashboard/sdp_events/event_actions.md) document. \n\nThe list of actions supported for Confluence are as follows. Some of these actions are common to other integrations as well. \n\n- **Copy Event Link**: The action copies the link to the Event. You can save or send this link to directly open the Event. This action is available only on the Event detail view.\n- **Ignore**: The ignore action flags Nightfall to ignore all the findings in the Event and may be taken if you find the findings false positive. This action marks the Event as resolved and moves it to the Resolved section. You can undo this action. \n- **Acknowledge**: You can take this action to notify other users that you have looked into this Event and will take suitable action in future. \n- **Notify Email**: This action notifies the end user who added the sensitive data file to the OneDrive about the event, through email.\n- **Notify Slack**: This action notifies the end user who added the sensitive data file to the OneDrive about the event, through Slack.\n- **Send to JIRA**: This action creates a JIRA ticket for the Event. You can pick a project and Issue type while creating the JIRA ticket and can assign the JIRA ticket to the end-user.\n- **Resolve**: This action must be taken when the sensitive data is removed completely. This action resolves the Event.\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/gmail/remediation.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:29:59.942Z","2026-08-04T18:30:36.849Z","e3472598-1819-41ec-aa42-64cdc67e6538",[],[],[],"help.nightfall.ai / gmail / policies.md","helpnightfallai-gmail-policiesmd","https://help.nightfall.ai/gmail/policies.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/gmail/policies.md).\n\n# Nightfall Policies for Gmail\n\nDLP policies are a set of rules that include specific conditions, actions, and exceptions that monitor and filter data. DLP policies also enable you to remediate any leakage of sensitive information from within your organization.\n\n- You can set up policies to scan data that is sent through some or all applications within your organization. \n- You can configure policies and choose to not apply them all the time.\n\nBefore you define a policy or a set of policies, we recommend that you define the objectives of each policy, which can then be fulfilled when you configure the policy.\n\nHere are a few important questions to ask before configuring your policies:\n\n- What data do you plan to monitor?\n- Where within the organization do you want to monitor?\n- What should be the scope of each policy?\n- What conditions must apply for the policy to match?\n- What exceptions/exclusions can be allowed?\n- What remediation actions should the policy take?\n\nYou can now configure policies on the Gmail integration to determine which repositories are monitored, and which ones are excluded from monitoring. You can also automate the remediation actions that you want Nightfall to perform on a policy violation.\n\n## Creating Policies in Nightfall for Gmail\n\nThe process of creating policies in Nightfall consists of six stages enlisted as follows. \n\n[Integration](https://help.nightfall.ai/nightfall-ai/gmail-dlp/gmail-policies/integration)\n\n[Detection Rules](/gmail/policies/detection_rules.md)\n\n[Advanced Settings](/gmail/policies/advanced_settings.md)\n\n[Creating Policy](/gmail/policies/risk_score.md)\n\n[Managing Violations](/gmail/policies/events.md)\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/gmail/policies.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T18:29:59.643Z","2026-08-04T18:29:59.669Z","6c4487e6-7cbb-4d37-9bb7-e1682c0dbdc2",[],[],[],"help.nightfall.ai / gmail / integration_alerts.md","helpnightfallai-gmail-integration-alertsmd","https://help.nightfall.ai/gmail/integration_alerts.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/gmail/integration_alerts.md).\n\n# Configure Alerts for Gmail\n\nNightfall DLP for Gmail supports the configuration of alerts at the policy level and at the integration level. Alerts for Gmail can be sent to the following alert destinations.\n\n- [Slack ](https://help.nightfall.ai/sensitive-data-protection/gmail-dlp/configuring-integration-alerts#configuring-slack-as-an-alert-channel)\n- [Email](https://help.nightfall.ai/sensitive-data-protection/gmail-dlp/configuring-integration-alerts#configuring-email-as-an-alert-channel)\n- [Webhook](https://help.nightfall.ai/sensitive-data-protection/gmail-dlp/configuring-integration-alerts#configuring-webhook-as-an-alert-channel)\n- [Jira Tickets](https://help.nightfall.ai/sensitive-data-protection/gmail-dlp/configuring-integration-alerts#configuring-jira-as-an-alert-channel)\n\n

\n\nWhen you configure alert settings at the integration level, the alert settings apply to all the policies, created for the Gmail DLP integration. However, when you configure alert settings specifically for a policy, which is created in the Gmail DLP integration, the alert settings are applicable only for that specific policy. \n\nThis document explains how to configure alerts at the integration level. To learn about how to configure alerts at the policy level, read [this document](/gmail/policies/advanced_settings.md#admin-alerting).\n\n## Prerequisites\n\n- To use Slack as an alert platform, you must first perform the required Slack configurations. You can refer to [this document](https://help.nightfall.ai/nightfall-ai/detection/setting-up-slack-as-an-alert-channel-in-nightfall) to learn more about how to configure Slack as an Alert platform. \n- To use Webhook as an alert platform, you must first perform the required Webhook configurations. You can refer to [this document](https://help.nightfall.ai/nightfall-ai/operationalizing-dlp/integrating-with-security-tools/integrating-with-siem#configuring-outgoing-webhooks)[ ](https://help.nightfall.ai/nightfall-ai/operationalizing-dlp/integrating-with-security-tools/integrating-with-siem#configuring-outgoing-webhooks)to learn more about how to configure Webhook as an Alert platform. \n- To use JIRA as an alert platform, you must have the DLP for the JIRA app installed from the [Atlassian Marketplace](https://marketplace.atlassian.com/apps/1226823/dlp-for-jira-nightfall-ai?tab=overview\\&hosting=cloud). You can read more about the DLP for JIRA integration [here](https://help.nightfall.ai/nightfall-ai/nightfall-for-jira/getting-started/installing-nightfall-for-jira). \n\n## Configure Alerts at the Integration Level \n\nYou can configure alerts at the integration level once you have installed the Nightfall for Gmail DLP integration. \n\nTo configure alerts at the integration level:\n\n1. Navigate to the Gmail DLP integration\n2. Scroll down to the **Alerting** section.\n3. You can configure one or multiple alert channels. \n\n### Configuring Slack as an Alert Channel\n\n1. To configure Slack as an alert channel, click **+ Slack channel**.\n\n

\n\n2. In the **Slack alert channel** field, enter the name of the Slack channel in which you wish to receive the alerts. \n3. Click **Save**. \n\n

\n\nA confirmation pop-up box is displayed to confirm if the Slack channel (entered in the second step) must be used only for Gmail DLP integration or all the Nightfall integrations. \n\n4. Select **No, only integration level** to use the Slack channel only for Gmail DLP, or select **Yes, please** to use the selected Slack channel for all the Nightfall integrations. \n\n

\n\n### Configuring Email as an Alert Channel\n\n1. Click **+ Email**.\n\n

\n\n2. Enter the Email ID of the recipient who should receive the notifications**.** \n3. Click **Save.** \n\n

\n\nA confirmation pop-up box is displayed to confirm if the Email ID (entered in the second step) must be used only for Gmail DLP integration or all the Nightfall integrations. \n\n4. Select **No, only integration level** to use the Slack channel only for Gmail DLP, or select **Yes, please** to use the selected Slack channel for all the Nightfall integrations. \n\n

{\n  \"service\": \"nightfall\",\n  \"test\": true,\n  \"timestamp\": \"2024-03-07T23:18:39Z\"\n}\n

\n\nThis is part of alert event consumption and can be ignored. \n{% endhint %}\n\n### **Configuring Jira as an Alert Channel**\n\n1. Click **+ Jira Ticket.**\n2. Select a JIRA project from the **Jira Project** drop-down menu.\n3. Select an issue type from the **Issue Type** drop-down menu. \n4. (Optional) Add comments to be added in the JIRA ticket. \n5. Click **Save changes**.\n\n

\n\nA confirmation pop-up box is displayed to confirm if the JIRA settings configured for the Gmail DLP integration must be applied to all the other Nightfall integrations too. \n\n6. Select **No, only integration level** to use the configurations only for Gmail DLP, or select **Yes, please** to use the selected JIRA configurations for all the Nightfall integrations. \n\n

\n\n## Configure End-User Notifications\n\nWhen an Event is triggered, Nightfall sends a notification to the end-user whose actions triggered the Event. While notifying the end-user, Nightfall also sends a text message. You can draft the text message to be sent to the end-user. This message applies to all the policies. Click **Save changes** once done.\n\n

State of existing Nightfall Violation	Developer Action on a file in GitHub repo	Automated actions due to Deduplication
No existing Event	Introduce sensitive data	New Event Created
Active Event not in a resolved state	Additional code with sensitive data pushed	Increment finding(s) in the existing Event Create an Event with all the new findings
Active Event not in a resolved state	Code with sensitive findings redacted	Number of findings in the existing Event updated If no finding remaining then the Event is marked resolved
Event is in a resolved state	Additional code with sensitive data pushed	New Event created

\n\nThe following table summarises the treatment of a GitHub violation with Deduplication in action when the developer(s) clones/merges a GitHub branch.\n\n| State of existing Nightfall Event | Developer Action on a file in GitHub repo | Automated actions due to Deduplication |\n| ------------------------------------ | ------------------------------------------------ | --------------------------------------------------------------------------------------------- |\n| No existing Event | Branch Clone | No new Events |\n| Active Event not in a resolved state | Branch Clone |

No new Events in the original branch
No Events in the cloned branch

No new Events
Existing Events from the Cloned Branch resolved

|\n\nWhen an Event is automatically resolved by the GitHub Deduplication feature (as a result of sensitive data being removed from the concerned GitHub file/repo) the log section of the Event displays a **Resolved automatically** message as shown in the following image. \n\n

\n\n## Nightfall Events\n\nTo view the on the Nightfall Console:\n\n1. Navigate to the **Detection and Response** from the left menu.\n2. (Optional) Modify the days filter to view Events prior to last 7 days. By default the Events recorded in the **Last 7 Days** are displayed.\n\n

\n\n3. Apply filters to view only the GitHub Events. \n\n

\n\nOnce you filter the Events to view only the GitHub Events, you can refer to the [Data Detection and Response Events](/dashboard/sdp_events.md#event-list-view) section to learn more about the available options. \n\n4. Click on any of the Events to view details of an Event. You may click anywhere in the row of an Event that you wish to inspect. Details will be present via a side panel.\n\n

\n\nThe side panel (or the Event detail view) is divided into three separate sections. The first section has information about the occurrence of individual findings with a preview. The third section is an activity log for the Event. Both these sections reveal information that is common across all sources/integrations. You can refer to these common sections in the [Data Detection and Response Events](/dashboard/sdp_events.md#event-detail-view) section.\n\nThe second section displays details that are source / integration specific and so the details vary from one integration to the other. \n\n## Event Actions\n\nNightfall allows you to take various action on Events. When you take an action on an Event, the status of the Event changes accordingly. To learn more about Event status, refer to the [Event Status](/dashboard/sdp_events/status.md) document.\n\nIn GitHub, you can take actions either from the Event list view page or the Event detail view page. On the Event list view page, you can click the ellipsis menu to view the available list of actions. \n\n

\n\nOn the Event detail view, you can view the applicable actions from the actions section at the bottom.\n\n

\n\nTo view the complete list of actions, applicable to all the integrations, you can refer to the [Applying Actions on Events](/dashboard/sdp_events/event_actions.md) document. \n\nThe list of actions supported for GitHub are as follows. Some of these actions are common to other integrations as well. \n\n- **Copy Event Link**: The action copies the link to the Event. You can save or send this link to directly open the Event. This action is available only on the Event detail view.\n- **View in GitHub**: This action redirects to the relevant repository that contains the sensitive data in the source GitHub. While this action is available only on the Event detail view, please note that relevant access to the document in source GitHub repository should be present.\n- **Download Original Content**: This action downloads the original content that contains sensitive data. If the content is deleted or moved to a different location within GitHub, this action fails. This action is available only on the Event detail view.\n- **Send to JIRA**: This action creates a JIRA ticket for the Event. You can pick a project and Issue type while creating the JIRA ticket and can assign the JIRA ticket to the end-user\n- **Acknowledge**: You can take this action to notify other users that you have looked into this Event and will take suitable action in future. \n- **Ignore**: The ignore action flags Nightfall to ignore all the findings in the Event and may be taken if you find the findings false positive. This action marks the Event as resolved and moves it to the Resolved section. You can undo this action. \n- **Notify Email**: This action notifies the end user who added the sensitive data in GitHub about the event, through email.\n- **Notify GitHub**: This action notifies the end user who added the sensitive data in GitHub about the event, through GitHub. To learn more about how to check notifications in GitHub, see [#viewing-notifications-in-github](#viewing-notifications-in-github \"mention\").\n- **Resolve**: This action must be taken when the sensitive data is removed completely from the source file. This action resolves the Event. \n\n## Email Notifications\n\n- When a data leak occurs, GitHub sends an Email notification to end users, if end users have configured Email as a Notification method in their GitHub account.\n- Additionally, if Nightfall admins have configured Email Notification in [Admin Alerting](https://help.nightfall.ai/nightfall-ai/nightfall-for-github/configuring-policies/advanced-settings#admin-alerting), Nightfall admins receive the Email notification. \n- If Nightfall admins have configured Email Notification in the Automation section of [End user notification](https://help.nightfall.ai/nightfall-ai/nightfall-for-github/configuring-policies/advanced-settings#end-user-notification)[ ](https://help.nightfall.ai/nightfall-ai/nightfall-for-github/configuring-policies/advanced-settings#end-user-notification)settings, end users receive an email from Nightfall. This Email allows end users to take actions from within the Email.\n\nThe Email received from by Nightfall Admins and end-users (if configured), looks as follows. \n\n

\n\n## Viewing Notifications in GitHub\n\nIf you have configured GitHub as a Notification in the Automation section of [End User Notification](https://help.nightfall.ai/nightfall-ai/nightfall-for-github/configuring-policies/advanced-settings#end-user-notification), end users can view the violation notification from within GitHub. \n\nOpen the file that triggered the violation. A comment is generated by Nightfall which also has the remediation options. The available options are based on the settings you configured in the Automation section of [End User Notification](https://help.nightfall.ai/nightfall-ai/nightfall-for-github/configuring-policies/advanced-settings#end-user-notification). \n\n{% hint style=\"info\" %}\nIf an end-user adds sensitive information in a feature branch and merges it with the main branch, Nightfall comments on this pull request. \n\nIf an end-user adds sensitive information in the main branch and commits it, Nightfall comments on this GitHub commit. \n\nThe Nightfall comment is created by **nightfall-for-github** bot. \n{% endhint %}\n\nIn the following image, the Nightfall comment has two options; **Report as False Positive** and **Report as False Positive with Business Justification**. These options are displayed because they were enabled in the [End-User Remediation](https://help.nightfall.ai/nightfall-ai/nightfall-for-github/configuring-policies/advanced-settings#end-user-remediation) section of the policy.\n\n

\n\nAdditionally, if end-users have configured GitHub to receive Notifications, they can also view the violation under the Notifications page. This Notification also tags the end-user. \n\nTo view the Violation message under GitHub notifications, end-users must execute the following steps. \n\n1. Click the GitHub Notifications icon.\n2. Select the Notification which has a tag (mention).\n3. Scroll down to view the Notification.\n\n

\n\n### Enabling Notifications in GitHub\n\nTo view Notifications from within GitHub end-users must enable the GitHub notifications. The steps to enable GitHub notifications are as follows. \n\n1. Click on your GitHub account icon and select **Settings**.\n2. Click **Notifications** from the left pane.\n3. Under **Subscriptions**, enable GitHub notifications for the **Participating, @mentions and custom** section.\n4. Click **Save**. \n\n


Getting Started	Learn how to create a Nightfall API key, Detectors, Detection rules, and Polices	/pages/NeXWlxIEjeijdZ9fDAmE	/files/p6smoWXMrlWVrnGdyMd1
Nightfall APIs	Nightfall Scan and Workflow APIs enable you to integrate DLP protection programatically	https://help.nightfall.ai/nightfall-firewall-for-ai/nightfall-apis/dlp-apis-firewall-for-ai-platform	/files/tRPs2uqO8Y26ZQtuYpji
SDKs	Learn how to leverage the Nightfall Software Development Kits (SDKs)	/pages/MaWfV3PsrIJBe7qilmgh	/files/CZCVE7sc59a8suyB2Ch5
Language Specific Guides	Learn how to use Nightfall's APIs/SDKs with specific programming languages.	/pages/SuQtZOYIjtUwF3EOs2zx	/files/gWZtlLo14TJTSmXbBOXh
Integration Tutorials	Learn how to integrate Nightfall into some GenAI apps and datastores.	/pages/lcPDqZnoUIUvD2sxJLvw	/files/ktNPOF4GQEvnJaw35J6i
Popular Use Cases	Review popular scenarios and apply them to your DLP use case.	/pages/4agObkPH5rmLf9gEswKM	/files/Pnik5pmYBhEe305xGhN0
Detection Playground	A code free environment for test driving Firewall for AI.	https://playground.nightfall.ai/	/files/j5jPK8zjTx8Os0hv7f6Z

\n\n{% hint style=\"info\" %}\nIf you have not yet subscribed to the Confluence integration, the **Manage** button is replaced by **Contact Sales** button. Click **Contact Sales** to sync up with the Nightfall sales team to discuss how you can subscribe to the Confluence integration.\n{% endhint %}\n\nYou can see that Nightfall lists the Atlassian accounts to which you have logged in. In the following image, there are two Atlassian accounts. \n\n4. Click **+ Add Site** to authorize the Atlassian account. \n\n{% hint style=\"info\" %}\nIf you do not have Confluence or JIRA set up on your Atlassian account, you cannot see the respective icons under the **App(s)** column. \n{% endhint %}\n\nYou are navigated to the Atlassian site. \n\n

\n\n5. Under the **Use app on** drop-down menu, choose the Atlassian site that you wish to authorize and install the **DLP for Confluence** app. \n\n{% hint style=\"info\" %}\nIf you have a single Atlassian account, Nightfall automatically selects the Atlassian account for authorization. This drop-down menu is active only when you have multiple Atlassian accounts. \n{% endhint %}\n\n

\n\n6. Click **Accept**. \n\n

\n\n7. Click the Confluence icon for the Atlassian account that you authorized in the previous step. \n\n

\n\nYou are navigated to the Atlassian Marketplace where the **DLP for Confluence** app is located.\n\n8. Click **Get it now**.\n\n

\n\n9. Click **Get it Now** on the **Add to Confluence** window.\n\n

\n\nOnce the installation is completed, you can view a pop-up box at the bottom left of your screen. You can click **Manage app** to customize the settings. \n\n

\n\nWhen you return to the Nightfall application, the appearance of the Confluence icon changes once the **DLP for Confluence** app is installed. This confirms the successful installation of the **DLP for Confluence** app. \n\n

\n\n
\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/confluence/installation.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:14:22.342Z","2026-08-04T18:41:14.418Z","ab0eab35-28b8-4612-b6bd-c6c6e1e36084",[],[],[],"help.nightfall.ai / confluence / getting_started.md","helpnightfallai-confluence-getting-startedmd","https://help.nightfall.ai/confluence/getting_started.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/confluence/getting_started.md).\n\n# Getting Started\n\nNightfall DLP for Confluence offers a cloud-native data leak protection solution that monitors and protects any sensitive data from leaking.\n\nNightfall can scan all Confluence assets (attachments, comments, spaces, blogs, and pages). Scans will include archived items, but not deleted items. Only fields of type free-text fields are scanned.\n\nGo through the following steps before you can configure policies on your implementation of Nightfall DLP for Confluence.\n\n- [Installing](/confluence/installation.md)\n- [Configuring Policies](https://help.nightfall.ai/nightfall-ai/nightfall-for-confluence/configuring-policies)\n\n## Confluence Page Restrictions\n\nNightfall throws an error while scanning certain pages/spaces in your Confluence instance. This issue is related to certain custom page permission restrictions for those specific Confluence pages. With base page restrictions set, the Nightfall app is unable to view edits on these page.\n\nWhen **Page restrictions** are set on a page/space, our app is no longer able to see it, so when scanning is attempted on items from that page, our API requests fail. For a short term solution, you can add our app 'Nightfall DLP for Confluence' to have 'View' access on the page.\\\n\\\n**Note**: We are currently working on a longer term solution for this issue, and are in discussion with Atlassian directly\n\nIf you are not seeing these pages being scanned and want to check if this restriction is in place, this can be checked as seen below:\n\n**Checking Workspace Permissions:**\n\nChecking and Updating Workspace Permissions\n\n**Checking Page Restrictions:**\n\nChecking and Updating Confluence Page Restrictions\n\nIf you have any questions about these restrictions, or are unsure how to workaround, please file a support ticket with us, or you can reach out to .\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/confluence/getting_started.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:14:21.969Z","2026-08-04T18:41:18.313Z","0a826794-8206-44e5-bb0e-47a12a8dc5d3",[],[],[],"help.nightfall.ai / confluence / faqs.md","helpnightfallai-confluence-faqsmd","https://help.nightfall.ai/confluence/faqs.md","> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/confluence/faqs.md).\n\n# FAQs\n\n[Can Nightfall scan Confluence pages with page restrictions?](/confluence/faqs/page-restrictions.md)\n\n***\n\n# Agent Instructions\n\nThis documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.\n\n## Querying This Documentation\n\nIf you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.\n\nPerform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:\n\n```\nGET https://help.nightfall.ai/confluence/faqs.md?ask=&goal=\n```\n\n`ask` is the immediate question: it should be specific, self-contained, and written in natural language.\n`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.\n\nThe response will contain a direct answer to the question and relevant excerpts and sources from the documentation.\n\nUse this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.\n","2026-08-04T17:15:29.482Z","2026-08-04T17:15:29.515Z","72c25b0c-002f-45ac-a9cb-db2bd4550b99",[],[],[],"Google Workspace Directory Service | Nightfall Documentation","google-workspace-directory-service-nightfall-documentation","https://help.nightfall.ai/nightfall_settings/directory_sync/google_workspace","This document explains the process of adding your Google Workspace tenant to Nightfall to enable Directory Sync. Once you add Google Workspace to Nightfall, you can sync users and user groups data from Google Workspace to Nightfall. To get an overview of the Directory Sync feature in Nightfall, you can read [this article](https://help.nightfall.ai/nightfall_settings/directory_sync) and then proceed with this document.\n\nTo install Google Directory:\n\n1. Click the **Settings** button in Nightfall.\n\n2. Click the **Directory Sync** tab.\n\n3. Click **Add directory**.\n\n4. Select **Google Workspace** as the identity provider.\n\n5. Copy the **Client ID** and **OAuth Scope ID**. Store these values in a secure place. You require them in the further steps.\n\n6. Login to your Google Workspace with an admin account.\n\n7. Click the menu icon.\n\n8. Select **Admin**.\n\n9. In the Admin console left pane, expand **Security** and then expand **Access and data control**.\n\n10. Click **API controls**.\n\n11. Click **MANAGE DOMAIN WIDE DELEGATION** under **Domain wide delegation**.\n\n12. Click **Add New**.\n\n13. Paste the **Client ID** copied from the Nightfall app, in the **Client ID** field.\n\n14. Paste the **Scopes ID** copied from the Nightfall app, under **OAuth Scope** field\\*\\*.\\*\\* Use comma to add multiple scope IDs.\n\n15. Click **AUTHORIZE.**\n\n16. Return to the Nightfall app and click **Continue**.\n\n17. Click **Connect**.\n\nOnce the setup is completed, Nightfall displays the list of active and inactive users in your Google Workspace. Nightfall syncs with your Identity and Access Provider every four hours. Also, you can manually sync once every hour. To sync data manually, click the ellipsis menu and select **Refresh.**\n\nCurrently, once registered you cannot unregister an Identity and Access Provider from Nightfall. If you wish to unregister your Identity and Access Provider, please contact Nightfall support.\n","2026-08-04T18:32:58.930Z","2026-08-04T18:32:58.958Z","6f9417cb-fdfb-47e1-badc-a8349219c0b0",[],[],[],"Google Drive App Selection | Nightfall Documentation","google-drive-app-selection-nightfall-documentation","https://help.nightfall.ai/google-drive/policies/integration","In this stage, you select the Integration for which the policy is created. In this case, the Google Drive integration must be selected.\n\n1. Click **Policies** from the left menu.\n\n2. Click **+ New Policy**.\n\n3. Select **Sensitive Data**.\n\n4. Select the **Google Drive** integration.\n","2026-08-04T17:14:20.413Z","2026-08-04T18:41:18.590Z","4cf88d1f-8f19-4bb6-a844-e1aee91b00b6",[],[],[],"Gmail App Selection | Nightfall Documentation","gmail-app-selection-nightfall-documentation","https://help.nightfall.ai/gmail/policies/integration","In this stage, you select the Integration for which the policy is created. In this case, the Gmail integration must be selected.\n\n1. Click **Policies** from the left menu.\n\n2. Click **+ New Policy**.\n\n3. Select **Sensitive Data**.\n\n4. Select the **Gmail** integration.\n","2026-08-04T18:29:58.863Z","2026-08-04T18:29:58.883Z","56498d42-8b1c-4b73-9e41-f8829309ef8a",[],[],[],"GitHub App Selection | Nightfall Documentation","github-app-selection-nightfall-documentation","https://help.nightfall.ai/github/policies/integration","In this stage, you select the Integration for which the policy is created. In this case, GitHub integration must be selected.\n\n1. Click **Policies** from the left menu.\n\n2. Click **+ New Policy**.\n\n3. Select **Sensitive Data**.\n\n4. Select the **GitHub** integration.\n","2026-08-04T17:13:11.479Z","2026-08-04T18:41:06.444Z","a493ee32-a515-42b8-816d-19c5d42a64ee",[],[],[],"Getting Started With Nightfall for Slack | Nightfall Documentation","getting-started-with-nightfall-for-slack-nightfall-documentation","https://help.nightfall.ai/slack/getting_started","# Getting Started With Nightfall for Slack\n\nNightfall for Slack is offered in two variants:\n\n- Nightfall Pro DLP for Slack\n\n- Nightfall DLP for Slack Enterprise\n","2026-08-04T17:12:55.705Z","2026-08-04T18:29:09.345Z","3152cc3f-1348-439e-9921-53220c27dfa9",[],[],[],"Getting Started | Nightfall Documentation","getting-started-nightfall-documentation-10","https://help.nightfall.ai/notion/getting_started","Notion is a collaboration tool used for multiple tasks like note-taking, brainstorming ideas, project management, and so on. Since Notion can be used for multiple purposes and content created in Notion can be shared over the web, sensitive data like PII, credentials, and secrets could sprawl into Notion at an alarming rate.\n\nThis document explains how you can prevent sensitive data from being leaked through the Notion platform by using the Nightfall Notion integration.\n","2026-08-04T17:12:49.897Z","2026-08-04T18:28:52.714Z","ddf5e5fb-1542-4ece-9d5d-773d9e7f95ff",[],[],[],"getting-started-nightfall-documentation-7","https://help.nightfall.ai/microsoft-exchange-1/getting_started","Nightfall DLP for Microsoft SharePoint offers a cloud-native data leak protection solution that monitors presence of sensitive data in MS SharePoint.\n\nNightfall DLP for SharePoint provides a seamless approach to monitor your data in Microsoft SharePoint. Nightfall DLP scans content in SharePoint for sensitive data. Additionally, Nightfall also allows notifications to be sent to the Nightfall administrators and SharePoint users thus enabling them to take follow up steps in alignment with the organization's requirements.\n","2026-08-04T17:12:36.146Z","2026-08-04T18:28:55.853Z","d3b420ea-6801-48ae-b579-ac2fa043ca9a",[],[],[],"getting-started-nightfall-documentation-4","https://help.nightfall.ai/jira/getting_started","Nightfall DLP for Jira offers a cloud-native data leak protection solution that monitors and protects any sensitive data from leaking.\n\nNightfall can scan all Jira item types (Tickets, Attachments, and Comments). Scans will include archived items, but not deleted items. Only fields of type free-text fields are scanned:\n\n- Summary (title)\n\n- Description (body)\n\n- Labels\n\n- All custom fields\n\nFields such as Assignee, Reporter, etc are not scanned.\n\nGo through the following steps before you can configure policies on your implementation of Nightfall DLP for Jira.\n","2026-08-04T17:12:34.843Z","2026-08-04T18:28:55.180Z","d1d28b28-9c0f-4829-a702-975de8b860e7",[],[],[],"getting-started-nightfall-documentation-3","https://help.nightfall.ai/confluence/getting_started","Nightfall DLP for Confluence offers a cloud-native data leak protection solution that monitors and protects any sensitive data from leaking.\n\nNightfall can scan all Confluence assets (attachments, comments, spaces, blogs, and pages). Scans will include archived items, but not deleted items. Only fields of type free-text fields are scanned.\n\nGo through the following steps before you can configure policies on your implementation of Nightfall DLP for Confluence.\n\n## Confluence Page Restrictions[](https://help.nightfall.ai/confluence/getting_started#confluence-page-restrictions)\n\nNightfall throws an error while scanning certain pages/spaces in your Confluence instance. This issue is related to certain custom page permission restrictions for those specific Confluence pages. With base page restrictions set, the Nightfall app is unable to view edits on these page.\n\nWhen **Page restrictions** are set on a page/space, our app is no longer able to see it, so when scanning is attempted on items from that page, our API requests fail. For a short term solution, you can add our app 'Nightfall DLP for Confluence' to have 'View' access on the page. **Note**: We are currently working on a longer term solution for this issue, and are in discussion with Atlassian directly\n\nIf you are not seeing these pages being scanned and want to check if this restriction is in place, this can be checked as seen below:\n\n**Checking Workspace Permissions:**\n\nChecking and Updating Workspace Permissions\n\n**Checking Page Restrictions:**\n\nChecking and Updating Confluence Page Restrictions\n\nIf you have any questions about these restrictions, or are unsure how to workaround, please file a support ticket with us, or you can reach out to .\n","2026-08-04T17:12:34.427Z","2026-08-04T18:28:54.824Z","a17f93df-5ddd-414f-ab0d-2d56bb437d7a",[],[],[],"getting-started-nightfall-documentation-6","https://help.nightfall.ai/microsoft-exchange/getting_started","Nightfall DLP for Microsoft Exchange Online (aka Microsoft Exchange) offers a cloud-native data leak protection solution that monitors presence of sensitive data in MS Outlook.\n\nNightfall DLP for Exchange provides a seamless approach to monitor emails sent using Microsoft Outlook. Nightfall DLP scans messages in the mails for sensitive data. Additionally, Nightfall also allows notifications to be sent to the Nightfall administrators and Exchange users thus enabling them to take follow up steps in alignment with the organization's requirements.\n","2026-08-04T17:12:35.886Z","2026-08-04T18:28:55.722Z","723dde3f-80c1-42fe-a10a-31ed2a972f03",[],[],[],"getting-started-nightfall-documentation-2","https://help.nightfall.ai/google-drive/getting_started","Nightfall's Data Detection & Response solution for Google Drive automatically detects and secures sensitive data in Google Drive while preventing inappropriate sharing. Monitors all data in Google Drive in real-time and scans historical files, with direct API integration.\n","2026-08-04T17:12:34.156Z","2026-08-04T18:28:54.976Z","675ed285-4526-4e49-bd7a-0bf2385aad63",[],[],[],"getting-started-nightfall-documentation","https://help.nightfall.ai/github/getting_started","GitHub is a service that allows you to store and manage your code and other assets within repositories.\n\nNightfall DLP for GitHub protects your data, like API keys and secrets, from leakages that could happen when using GitHub. Nightfall scans commits to Git repositories, identifies sensitive information, and prevents it from being leaked.\n\nNightfall for GitHub supports the following cloud editions of GitHub:\n\n- Enterprise Cloud\n\n- Enterprise Servers\n\n- For Teams and Startups\n\nYou can install and authorize Nightfall DLP app package in GitHub.\n\n[Requirements](https://help.nightfall.ai/github/getting_started/requirements)\n\n[Installing Nightfall for GitHub](https://help.nightfall.ai/github/getting_started/installation)\n","2026-08-04T17:12:32.731Z","2026-08-04T18:28:53.951Z","5f734ea5-f1fd-4c7f-befb-1d2f02c5ab17",[],[],[],"getting-started-nightfall-documentation-8","https://help.nightfall.ai/salesforce/getting-started","Nightfall's Salesforce integration allows you to scan updates to objects and fields in real-time across sandbox and production organizations in Salesforce. This getting started guide will walk you through installing and upgrading the components of the solution.\n\nSalesforce vertical cloud offerings are not supported as of today.\n\nNightfall's Salesforce integration allows you to scan updates to objects and fields in real-time across sandbox and production organizations in Salesforce. This getting started guide will walk you through installing and upgrading the components of the solution.\n\nNightfall DLP for Salesforce supports the following Salesforce Sales Cloud editions across both production and sandbox instances:\n\n- Enterprise\n\n- Unlimited\n\n- Developer\n\nSalesforce vertical cloud offerings are not supported as of today.\n\nYou can install and authorize Nightfall DLP app package in Salesforce production environments.\n\nYou can view and remediate Salesforce DLP policy violations within the Nightfall dashboard and violations monitoring page.\n","2026-08-04T17:12:48.603Z","2026-08-04T18:28:51.709Z","59c040ff-4067-475b-a74e-50aedcace547",[],[],[],"getting-started-nightfall-documentation-5","https://help.nightfall.ai/microsoft-365/getting_started","Nightfall DLP for Microsoft 365 (M365) offers a cloud-native data leak protection solution that monitors presence of sensitive data across the following M365 services - Exchange Online, Sharepoint Online, OneDrive for Business, and MS Teams.\n\nNightfall DLP for M365 provides a seamless approach to monitor User OneDrives, Teams Channels and Teams Chats. Nightfall DLP scans messages in Team channels / chats and scans files in user's OneDrives. Further, Nightfall also allows notifications to be sent to the Nightfall administrators and M365 users and enables them to take followup steps in alignment with the organization's requirements.\n\nThe following steps need to be completed to enable Nightfall DLP workflows for OneDrive for Business and MS Teams,\n\n1. Setup of directory sync, and\n\n2. Registration of the M365 endpoint with Nightfall\n","2026-08-04T17:12:35.490Z","2026-08-04T18:28:55.582Z","26a738de-4430-4a3c-af7b-38cebf6007db",[],[],[],"getting-started-nightfall-documentation-9","https://help.nightfall.ai/zendesk/getting_started","For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). This page is also available as [Markdown](https://help.nightfall.ai/zendesk/getting_started.md).\n\nThis guide will help you to get started with installing and integrating Nightfall DLP for Zendesk.\n\nBefore you get started with configuring Nightfall DLP for Zendesk, you must install the app.\n\nLast updated 1 year ago\n\nWas this helpful?\n","2026-08-04T17:12:48.741Z","2026-08-04T18:28:51.848Z","245900a6-8dc7-4b5b-8cb5-5c21cc1ede50",[],[],[],"GenAI Protection | Developer APIs | Nightfall Documentation","genai-protection-developer-apis-nightfall-documentation","https://help.nightfall.ai/developer-api/tutorials/genai_protection","# GenAI Protection | Developer APIs\n\nFor the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). This page is also available as [Markdown](https://help.nightfall.ai/developer-api/tutorials/genai_protection.md).\n\nThis section consists of various documents that assist you in scanning various popular SaaS GenAI services and frameworks using Nightfall APIs.\n\nLast updated 2 years ago\n\nWas this helpful?\n","2026-08-04T17:13:03.522Z","2026-08-04T17:13:03.545Z","bc7bba64-1351-4821-bc00-3150d1a1d5b2",[],[],[],"Frequently Asked Questions (FAQs) | Nightfall Documentation","frequently-asked-questions-faqs-nightfall-documentation","https://help.nightfall.ai/faqs","For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). This page is also available as [Markdown](https://help.nightfall.ai/faqs.md).\n\nA list of common queries which users get while using Nightfall and their responses.\n\nLast updated 2 years ago\n\nWas this helpful?\n","2026-08-04T17:12:29.778Z","2026-08-04T18:29:08.542Z","6139e5bc-0323-4124-969b-59a2a45bfdc0",[],[],[],"frequently-asked-questions-faqs-nightfall-documentation-2","https://help.nightfall.ai/nightfall-for-anthropic-claude/frequently-asked-questions-faqs","**How fast does Nightfall see a new Claude message?**\n\nConversations and files are polled every 60 seconds; the activity feed is polled every 30 seconds. `[verify]` Cadence with engineering against PRD §9b.\n\n**What happens if a user deletes content in Claude?**\n\nThe connector best-effort propagates deletes to the Nightfall index. `[verify]` Deletion-propagation semantics with Anthropic. Tracked as PRD §14 open question 5.\n\n**Can I keep finding metadata but drop the raw Claude conversation text?**\n\nYes. Enable redaction-at-ingest mode on the integration. Findings, detector hits, and byte offsets are preserved; the raw content is not stored. See PRD US-18.\n\n**Where can I see Claude admin activity?**\n\nThe **Claude Activity** view in Nightfall. Events also forward to your SIEM destination if you have one configured.\n\n**Can I block a prompt before it reaches Claude?**\n\nNot via the Compliance API. Use the Nightfall endpoint agent for inline block on Claude Desktop, Claude Code, or the Claude browser tab. (Linked above.)\n\n**Will this cover Claude on Bedrock or Vertex AI?**\n\nNo. Those surfaces are not exposed by the Compliance API. Use the Nightfall endpoint agent on the developer's machine, or the AI Agent Security integration if the work is happening inside Claude Code.\n","2026-08-04T17:12:49.653Z","2026-08-04T18:28:52.553Z","3792eed3-74f0-4712-af11-02476265e0b9",[],[],[],"Frequently Asked Questions (FAQs) for End-Users | Nightfall Documentation","frequently-asked-questions-faqs-for-end-users-nightfall-documentation","https://help.nightfall.ai/operationalizing_nightfall_dlp/faqs_end_users","# Frequently Asked Questions (FAQs) for End-Users\n\n## What is Nightfall?[](https://help.nightfall.ai/operationalizing_nightfall_dlp/faqs_end_users#what-is-nightfall)\n\nNightfall is like a security guard for your organization’s digital information. It lives in the cloud and keeps an eye out for any signs of data leaks. Imagine it as a watchful friend who ensures that sensitive information doesn’t accidentally slip out. Nightfall ensures that your organization’s secrets stay safe.\n\nYou can learn more about Nightfall from [this document](https://help.nightfall.ai/nightfall-ai/introduction_to_nightfall/untitled).\n\n## Why am I receiving Notifications from Nightfall?[](https://help.nightfall.ai/operationalizing_nightfall_dlp/faqs_end_users#why-am-i-receiving-notifications-from-nightfall)\n\nHere are some everyday situations where Nightfall steps in to protect your data:\n\nGoogle Docs, Sheets, and Slides:\n\nIf you create a document, spreadsheet, or presentation with sensitive content (such as financial data or personal info), Nightfall alerts your security team which in turn may choose to alert you.\n\nMessaging Apps (Slack, MS Teams): When you send messages containing sensitive information (maybe a credit card number or confidential project details), Nightfall gives your security team a heads-up which in turn may choose to alert you.\n\n**Zendesk Tickets:**\n\nEven in customer support interactions, if you accidentally add sensitive info in comments or descriptions, Nightfall intervenes.\n\n**Code Commit on GitHub:**\n\nWhen you’re working on code and accidentally include sensitive details (like passwords or private keys), Nightfall raises a flag. Your security team might choose to notify you of such an event.\n\nThese are a few examples of how Nightfall helps your organization protect sensitive data. Your security or data governance team may decide to send you additional information about best practices for your situation, invite you to take action, or for you to provide additional context to the situation.\n\n## What's included in Nightfall notifications?[](https://help.nightfall.ai/operationalizing_nightfall_dlp/faqs_end_users#whats-included-in-nightfall-notifications)\n\nYou should expect the following information in a Nightfall notification:\n\nPolicy Information\n\nA custom message from your organization often includes information about the data policy and best practices related to the sensitive data discovered.\n\nEvent Information\n\nDetails about the type of sensitive data including the location and time of the event\n\nCall to action\n\nA list of actions you can take to ensure compliance with your organization's policy or the ability to submit a business justification or report a false positive.\n\n## What should I do now?[](https://help.nightfall.ai/operationalizing_nightfall_dlp/faqs_end_users#what-should-i-do-now)\n\nOnce you identify the potentially sensitive data, you can take appropriate action. The Nightfall alert displays the actions you can take. The category of actions is as follows.\n\n- **Report as False Positive**:- If you are confident that the potentially sensitive data identified by Nightfall is not sensitive, you can choose either the Report False Positive or the Report False Positive with Business Justification actions.\n\n- **Remove Sensitive Data or Access**:- If the Nightfall alert identified sensitive data you must take action immediately. The available actions vary for each platform. Some examples of these actions are:\n\n - For Slack, you can **Redact** the sensitive information or **Delete** the message.\n\n - For GitHub or Zendesk, you can choose to either **Redact** or **Remove** the sensitive data.\n\n - For Google Drive, you can choose to **Remove access to external users**, **Restrict Link**, or **Disable Download**.\n\n - For Notion, you can either **Redact**, **Remove access to external users**, or **Restrict Link**.\n\n**Note**: The available actions depend on the settings configured by your Nightfall administrator. If you are unable to view a specific remedial action, contact your Nightfall administrator.\n\n## Why do I keep receiving these alerts?[](https://help.nightfall.ai/operationalizing_nightfall_dlp/faqs_end_users#why-do-i-keep-receiving-these-alerts)\n\n**New notifications**\n\nYour organization may choose to notify users associated with a potential sensitive data leak or exposure risk. If you think that you have received a notification by error, make sure to report it as a false positive if this option is available to you on the notification or reach out to your data governance and security team.\n\n**Reminder notifications**\n\nWhen the notification you receive contains a set of actions you can take, you will keep receiving reminders until you take action, submit a business justification or report as a false positive..\n\n## What just happened? Why did my content get redacted?[](https://help.nightfall.ai/operationalizing_nightfall_dlp/faqs_end_users#what-just-happened-why-did-my-content-get-redacted)\n\nIf something you sent or created was automatically removed, this means Nightfall detected what your organization considers a piece of sensitive information. Nightfall will not remove or redact any content that your Nightfall Administrator did not explicitly instruct it to detect.\n\n## What can I do if my content is redacted, but shouldn’t have been?[](https://help.nightfall.ai/operationalizing_nightfall_dlp/faqs_end_users#what-can-i-do-if-my-content-is-redacted-but-shouldnt-have-been)\n\nIf you are confident that any data redacted by Nightfall is not sensitive, contact your Nightfall Administrator. If the redacted data is sensitive, you need not take any further action but adhere to more safe sharing practices in the future.\n\n## What are the best practices I should adopt?[](https://help.nightfall.ai/operationalizing_nightfall_dlp/faqs_end_users#what-are-the-best-practices-i-should-adopt)\n\nSome of the best practices Nightfall recommends are:\n\n- Be overly cautious when sharing active credentials only through approved applications or channels. If you wish to share dummy API keys or testing credentials, notify your organization's Nightfall Administrator.\n\n- Thoroughly check if any content that you are about to publish or share contains any sensitive data.\n\n## What is Sensitive Data?[](https://help.nightfall.ai/operationalizing_nightfall_dlp/faqs_end_users#what-is-sensitive-data)\n\nSensitive data includes information that requires special protection due to its potential impact if exposed. Examples include personally identifiable information (PII), payment card information (PCI), and protected health information (PHI). The full list varies based on the organization and the industry in which it operates.\n\n## Why Is Protecting Sensitive Data Crucial?[](https://help.nightfall.ai/operationalizing_nightfall_dlp/faqs_end_users#why-is-protecting-sensitive-data-crucial)\n\nSensitive data leaks or breaches can lead to loss of trust, financial repercussions, and legal consequences. Everyone in the organization must prioritize safeguarding this data.\n","2026-08-04T17:12:54.977Z","2026-08-04T18:29:08.308Z","2fd81132-9cf3-460e-94c7-c2546a841f8a",[],[],[],"FAQs | Nightfall Documentation","faqs-nightfall-documentation","https://help.nightfall.ai/slack/slack-faqs","For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). This page is also available as [Markdown](https://help.nightfall.ai/slack/slack-faqs.md).\n\nPlease find links to our FAQs for Slack in the subpages of this section.\n\nLast updated 2 years ago\n\nWas this helpful?\n","2026-08-04T17:12:32.607Z","2026-08-04T18:28:53.714Z","c51bb375-68e1-4e96-8935-2eea8973c0b8",[],[],[],"faqs-nightfall-documentation-2","https://help.nightfall.ai/confluence/faqs","For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). This page is also available as [Markdown](https://help.nightfall.ai/confluence/faqs.md).\n\nFAQs on Nightfall for Confluence\n\nLast updated 1 year ago\n\nWas this helpful?\n","2026-08-04T17:12:34.692Z","2026-08-04T18:28:55.114Z","c4bf5c16-3078-4356-a425-1992bbaefada",[],[],[],"faqs-nightfall-documentation-3","https://help.nightfall.ai/salesforce/faqs","#### How does Nightfall DLP for Salesforce leverage Salesforce Platform Events?[](https://help.nightfall.ai/salesforce/faqs#how-does-nightfall-dlp-for-salesforce-leverage-salesforce-platform-events)\n\nNightfall DLP for Salesforce depends on the [Platform Events](https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_intro_emp.htm) messaging platform of a Salesforce org that Salesforce promotes as best practise to receive notifications for Salesforce events. Further, [Platform Events limits](https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_limits_default.htm) are shared across all workflows that leverage Platform Events and, per Salesforce, are replinished on a 24 hour rolling basis.\n\nEvery time an update happens on one of the objects monitoried by Nightfall DLP for Salesfoce, Nightfall's Salesforce package triggers an event that is queued in the Salesforce orgs Platform Events messaging queue. Subsequently Nightfall DLP Platform retrieves the event and the payload from the Platform Events queue and processes the update.\n\n#### How Salesforce Platform Events limits affect Nightfall DLP for Salesforce processing?[](https://help.nightfall.ai/salesforce/faqs#how-salesforce-platform-events-limits-affect-nightfall-dlp-for-salesforce-processing)\n\nNightfall understands the criticality of Platform Events for Salesforce workflows and has defined a High Threshold and a Low Threshold for Platform Events usage on the customer's Salesforce org. If the Platform Events usage on the customer's Salesforce org breaches the High Threshold then Nightfall DLP for Salesforce will pause scan. Nightfall DLP for Salesforce will resume scan only when the Platform Events usage on the customer's Salesforce org goes below the Low Threshold. This way Nightfall DLP for Salesforce behaves as a model enterprise application and ensures that critical Salesforce workflows (like order processing) are prioritised over sensitive data scan.\n\nPlease reach out to your customer success manager for further details.\n\n#### I selected Delete and Redact in my Policy. Is that a problem?[](https://help.nightfall.ai/salesforce/faqs#i-selected-delete-and-redact-in-my-policy.-is-that-a-problem)\n\nIf you opted for both Redact and Delete actions in a policy for a set of objects and fields, Delete takes precedence over redact.\n\nAll potential sensitive tokens are automatically deleted from the configured objects and fields.\n\n#### On a single object, I want to configure a policy to automatically delete all credit card data, but auto-redact SSN.[](https://help.nightfall.ai/salesforce/faqs#on-a-single-object-i-want-to-configure-a-policy-to-automatically-delete-all-credit-card-data-but-aut)\n\nYou can create two policies on the object;\n\n- one policy with a detection rule for the SSN detector, with redaction as the automated action.\n\n- Another policy with a detection rule for credit card detector with delete as the automation action.\n\n#### Why does Nightfall only scan emails that are sent, replied, forwarded but not the draft emails?[](https://help.nightfall.ai/salesforce/faqs#why-does-nightfall-only-scan-emails-that-are-sent-replied-forwarded-but-not-the-draft-emails)\n\nSalesforce may save emails in draft stage multiple times either because of the user action or automatically. Every save triggers a Salesforce event which causes Nightfall to scane the contents of the email draft if there is a policy to scan emails objects. This can lead to a situation where multiple violations are reported for the same sensitive data if the email is saved multiple times in the draft stage.\n\nSo, Nightfall has disabled scanning of emails as long as they are in draft stage. However, emails will continue to be be scanned when other operations happen, for examples emails are sent, replied and forwarded. The user can reach out to Nightfall if they wish Nightfall to scan the drafts too, but it should be noted that as described above, this can lead to the same findings getting flagged across violations whenever the draft is saved.\n\n#### Nightfall doesn’t remediate sensitive information from Email Message object. How do I solve this?[](https://help.nightfall.ai/salesforce/faqs#nightfall-doesnt-remediate-sensitive-information-from-email-message-object.-how-do-i-solve-this)\n\nEmail message is an immutable object in Salesforce. Therefore, Nightfall cannot modify the object record. You can delete the email from within Salesforce, once you receive a notification.\n\n**I received a violation notification. However, the information was removed by the user in Salesforce. How will auto remediation respond?**\n\nIf the object does not contain sensitive information at the time of remediation, Nightfall will not remediate any data. Nightfall will re-scan the violated object and fields before performing any remediation.\n\n#### I performed manual remediation on an object record after the object was deleted from Salesforce. How do I know if it was successful?[](https://help.nightfall.ai/salesforce/faqs#i-performed-manual-remediation-on-an-object-record-after-the-object-was-deleted-from-salesforce.-how)\n\nNightfall detects that the object record does not exist anymore, and will stop remediation. A notification is sent to you.\n\n#### How do I know if remediation action was successful?[](https://help.nightfall.ai/salesforce/faqs#how-do-i-know-if-remediation-action-was-successful)\n\nNightfall sends notifications for remediation action it performs.\n\n#### A new version of the attachment was uploaded, can I remediate the previous version which had sensitive information?[](https://help.nightfall.ai/salesforce/faqs#a-new-version-of-the-attachment-was-uploaded-can-i-remediate-the-previous-version-which-had-sensitiv)\n\nNo, Salesforce does not provide the option to delete specific versions of a file. Further, Salesforce only allows deletion of all the versions of an attachment. You can manually delete the attachment in Salesforce.\n\nIf the version was updated, and the object clears the scan, Nightfall will not delete the attachment and issues a notification with this information.\n\n#### If I have Einstein Activity Capture configured which synchronizes my mail and I see them in Salesforce. Can Nightfall detect sensitive information in these objects too?[](https://help.nightfall.ai/salesforce/faqs#if-i-have-einstein-activity-capture-configured-which-synchronizes-my-mail-and-i-see-them-in-salesfor)\n\nNo. Nightfall does not have the capability to detect sensitive information in any entity synced by Einstein Activity Capture.\n\n#### What does the Nightfall DLP webhook notification for Salesforce look like?[](https://help.nightfall.ai/salesforce/faqs#what-does-the-nightfall-dlp-webhook-notification-for-salesforce-look-like)\n\nPlease see some example webhook responses below:\n\n- Violations\n\n- Manual Remediation\n\n- Automated Remediation\n\n#### Violation[](https://help.nightfall.ai/salesforce/faqs#violation)\n\n#### Manual Remediation[](https://help.nightfall.ai/salesforce/faqs#manual-remediation)\n\n#### Automated Remediation[](https://help.nightfall.ai/salesforce/faqs#automated-remediation)\n","2026-08-04T17:12:48.457Z","2026-08-04T18:28:51.976Z","22fc0351-ad62-42c1-884d-bf910594032d",[],[],[],"FAQs | Developer APIs | Nightfall Documentation","faqs-developer-apis-nightfall-documentation","https://help.nightfall.ai/developer-api/faqs","For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). This page is also available as [Markdown](https://help.nightfall.ai/developer-api/faqs.md).\n\nLast updated 2 years ago\n\nWas this helpful?\n","2026-08-04T17:13:02.077Z","2026-08-04T17:13:02.178Z","e8bb6a72-bf06-4088-bcd0-14bbab72fd13",[],[],[],"Exfiltration Prevention APIs | Developer APIs | Nightfall Documentation","exfiltration-prevention-apis-developer-apis-nightfall-documentation","https://help.nightfall.ai/developer-api/nightfall_apis/exfiltration-prevention-apis","# Exfiltration Prevention APIs | Developer APIs\n\nevent\\_idthe unique identifier of the exfiltration event to filter onintegration\\_namethe name of the integration to filter onstatethe state of the event to filter on (active, pending, resolved, expired)event\\_typethe type of exfiltration event to filter onactor\\_namethe name of the actor who performed the action to filter onactor\\_emailthe email of the actor who performed the action to filter onuser\\_namethe username of the user to filter on (backward compatibility)user\\_emailthe email of the user to filter on (backward compatibility)notesthe comment or notes associated with the event to filter onrisk\\_labelthe risk label to filter onrisk\\_sourcethe risk determination source to filter onpolicy\\_idthe unique identifier of the policy to filter onpolicy\\_namethe name of the policy to filter onresource\\_idthe identifier of the resource to filter onresource\\_namethe name of the resource to filter onresource\\_owner\\_namethe name of the resource owner to filter onresource\\_owner\\_emailthe email of the resource owner to filter onresource\\_content\\_typethe content type of the resource to filter onendpoint.device\\_idthe device identifier for endpoint events to filter onendpoint.machine\\_namethe machine name for endpoint events to filter onendpoint.ai\\_agent.client\\_typethe AI agent client (e.g. claude\\_code, cursor, cowork) to filter onendpoint.ai\\_agent.client\\_versionthe AI agent client version to filter onendpoint.ai\\_agent.trigger\\_pointthe AI agent event phase (PROMPT, MODEL\\_RESPONSE, TOOL\\_REQUEST, TOOL\\_RESPONSE, SHELL, OTEL\\_TELEMETRY) to filter onendpoint.ai\\_agent.session\\_idthe AI agent session identifier to filter onendpoint.ai\\_agent.tool\\_namethe tool invoked by the AI agent to filter onendpoint.ai\\_agent.server\\_namethe MCP server that served the tool to filter onendpoint.ai\\_agent.decisionthe permission decision (allow, deny, ask) to filter onendpoint.ai\\_agent.tool\\_use\\_idthe unique identifier for a specific tool invocation to filter onendpoint.ai\\_agent.modelthe model used for the request (OTel only, e.g. claude-opus-4-7) to filter onendpoint.ai\\_agent.error\\_messagethe error message from a failed AI agent call to filter ongdrive.permissionthe permission setting for Google Drive files to filter ongdrive.shared\\_internal\\_emailthe internal emails with which the file is shared to filter ongdrive.shared\\_external\\_emailthe external emails with which the file is shared to filter ongdrive.drivethe Google Drive name to filter ongdrive.file\\_ownerthe owner of the Google Drive file to filter ongdrive.label\\_namethe label name applied to Google Drive files to filter onsalesforce.report.scopethe scope of the Salesforce report to filter onsalesforce.report.event\\_sourcethe event source of the Salesforce report to filter onsalesforce.report.source\\_ipthe source IP address of the Salesforce report to filter onsalesforce.report.session\\_levelthe session level of the Salesforce report to filter onsalesforce.report.operationthe operation type of the Salesforce report to filter onsalesforce.report.descriptionthe description of the Salesforce report to filter onsalesforce.file.source\\_ipthe source IP address for Salesforce file events to filter onsalesforce.file.session\\_levelthe session level for Salesforce file events to filter onlast\\_actioned\\_bythe entity that performed the last action on the violation, can be one of NIGHTFALL, ADMIN or END\\_USER\n","2026-08-04T17:13:03.872Z","2026-08-04T17:13:03.897Z","3da97101-d9e2-44fb-8c82-255148ea8c2f",[],[],[],"Event Status | Nightfall Documentation","event-status-nightfall-documentation","https://help.nightfall.ai/dashboard/sdp_events/status","The Status of an Event implies the current state of the Event. For instance, an Event whose status displays **Notified**, implies that the end-user whose actions caused the violation has been notified about their actions. They must now take appropriate actions.\n\nWhen a new Event is created in Nightfall, the status is **Active**. The status of the violation gets modified by one of the following methods.\n\n- **Automatically**: If you have configured either Admin alerting, end-user alerting, or have allowed end-user remediation, the status of the violation changes automatically.\n\n- **Manually**: If you apply an action on a Violation manually either from the Violations page or from any other platform, the status of the violation changes accordingly.\n\n## Status List[](https://help.nightfall.ai/dashboard/sdp_events/status#status-list)\n\nThe various Status available in Nightfall are listed as follows.\n\n### Active[](https://help.nightfall.ai/dashboard/sdp_events/status#active)\n\nThis status implies that the Event is newly created and no action (not even notification about the Event) is implemented.\n\n### Acknowledged[](https://help.nightfall.ai/dashboard/sdp_events/status#acknowledged)\n\nThis status implies that the Nightfall admin has viewed acknowledged the Event. A further action needs to be taken in future.\n\n### Notified[](https://help.nightfall.ai/dashboard/sdp_events/status#notified)\n\nThis status implies that the end-users have been notified about their actions that caused the Event.\n\n### Redacted[](https://help.nightfall.ai/dashboard/sdp_events/status#redacted)\n\nThis status implies that the sensitive data that triggered the Event, is redacted.\n\n### Quarantined[](https://help.nightfall.ai/dashboard/sdp_events/status#quarantined)\n\nThis status implies that the entity (file, email, and so on) that contains the sensitive data is quarantined from rest of the data.\n\n### Accepted[](https://help.nightfall.ai/dashboard/sdp_events/status#accepted)\n\n### Rejected[](https://help.nightfall.ai/dashboard/sdp_events/status#rejected)\n\n### Scheduled[](https://help.nightfall.ai/dashboard/sdp_events/status#scheduled)\n\n### Removed Internal Users[](https://help.nightfall.ai/dashboard/sdp_events/status#removed-internal-users)\n\nThis status implies that the access to the file or entity that contains sensitive data is no longer accessible to the internal users of the organization.\n\n### Removed External Users[](https://help.nightfall.ai/dashboard/sdp_events/status#removed-external-users)\n\nThis status implies that the access to the file or entity that contains sensitive data is no longer accessible to the external users who are not part of your organization.\n\n### Link Settings Changed[](https://help.nightfall.ai/dashboard/sdp_events/status#link-settings-changed)\n\nThis status implies that the file's (that contains sensitive data) access permissions have been modified.\n\n### Deleted[](https://help.nightfall.ai/dashboard/sdp_events/status#deleted)\n\nThis status implies that the file or the entity that contained the sensitive data is deleted.\n\n### Ignored[](https://help.nightfall.ai/dashboard/sdp_events/status#ignored)\n\nThis status implies that the Nightfall admin has ignored the Event either because its false positive or because they wish to look into it in the later.\n\n### Disabled Download[](https://help.nightfall.ai/dashboard/sdp_events/status#disabled-download)\n\nThis status implies that the file that contains sensitive data has been disabled from downloading. This prevents any user from downloading the file.\n\n### Marked as Private[](https://help.nightfall.ai/dashboard/sdp_events/status#marked-as-private)\n\nThis status implies that the file or the entity containing sensitive data is marked as private.\n\n### Attachment Deleted[](https://help.nightfall.ai/dashboard/sdp_events/status#attachment-deleted)\n\nThis status implies that the attachment that contains sensitive data has been deleted.\n\n### Sent to JIRA[](https://help.nightfall.ai/dashboard/sdp_events/status#sent-to-jira)\n\nThis status implies that a new JIRA ticket has been created to represent this Event.\n\n### Encrypted[](https://help.nightfall.ai/dashboard/sdp_events/status#encrypted)\n\nThis status implies that the sensitive data has been encrypted.\n\n### Blocked[](https://help.nightfall.ai/dashboard/sdp_events/status#blocked)\n\nThis status implies that the entity containing the sensitive data has been encrypted.\n\n### Input Requested[](https://help.nightfall.ai/dashboard/sdp_events/status#input-requested)\n\nThis status implies that a notification has been sent to the end-user requesting justification for their actions that caused the Event.\n\n### Input Received[](https://help.nightfall.ai/dashboard/sdp_events/status#input-received)\n\nThis status implies that the end-user has provided justification of their action(s) that triggered the Event.\n\n### Restricted to Owner[](https://help.nightfall.ai/dashboard/sdp_events/status#restricted-to-owner)\n\nThis status implies that the access to the file containing sensitive data is now restricted only to the owner of the file.\n\n### Deleted File[](https://help.nightfall.ai/dashboard/sdp_events/status#deleted-file)\n\nThis status implies that the file containing sensitive data is deleted.\n\n### Moved to Recycle Bin[](https://help.nightfall.ai/dashboard/sdp_events/status#moved-to-recycle-bin)\n\nThis implies that the entity containing sensitive data is moved to recycle bin.\n\n### Quarantined Email[](https://help.nightfall.ai/dashboard/sdp_events/status#quarantined-email)\n\nThis status implies that the email has been quarantined. A Nightfall admin must visit the quarantine settings in Gmail and take an action accordingly. This status is applicable only to Gmail.\n\n### Released Email[](https://help.nightfall.ai/dashboard/sdp_events/status#released-email)\n\nThis status implies that the email was sent to the recipient after scanning. There were no actions taken on the email. This status is applicable only to Gmail.\n\n### Pending[](https://help.nightfall.ai/dashboard/sdp_events/status#pending)\n\nThese are the violations which have been notified to the end-users. However no action has been taken by the end-users or any other user.\n\n### Resolved[](https://help.nightfall.ai/dashboard/sdp_events/status#resolved)\n\nThis status implies that the sensitive data issue in the Event has been addressed and thus the Event is resolved.\n\n### Expired[](https://help.nightfall.ai/dashboard/sdp_events/status#expired)\n\nThis status implies that the Event has expired since no action has been taken even after the stipulated time period.\n","2026-08-04T17:14:15.960Z","2026-08-04T18:30:37.181Z","108223b0-4455-438c-9320-bfc04c6ab4af",[],[],[],"Evaluating Detection | Nightfall Documentation","evaluating-detection-nightfall-documentation","https://help.nightfall.ai/detection_platform/evaluate_nightfall_detection","In order to evaluate the success of your cloud DLP detection, you must first have clarity around your organization’s goals. This will be highly dependent on your organization’s unique circumstances and needs.\n\nHere are some guiding questions:\n\n- What sensitive data would you like to detect and which are the highest priorities for each SaaS application?\n\n- What level of risk are you comfortable with? Would you like to alert on only the most risky findings or have visibility into even low-risk data types that may not warrant action?\n\n- How much operational load are you willing to take on? The more granular your approach, the less human discretion will be required in the filtering and remediation steps.\n\n- What are the requirements of any compliance regimes you are accountable to?\n\n- What user strategy would you like to implement?\n\n - Some potential answers:\n\n - Minimal impact on user experience, only alerting and monitoring to security staff and notifications to end users to guide towards remediation?\n\n - Educating and empowering users about DLP best practices?\n\n - Enforcing DLP through strict controls and automation?\n\n### Testing Detection Rules[](https://help.nightfall.ai/detection_platform/evaluate_nightfall_detection#testing-detection-rules)\n\nOnce you have a sense of your goals, we recommend that you optimize your detection during a phased, iterative implementation - start small, and broaden gradually. Typically, the biggest pitfall customers want to avoid during implementation is to get flooded by too many low-priority alerts that become unmanageable - which is typically caused by taking too broad of an approach to detection. By taking the time to optimize your detection gradually during the first few weeks, your team will be set up for ongoing success.\n\nFor this reason, we have created our Detection Wizard, which is a resource that will recommend the exact configuration to suit your use cases. You can shortcut a lot of legwork in choosing and fine-tuning rules by immediately identifying the recommended and validated configuration that matches your use case.\n\nThere is generally little reason to deviate from the Wizard’s recommendations at the outset, but your use case may warrant fine-tuning and broadening your detection logic over time:\n\nWe recommend that you select just a few detectors to start out with as recommended by the Wizard, in order to optimize detection of the most critical and high-risk information types.\n\n- Once a few detectors and initial detection rules are in place, test some sample data and monitor the results. We suggest you evaluate metrics such as false positive and false negative rates, and assess whether the volume of alerts/results is manageable by your team. You may adjust parameters such as Minimum Confidence and Minimum Number of Findings to optimize the level of alerts through your testing process.\n\n- Then, continue to iterate and modify your detection by adding and optimizing a few more detectors as required. Focus on starting with tighter detection rules (higher confidence levels), and slowly relax or broaden the rules over time.\n\n### Sample Data[](https://help.nightfall.ai/detection_platform/evaluate_nightfall_detection#sample-data)\n\nNightfall offers a library of [Sample Data](https://help.nightfall.ai/nightfall-ai/nightfall-detection-and-policy-templates/nightfall-sample-data-sets) that we recommend for evaluating DLP technologies.\n\n### Evaluating Detection During Tests vs. in the Wild[](https://help.nightfall.ai/detection_platform/evaluate_nightfall_detection#evaluating-detection-during-tests-vs.-in-the-wild)\n\nIt’s important to understand that the rate of true positive data “in the wild” tends to be significantly lower than true positive data in a test environment. That’s because, in a test environment, many occurrences of sensitive information will be intentionally planted.\n\nAs a result, test environments are typically most useful for optimizing sensitivity, or the true positive rate - detection is optimized toward identifying sensitive information as sensitive. While this helps ensure that occurrences of sensitive information are, in fact, correctly flagged, it also means detection is somewhat skewed toward flagging information as sensitive, thus increasing the potential for false positives (see [the tradeoff between sensitivity and specificity](https://help.nightfall.ai/nightfall-ai/detection/how-detection-works#understanding-accuracy)).\n\nWhat this means for you is that if you fine-tune a detection rule in a test environment, you may over-index towards sensitivity rather than specificity, which can result in a higher degree of false positives in the wild. As a result, we highly recommend evaluating detection rules in a production environment rather than a test environment, when possible.\n","2026-08-04T17:12:51.814Z","2026-08-04T18:29:06.349Z","6ccdd9cd-6618-430f-a32b-b8fe664f23af",[],[],[],"Errors | Developer APIs | Nightfall Documentation","errors-developer-apis-nightfall-documentation","https://help.nightfall.ai/developer-api/key-concepts/errors","While using Nightfall's Scan API, you may encounter some of the common errors outlined below. Try following the provided troubleshooting steps.\n\nIf problems persist, please [contact Nightfall Support](mailto:support@nightfall.ai) for further assistance.\n\n### HTTP Error Codes[](https://help.nightfall.ai/developer-api/key-concepts/errors#http-error-codes)\n\nThe following error codes are returned as part of a standard HTTP response.\n","2026-08-04T17:13:02.299Z","2026-08-04T17:13:02.324Z","6ea2401c-a989-4ba3-808a-1c079a153c35",[],[],[],"Entities and Terms to Know | Developer APIs | Nightfall Documentation","entities-and-terms-to-know-developer-apis-nightfall-documentation","https://help.nightfall.ai/developer-api/key-concepts/key_terms","# Entities and Terms to Know | Developer APIs\n\nThis section describes the terms you will need to know when using the API.\n\n## Detectors[](https://help.nightfall.ai/developer-api/key-concepts/key_terms#detectors)\n\nDetectors provide the logic to find potentially sensitive pieces of data.\n\nWhen this logic detects such data, the Detector is considered \"triggered.\"\n\nNightfall's has numerous pre-built Detectors that are trained via machine learning. Detectors may also be defined with regular expressions or dictionaries. Their accuracy may be further refined with exclusion rules and context rules. Whether a Detector is triggered may be controlled by a minimum confidence threshold per Detector and minimum number of findings per Detector as set on a Detection Rule.\n\nThe built-in set of Detectors cover a number of different categories of data, including:\n\n- Standard PII (e.g. social security number, driver's license number, ID card image)\n\n- PCI (Credit Card Number, credit card image)\n\n- Healthcare (e.g. PHI, US Medicare Beneficiary Number)\n\n- Finance - Banking (e.g. SWIFT code, IBAN code, US bank routing number)\n\n- Network (e.g. an IP Address)\n\nThe full set is enumerated in the [Detector Glossary](https://help.nightfall.ai/nightfall-ai/detection-engine/choosing-detectors/nightfall-detector-glossary).\n\n### Custom Detectors[](https://help.nightfall.ai/developer-api/key-concepts/key_terms#custom-detectors)\n\nNightfall also supports [RE2 regexes](https://github.com/google/re2/wiki/Syntax) and word lists for any custom detectors that you may want to implement.\n\nOver time, we've aggregated the following [regex library](https://help.nightfall.ai/nightfall-ai/detection-engine/regex-library#regex-library), which you're welcome to select from to save you some time. Please note that a regular expression is an established yet limited method that searches for pre-defined patterns, so your mileage may vary.\n\nYou can test regular expressions [here](https://regex101.com/).\n\nYou can input custom detectors in two ways: directly in the Nightfall [Dashboard](https://app.nightfall.ai/) by navigating to **Detectors** → **New Detector** → **Regular expression**, or [define them inline](https://docs.nightfall.ai/docs/creating-an-inline-detection-rule)[.](https://help.nightfall.ai/developer-api/key-concepts/scanning_features/inline_detection_rules)\n\n### Exclusion Rules[](https://help.nightfall.ai/developer-api/key-concepts/key_terms#exclusion-rules)\n\nAn exclusion rule is a regular expression or word list that will be used once a Detector is triggered by its primary expression or word list to eliminate false positives.\n\nFor instance, you may have a Detector designed to detect phone numbers. However, you may have a particular set of phone numbers that you use for testing purposes that are known not to be valid (e.g. they start with the prefix 555) and this should be ignored. Adding an exclusion rule would allow you to prevent those matches from being returned by the API.\n\nSee: [Using Exclusion Rules](https://help.nightfall.ai/developer-api/key-concepts/key_terms#exclusion-rules)\n\n### Context Rules[](https://help.nightfall.ai/developer-api/key-concepts/key_terms#context-rules)\n\nContext Rules are additional matching expressions for a Detector that may be used to adjust the confidence score of a match.\n\nYou may provide a regular expression and the number of leading or trailing characters within which a match of that expression must occur in order to adjust the confidence level to a particular level.\n\nFor instance, if you found a sequence that appeared to be a social security number based on its length or formatting, you might boost the confidence score if it was preceded by the text like “SSN” or “Social Security Number.”\n\n### Returning Surrounding Context[](https://help.nightfall.ai/developer-api/key-concepts/key_terms#returning-surrounding-context)\n\nYou may request that a sequence of bytes of a given length be provided from before and after the text that triggers a Detection Rule.\n\nThis information can help you better understand whether or not something is an actual violation by observing the circumstances within which the detected text was found.\n\nYou are limited to a maximum of 40 bytes of this context text preceding and trailing the match for a total of 80 bytes overall.\n\nSee: [Using Context](https://help.nightfall.ai/developer-api/key-concepts/scanning_features/context_rules)\n\n## Detection Rules[](https://help.nightfall.ai/developer-api/key-concepts/key_terms#detection-rules)\n\nDetection Rules are aggregations of Detectors that are assigned a minimum confidence level. The identifiers of Detection Rules are used as a parameter to the API.\n\nYou may create Detection Rules as described in the section Creating Detection Rules and use their identifier as part of API calls to scan content.\n\nAlternatively you may specify Detection Rules [programmatically](https://help.nightfall.ai/developer-api/key-concepts/scanning_features/inline_detection_rules) in each API call, as described in the scan method documentation below.\n\nA Detection Rule is composed of a list of Detectors with which you wish to scan each request payload, where any or all Detectors may be satisfied in order to trigger the rule. You can add up to 50 total Detectors with a limit of 30 regular expression type custom detectors.\n\nAdditionally, each Detector in the Detection Rule is assigned a “minimum confidence” level (see [below](https://docs.nightfall.ai/docs/entities-and-terms-to-know#confidence-levels) and a minimum number of findings to determine if the Detection Rule should be considered triggered.\n\n### Confidence Levels[](https://help.nightfall.ai/developer-api/key-concepts/key_terms#confidence-levels)\n\nDetection results will be returned with one of the following confidence values.\n\nIn practice, the API will only return detections assigned a POSSIBLE or higher confidence level.\n\n- VERY\\_LIKELY (recommended)\n\n- LIKELY\n\n- POSSIBLE\n\n- UNLIKELY\n\n- VERY\\_UNLIKELY\n\nLearn more about what different confidence levels mean and how to choose the right minimum confidence level for your detection rule [**here**](https://help.nightfall.ai/nightfall-ai/detection-engine/detection-engine-faqs/what-do-different-confidence-levels-mean).\n\n## Policies[](https://help.nightfall.ai/developer-api/key-concepts/key_terms#policies)\n\nPolicies allow you to create templates for the most common workflows by unifying a set of Detection Rules with the actions to be taken when those rules are triggered, including:\n\n- automated actions such as redaction of findings\n\n- alerting through webhooks\n\nOnce defined, a Policy may be used in requests to the Nightfall API, such as calls to scan file uploads, though automated redactions are not available for uploaded files at this time.\n","2026-08-04T17:12:59.401Z","2026-08-04T17:12:59.435Z","79237d16-5abb-481b-9327-b1043b6ae4e7",[],[],[],"Endpoint | Nightfall AI Knowledge Base","endpoint-nightfall-ai-knowledge-base","https://kb.nightfall.ai/collections/8780305235-endpoint","Nightfall macOS Agent: How to Add the Nightfall Chrome ExtensionSettings to an Existing Non-Nightfall Profile\n\n›\n","2026-08-03T17:22:49.920Z","2026-08-04T19:49:19.931Z","5f1ffde2-f84d-436c-9d4f-1c8ec0a05ef4",[],[],[],"Encryption Events Page | Data Encryption | Nightfall Documentation","encryption-events-page-data-encryption-nightfall-documentation","https://help.nightfall.ai/data-encryption/gmail/encryption-events-page","# Encryption Events Page | Data Encryption\n\nThe Encryption events page displays all the encryption events registered by Gmail. An event is triggered when an encryption policy is violated. To learn more about configuring encryption policies, refer to the [Creating Policies for Encryption](https://help.nightfall.ai/data-encryption/gmail/creating-policies-for-encryption) document.\n\n**Important**\n\nAn encryption event is generated only when both of the following conditions are met.\n\n- Nightfall admin creates one or more encryption policies.\n\n- An end-user (who matches the scope for at least one of the policies) sends an email with encryption enabled.\n\nTo navigate to the encryption events page in Nightfall, click **Data Encryption** from the left menu.\n\nOnce you land on the Encryption page, Nightfall displays the encryption events for the last 7 days. You can view that the date filter also displays **Last 7 Days**.\n\nTo view the historic encryption events, click the date filter, set the required time period and click **Apply**.\n\n## Events Columns[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#events-columns)\n\nThe encryption events page consists of the following columns.\n\n## Searching Events[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#searching-events)\n\nThe Events encryption page provides a search bar. You can use the search operators to search a specific event. Nightfall provides multiple operators to search. When you click the search bar, five operators are displayed. You can click the **View all operators** button to view all the available search operators.\n\nFor example, you can use the **user\\_email** search operator to search for events that were generated as a result of emails sent by a specific sender. In the following image the **user\\_email** operator is used to search for events generated by a user whose mail ID is ****.\n\nThe complete list of search operators provided by Nightfall are as follows.\n\n### General Operators[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#general-operators)\n\n#### Integration\\_name[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#integration_name)\n\nThis operator allows you to search events that belong to a specific integration. For example Gmail.\n\n#### User\\_name[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#user_name)\n\nThis operator allows you to search events based on the user name of the sender.\n\n#### state[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#state)\n\nThis operator allows you to search events based on their status.\n\n#### user\\_email[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#user_email)\n\nThis operator allows you to search events that were generated as a result of emails sent from a specific email ID.\n\n### Gmail Operators[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#gmail-operators)\n\n#### gmail.bcc[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#gmail.bcc)\n\nThis operator allows you to search events that were generated as a result of emails sent by including a specific mail ID in the BCC field.\n\n#### gmail.from[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#gmail.from)\n\nThis operator allows you to search events that were generated as a result of emails sent from a specific email ID.\n\n#### gmail.to[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#gmail.to)\n\nThis operator allows you to search events that were generated as a result of emails sent to a specific email ID.\n\n#### gmail.cc[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#gmail.cc)\n\nThis operator allows you to search events that were generated as a result of emails sent by including a specific mail ID in the CC field.\n\n#### gmail.subject[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#gmail.subject)\n\nThis operator allows you to search events that were generated as a result of emails sent by including a specific subject in the Subject field of the email.\n\n#### gmail.user\\_name[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#gmail.user_name)\n\nThis operator allows you to search events based on the gmail user name of the sender.\n\n## Actions[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#actions)\n\nThe actions menu allows you to take appropriate actions on the events. When you initiate an action on an event, the status of the event changes accordingly. For instance, if you apply the encrypt action, the email that triggered the event is encrypted and the status of the event changes to **Encrypted**.\n\nYou can apply an action from the ellipsis menu on the Events page\n\nAlternatively, you can also apply an action from the [Event Detail View](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#event-detail-view) page.\n\nThe actions that you can perform on an encryption Event are as follows.\n\n### Set Expiration[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#set-expiration)\n\nThis action allows you to set an expiration date for the email Recipients cannot view the email after the set expiration period. If an expiration period is already set by the end-user or through automated actions, you can still override the expiration period and set a new expiration period.\n\n### Disable Forward[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#disable-forward)\n\nThis action disables the recipient's ability to forward emails.\n\n### Persistent Protection[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#persistent-protection)\n\nThis action prevents end-users from downloading any attachments or copying the contents of the attachments.\n\n### Resolve[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#resolve)\n\nThis action resolves the Event. You must apply this action when a suitable remediation action has been implemented.\n\n## Event Detail View[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#event-detail-view)\n\nThe Event detail view page displays various details of a specific event. You must click the required event to open the detail view window. The Event detail view displays the following details.\n\n## Encryption Event History[](https://help.nightfall.ai/data-encryption/gmail/encryption-events-page#encryption-event-history)\n\nThe event history section is a log book for the Events. It displays the series of actions that were taken. By default, the first log message recorded is the Event creation and the second log message displays that the email was encrypted by the sender.\n\nOnce the recipient decrypts the Email and view it, a new log message is displayed as follows.\n\nAs you perform various actions on the Email or the Event, the log message is recorded for each action as follows.\n\nAt the end of the event section, Nightfall provides a text box. You can add comments in the text box and save them for future use. You can add a maximum of 300 characters in the text box.\n","2026-08-04T18:30:36.998Z","2026-08-04T18:30:37.057Z","a1517f7f-0d15-4829-9ac1-e99cdf10b65e",[],[],[],"Enable Google Drive Labels | Nightfall Documentation","enable-google-drive-labels-nightfall-documentation","https://help.nightfall.ai/google-drive/getting_started/labels","Labels in Google Drive support various business operations by adding additional metadata to files. Nightfall leverages Google Drive labels to identify sensitive data in Google Drive files and apply automated actions based on labels. To learn more about Google Drive labels, refer to this [Google document](https://support.google.com/a/answer/9292382?hl=en\\&ref_topic=13128179\\&fl=1\\&sjid=13080326729164278818-NC).\n\nTo enable Google Drive labels, you must perform the following prerequisite actions.\n\n[Adding Scope of Google Drive Labels API](https://help.nightfall.ai/google-drive/getting_started/labels#adding-scope-of-google-drive-labels-api)\n\n[Enabling Google Drive Labels API](https://help.nightfall.ai/google-drive/getting_started/labels#enabling-google-drive-labels-api)\n\n## Adding Scope of Google Drive Labels API[](https://help.nightfall.ai/google-drive/getting_started/labels#adding-scope-of-google-drive-labels-api)\n\nTo use Google Drive labels, Nightfall admins must perform the following configurations in your Google Workspace account. You must have the client ID of your Google Workspace.\n\n1. Log in to Google Workspace as an admin.\n\n2. Click **Add a filter**.\n\n3. Select **Client ID**.\n\n4. Enter the client ID and click **Apply**.\n\nYou can use the Client ID stored during the installation of Nightfall for Google Drive integration. The details can be found in this [Nightfall documentation](https://help.nightfall.ai/google-drive/getting_started/installation) (step 4).\n\nThe matching account is displayed.\n\n1. Hover your mouse to the right and click **Edit**.\n\n2. In the **OAuth scopes** field, enter the following scope and click **Authorize**.\n\n### Enabling Google Drive Labels API[](https://help.nightfall.ai/google-drive/getting_started/labels#enabling-google-drive-labels-api)\n\nOnce the scope is added, Nightfall admins must enable the Google Drive Label API. Nightfall recommends you to read this [Google documentation](https://developers.google.com/workspace/guides/enable-apis) on enabling APIs before proceeding with this section.\n\n1. Navigate to the Google Drive Labels API from the GCP console that can be found [here](https://console.cloud.google.com/apis/library/drivelabels.googleapis.com).\n\n2. Click the **Select a Project** menu.\n\nThe list of Google projects is displayed.\n\n1. Select a Project that has the Service Account, used to install the Nightfall Google Drive integration\n\n2. Click **Enable**.\n\n**Important**\n\nBefore using Google Drive Labels in Google Drive policies, ensure that you have created the appropriate Google Drive Labels. To learn more about creating Google Drive labels, refer this [Google Document](https://support.google.com/a/answer/13127870?hl=en).\n","2026-08-04T17:14:18.602Z","2026-08-04T18:41:20.231Z","d47c8a09-e3e4-4348-a2ff-28030b04eaf3",[],[],[],"Does Nightfall scan unstructured data? | Nightfall Documentation","does-nightfall-scan-unstructured-data-nightfall-documentation","https://help.nightfall.ai/faqs/unstructured_data_scan","# Does Nightfall scan unstructured data?\n\nYes, Nightfall scans unstructured data and parses text from 100+ file types. For example, this could be data like customer chat logs, JSON objects, application logs, spreadsheets, PDFs, images, screenshots, etc. Read more about the risks imposed by unstructured data on our blog [here](https://nightfall.ai/resources/unstructured-data-risk-opportunity/).\n","2026-08-04T17:12:57.357Z","2026-08-04T17:12:57.379Z","cc9f56da-9c92-46d0-b8a9-08d92684a6f6",[],[],[],"Does Nightfall require data to be already tagged? | Nightfall Documentation","does-nightfall-require-data-to-be-already-tagged-nightfall-documentation","https://help.nightfall.ai/faqs/data_tagging","# Does Nightfall require data to be already tagged?\n\nNo, Nightfall doesn’t require data to be pre-tagged. Nightfall uses machine learning to detect 100+ types of sensitive data out of the box, without prior tuning or tagging required. This includes forms of PII, PHI, PCI, and other sensitive content – for example, emails, social security numbers, etc. Our detectors leverage context surrounding a specific token to properly identify and classify it, which dramatically improves accuracy over traditional rules-based approaches to DLP.\n","2026-08-04T17:12:57.480Z","2026-08-04T17:12:57.504Z","f63bf578-dced-4840-801d-d375e99de815",[],[],[],"DLP APIs - Native SaaS Apps | Developer APIs | Nightfall Documentation","dlp-apis-native-saas-apps-developer-apis-nightfall-documentation","https://help.nightfall.ai/developer-api/nightfall_apis/saas","# DLP APIs - Native SaaS Apps | Developer APIs\n\nstatethe violation states to filter onuser\\_emailthe emails of users updating the resource resulting in the violationuser\\_namethe usernames of users updating the resource resulting in the violationintegration\\_namethe integration to filter onconfidenceone or more likelihoods/confidencespolicy\\_idone or more policy IDsdetection\\_rule\\_idone or more detection rule IDsdetector\\_idone or more detector IDsrisk\\_labelthe risk label to filter onrisk\\_sourcethe risk determination source to filter onslack.channel\\_namethe slack channel names to filter onslack.channel\\_idthe slack channel IDs to filter onslack.workspacethe slack workspaces to filter onconfluence.parent\\_page\\_namethe names of the parent pages in confluence to filter onconfluence.space\\_namethe names of the spaces in confluence to filter ongdrive.drivethe drive names in gdrive to filter onjira.project\\_namethe jira project names to filter onjira.ticket\\_numberthe jira ticket numbers to filter onsalesforce.org\\_namethe salesforce organization names to filter onsalesforce.objectthe salesforce object names to filter onsalesforce.record\\_idthe salesforce record IDs to filter ongithub.author\\_emailthe github author emails to filter ongithub.branchthe github branches to filter ongithub.committhe github commit ids to filter ongithub.orgthe github organizations to filter ongithub.repositorythe github repositories to filter ongithub.repository\\_ownerthe github repository owners to filter onteams.team\\_namethe m365 teams team names to filter onteams.channel\\_namethe m365 teams channels to filter onteams.channel\\_typethe m365 teams channel types to filter onteams.team\\_sensitivitythe m365 teams sensitivities to filter onteams.senderthe m365 teams senders to filter onteams.msg\\_importancethe m365 teams importance to filter onteams.msg\\_attachmentthe m365 teams attachment names to filter onteams.chat\\_idthe m365 teams chat ID to filter onteams.chat\\_typethe m365 teams chat type to filter onteams.chat\\_topicthe m365 teams chat topic to filter onteams.chat\\_participantthe m365 teams chat participant's display name to filter ononedrive.drive\\_ownerdrive owner's display name to filter ononedrive.drive\\_owner\\_emaildrive owner's email to filter ononedrive.file\\_namethe file name to filter ononedrive.created\\_bythe m365 user, who created the file in the drive, display name to filter ononedrive.created\\_by\\_emailthe m365 users, who created the file in the drive, email to filter ononedrive.modified\\_bythe m365 users, who last modified the file in the drive, display name to filter ononedrive.modified\\_by\\_emailthe m365 users, who last modified the file in the drive, email to filter onzendesk.ticket\\_statusthe zendesk ticket status to filter onzendesk.ticket\\_titlethe zendesk ticket titles to filter onzendesk.ticket\\_group\\_assigneethe zendesk ticket assignee groups to filter onzendesk.current\\_user\\_rolethe zendesk ticket current assignee user's roles to filter onnotion.created\\_bythe names of the users creating a resource in notion to filter onnotion.last\\_edited\\_bythe names of the users editing a resource in notion to filter onnotion.page\\_titlethe page names in notion to filter onnotion.workspace\\_namethe workspace names in notion to filter ongmail.user\\_namethe names of the sender to filter ongmail.fromthe email of sender to filter ongmail.tothe email or name of recipients to filter ongmail.ccthe email or name of cc to filter ongmail.bccthe email or name of bcc to filter ongmail.thread\\_idthe thread id of email to filter ongmail.subjectthe subject of email to filter ongmail.attachment\\_namethe name of attachment to filter ongmail.attachment\\_typethe type of attachment to filter onlast\\_actioned\\_bythe entity that performed the last action on the violation, can be one of NIGHTFALL, ADMIN or END\\_USER\n","2026-08-04T17:13:03.386Z","2026-08-04T17:13:03.413Z","4eb8889f-0c78-4141-986d-7852e91febd7",[],[],[],"DLP APIs - Firewall for AI Platform | Developer APIs | Nightfall Documentation","dlp-apis-firewall-for-ai-platform-developer-apis-nightfall-documentation","https://help.nightfall.ai/developer-api/nightfall_apis/dlp","# DLP APIs - Firewall for AI Platform | Developer APIs\n\n```\nPOST /v3/scan HTTP/1.1\nHost: api.nightfall.ai\nAuthorization: Bearer YOUR_SECRET_TOKEN\nContent-Type: application/json\nAccept: */*\nContent-Length: 1595\n\n{\n \"policyUUIDs\": [\n \"text\"\n ],\n \"policy\": {\n \"detectionRuleUUIDs\": [\n \"text\"\n ],\n \"detectionRules\": [\n {\n \"name\": \"text\",\n \"logicalOp\": \"ANY\",\n \"detectors\": [\n {\n \"minNumFindings\": 1,\n \"minConfidence\": \"VERY_UNLIKELY\",\n \"detectorUUID\": \"text\",\n \"displayName\": \"text\",\n \"detectorType\": \"NIGHTFALL_DETECTOR\",\n \"nightfallDetector\": \"AMERICAN_BANKERS_CUSIP_ID\",\n \"regex\": {\n \"pattern\": \"text\",\n \"isCaseSensitive\": true\n },\n \"wordList\": {\n \"values\": [\n \"text\"\n ],\n \"isCaseSensitive\": true\n },\n \"contextRules\": [\n {\n \"regex\": {\n \"pattern\": \"text\",\n \"isCaseSensitive\": true\n },\n \"proximity\": {\n \"windowBefore\": 1,\n \"windowAfter\": 1\n },\n \"confidenceAdjustment\": {\n \"fixedConfidence\": \"VERY_UNLIKELY\"\n }\n }\n ],\n \"exclusionRules\": [\n {\n \"matchType\": \"PARTIAL\",\n \"exclusionType\": \"REGEX\",\n \"regex\": {\n \"pattern\": \"text\",\n \"isCaseSensitive\": true\n },\n \"wordList\": {\n \"values\": [\n \"text\"\n ],\n \"isCaseSensitive\": true\n }\n }\n ],\n \"redactionConfig\": {\n \"maskConfig\": {\n \"maskingChar\": \"text\",\n \"charsToIgnore\": [\n \"text\"\n ],\n \"numCharsToLeaveUnmasked\": 1,\n \"maskLeftToRight\": true\n },\n \"infoTypeSubstitutionConfig\": {},\n \"substitutionConfig\": {\n \"substitutionPhrase\": \"text\"\n },\n \"cryptoConfig\": {\n \"publicKey\": \"text\"\n },\n \"removeFinding\": true\n },\n \"scope\": \"Content\"\n }\n ]\n }\n ],\n \"contextBytes\": 1,\n \"defaultRedactionConfig\": {\n \"maskConfig\": {\n \"maskingChar\": \"text\",\n \"charsToIgnore\": [\n \"text\"\n ],\n \"numCharsToLeaveUnmasked\": 1,\n \"maskLeftToRight\": true\n },\n \"infoTypeSubstitutionConfig\": {},\n \"substitutionConfig\": {\n \"substitutionPhrase\": \"text\"\n },\n \"cryptoConfig\": {\n \"publicKey\": \"text\"\n },\n \"removeFinding\": true\n },\n \"alertConfig\": {\n \"slack\": {\n \"target\": \"text\"\n },\n \"email\": {\n \"address\": \"text\"\n },\n \"url\": {\n \"address\": \"text\"\n },\n \"siem\": {\n \"address\": \"text\",\n \"sensitiveHeaders\": {\n \"ANY_ADDITIONAL_PROPERTY\": \"text\"\n },\n \"plainTextHeaders\": {\n \"ANY_ADDITIONAL_PROPERTY\": \"text\"\n }\n }\n }\n },\n \"payload\": [\n \"text\"\n ]\n}\n```\n","2026-08-04T17:13:03.254Z","2026-08-04T17:13:03.281Z","b90ccac3-2bcc-419f-92f2-54b0f0ea7e3f",[],[],[],"Directory Sync | Nightfall Documentation","directory-sync-nightfall-documentation","https://help.nightfall.ai/nightfall_settings/directory_sync","This document explains how to integrate Nightfall with your identity providers (IdPs) like Microsoft Entra ID, Google Workspace Directory, and Okta Service. This integration simplifies policy management in Nightfall allowing you to include or exclude users and user groups, by leveraging existing user information for easier administration within Nightfall and other SaaS products.\n\n## Advantages of Integration[](https://help.nightfall.ai/nightfall_settings/directory_sync#advantages-of-integration)\n\n- **Simplified Policy Management**: Nightfall automatically synchronises user and group information from your IDps, eliminating the need for manual user inclusions or exclusions in policies. This continuous sync ensures your policies always reflect the latest user directory information, streamlining management and reducing administrative overhead.\n\n- **Tailored Policies with User Groups**: Leverage existing user groups defined in your IdPs to easily create granular DLP policies within Nightfall. Assign specific access and permission levels to different user groups, ensuring data security and compliance across various SaaS applications like Microsoft Teams, OneDrive, and Google Drive.\n\n- **Dynamic User Management**: As users are added or removed from your IdP directory, Nightfall automatically reflects these changes, updating your DLP policies. This ensures your policies remain accurate and relevant, eliminating the need for manual updates.\n\n## Configuring Directory Sync[](https://help.nightfall.ai/nightfall_settings/directory_sync#configuring-directory-sync)\n\nThe Directory Sync feature allows you to connect your user directories (Microsoft Entra ID and Google Workspace) with Nightfall. This sync is essential for enabling functionalities within Nightfall's SaaS apps like Microsoft 365 Teams, OneDrive for Business, Google Drive, and other apps.\n\n- **Microsoft Teams Direct Message Monitoring (Azure Entra ID):** To monitor direct messages in Microsoft Teams for potential data leaks, Nightfall requires access to your Microsoft Entra ID account. Syncing your Entra ID account grants Nightfall a list of active users and groups, facilitating the monitoring of user communication and data flow.\n\n- **OneDrive for Business**: To monitor user OneDrive for potentially sensitive data leaks Nightfall requires access to your Microsoft OneDrive for Business account. Syncing your Entra ID account grants Nightfall a list of active users and groups, facilitating the monitoring of user One Drives.\n\n**Supported Identity Providers**\n\nNightfall currently integrates with the following IDps:\n","2026-08-04T17:12:50.967Z","2026-08-04T18:28:53.376Z","a4b3527c-ab67-4dd2-922b-e6b670f8d075",[],[],[],"Detectors | Nightfall Documentation","detectors-nightfall-documentation","https://help.nightfall.ai/detection_platform/detectors","A Detector is a tool that scans any online entity to detect if any sensitive data is present in the entity. An \"entity\" can refer to any resource on the Internet like a file in Google Drive, ticket data in JIRA, code snippets in GitHub, customer data in Salesforce, and so on.\n\nThere are two types of detectors; Nightfall Detectors and Custom Detectors.\n\n## **Nightfall Detectors**[](https://help.nightfall.ai/detection_platform/detectors#nightfall-detectors)\n\nNightfall provides a comprehensive library of **machine learning–powered detectors** that identify sensitive data across text, images, files, and source code with 90%-95% precision out of the box. All detectors are available immediately in your workspace under **Detection → Detectors**\n\nDetectors power the core of Nightfall’s data protection capabilities. They allow you to quickly scan and classify content for risks such as PII, PHI, financial data, credentials, intellectual property (IP), confidential corporate documents, and more.\n\nNightfall offers two primary types of detectors:\n\n## **1. Entity Detectors**[](https://help.nightfall.ai/detection_platform/detectors#id-1.-entity-detectors)\n\nEntity Detectors identify **specific pieces of sensitive information**—such as an SSN, a driver’s license number, credit card number, password, or an api key —where the format is known and can be validated.\n\nEntity Detectors use:\n\n- Pattern recognition\n\n- Natural-language context\n\n- Validation logic\n\n- ML-based disambiguation\n\nThese detectors are ideal when you need precise identification of well-defined data types (e.g., U.S. Social Security Numbers, credit card numbers, or country-specific passport IDs).\n\n#### **Examples of When Entity Detectors Are Useful**[](https://help.nightfall.ai/detection_platform/detectors#examples-of-when-entity-detectors-are-useful)\n\n- Detecting employees’ personal data in outbound messages\n\n- Preventing customer PII leaks (e.g., driver's license numbers)\n\n- Flagging financial identifiers in logs or repositories\n\n- Monitoring exposed secrets or API keys\n\nEntity Detectors answer the question: **“Does this content contain PII, PCI, PHI, or credentials?”**\n\n## **2.** File Classifiers[](https://help.nightfall.ai/detection_platform/detectors#id-2.-file-classifiers)\n\nFile Classifiers identify intellectual property and confidential documents—your organization’s **crown jewels**—based on a file’s **content, structure, and semantic meaning**, not just the presence of individual data types like PII or API keys.\n\nInstead of asking _“Does this file contain a sensitive string?”_, File Classifiers answer a more important question:\n\n> **“What type of document is this, and how sensitive is it?”**\n\n#### What File Classifiers Detect[](https://help.nightfall.ai/detection_platform/detectors#what-file-classifiers-detect)\n\nFile Classifiers are designed to identify entire **document types**, including:\n\n- Proprietary source code and internal algorithms\n\n- Confidential business documents and internal reports\n\n- Unreleased product materials and R\\&D artifacts\n\n- Financial statements, forecasts, tax files, and regulatory drafts\n\n- Legal agreements, contracts, and NDAs\n\n- Patient and medical records\n\n- Customer lists and account data\n\n- Images of physical documents (e.g., passports, IDs, credit cards)\n\n#### How File Classification Works[](https://help.nightfall.ai/detection_platform/detectors#how-file-classification-works)\n\nTo classify files accurately, Nightfall analyzes signals across the full document, including:\n\n- Writing style and technical terminology\n\n- Domain-specific language (legal, engineering, HR, finance, healthcare)\n\n- File structure (headings, tables, templates, layouts)\n\n- Semantic meaning at the paragraph and document level\n\n- Visual elements in scanned or image-based documents\n\n#### Why This Matters[](https://help.nightfall.ai/detection_platform/detectors#why-this-matters)\n\nBy understanding **what a document is**, not just **what it contains**, File Classifiers enable you to detect and protect your most business-critical assets from:\n\n- Accidental sharing\n\n- Insider risk\n\n- Malicious exfiltration\n\nThis approach closes the gap where traditional, entity-based DLP falls short.\n\nTo view the detectors of a specific category, click the category name. All the Nightfall detectors' category names are highlighted in the above image.\n\nFor the complete list of all the detectors present in all the categories, you can view the [Nightfall Detector Glossary](https://help.nightfall.ai/detection_platform/detection_glossary) document.\n\nNow that you are aware of all the available detectors, you can choose to use any of the existing Nightfall detectors or create your detector specific to your organization's requirements. If you are not sure of which Nightfall detector to use, view the [Choosing a Nightfall Detector](https://help.nightfall.ai/detection_platform/choosing_detectors) document.\n\nIf Nightfal detectors can address your organization's requirements and you do not wish to create any custom detectors, you can refer to the [Create Detection Rules](https://help.nightfall.ai/detection_platform/create_detection_rules) document, to learn about how to add detectors to a detection rule.\n\nIf Nightfall detectors cannot address your organization's requirements, you can create your own detector(s) or customize a Nightfall detector. You can refer to the [Creating Custom Detectors](https://help.nightfall.ai/detection_platform/custom_detectors) document to learn about custom detectors.\n","2026-08-04T17:12:47.258Z","2026-08-04T18:29:05.928Z","d6ebe5a1-49db-4951-94a2-3539eaf063d4",[],[],[],"Detection Rules | Nightfall Documentation","detection-rules-nightfall-documentation","https://help.nightfall.ai/nightfall_policy_templates/detection_rules","To view the recommended configurations to apply to different use cases, you are welcome to leverage the [**Detection Wizard**](https://playground.nightfall.ai/detection-wizard) in the Nightfall Playground. This wizard will generate the detection rules that you can apply in your Nightfall console. Learn more about [**Creating Detection Rules**](https://help.nightfall.ai/detection_platform/create_detection_rules).\n\nOnce you have generated the detection rules, you can implement these templates on your own and add the detection rules to your [**Nightfall Dashboard**](https://app.nightfall.ai/detection-engine/detection-rules). You should be all set within 10-15 minutes.\n\nAlternatively, feel free to forward the email you receive with the templates to to have your Customer Success Manager implement these in your tenant on your behalf.\n\nOnce you've implemented your detection rules, test them using our [**sample data sets**](https://help.nightfall.ai/nightfall-detection-and-policy-templates/nightfall-test-data-sets).\n","2026-08-04T17:12:53.464Z","2026-08-04T18:29:07.118Z","0c69305f-fe39-4bbe-bfc1-cd2061259b6a",[],[],[],"Detection Rules | Nightfall AI Knowledge Base","detection-rules-nightfall-ai-knowledge-base","https://kb.nightfall.ai/collections/1035662851-detection-rules","\\[\n\nNightfall Detection Rules: Why is \"Very Likely\" Grayed Out within the Detection Rule?\n\n›\n\n]\\(\n\nNightfall Detection Rules: How to Increase the Confidence of a Custom RegEx Detector\n\n›\n\n]\\(\n\nNightfall Detection Rules: How to Use Regex Context Rules\n\n›\n\n]\\(\n\nNightfall Detection Rules: How to Set Up Credit Card Number Exclusions\n\n›\n\n]\\()\n","2026-08-03T17:22:50.375Z","2026-08-04T19:49:20.146Z","81a66ced-7c22-49c9-a1e3-36f231a6764f",[],[],[],"https://help.nightfall.ai/detection_platform/overview_platform","## **What is machine learning?**[](https://help.nightfall.ai/detection_platform/overview_platform#what-is-machine-learning)\n\nEach machine learning detector is a model, which is trained using curated datasets to recognize sensitive data tokens based on certain characteristics (e.g. structure) and on surrounding context (e.g. preceding words). Machine learning models have the ability to automatically learn and improve from experience, without being explicitly programmed - giving them broader scope and higher accuracy than hard-programmed models (such as r[egular expressions](https://help.nightfall.ai/detection_platform/faq/regex_library)).\n\n## **How do Nightfall’s detectors leverage machine learning?**[](https://help.nightfall.ai/detection_platform/overview_platform#how-do-nightfalls-detectors-leverage-machine-learning)\n\nNightfall’s detectors are trained via machine learning to recognize many potential permutations of sensitive data tokens, and also to recognize and assess the surrounding context. The ability to recognize a variety of data structures and context gives Nightfall’s detection far more scope and accuracy than traditional regular expression (regex)-based detection. Nightfall’s internal team of machine learning engineers and data scientists are continuously developing new machine learning-based detectors, and they also handle the ongoing maintenance and training of our detection engine to continually improve accuracy and results.\n\n## **Understanding Accuracy**[](https://help.nightfall.ai/detection_platform/overview_platform#understanding-accuracy)\n\nA little background on measuring accuracy will be helpful to understand before you embark on your detector optimization journey. Accuracy is the ability of a detector to correctly flag sensitive content and not flag content that is not sensitive.\n\nNo detector is 100% accurate, and it is possible to have a discrepancy between information that is actually sensitive, and information that is flagged by a detector as sensitive. For example, a detector may incorrectly assess a piece of sensitive content as nonsensitive (this would be a false positive). The various result types you may get, based on the actual versus assessed sensitivity of content, are illustrated below.\n\n**Accuracy = (TP + TN) / (TP + TN + FP + FN)**\n\n**Sensitivity = TP / (TP + FN)**\n\n**Specificity = TN / (FP + TN)**\n\nYour organization will, of course, want sensitive data detection to be as accurate as possible. However, it’s important to understand that there is always a tradeoff between accurately identifying true positives (sensitivity) versus accurately identifying true negatives (specificity).\n\n- Sensitivity (also known as: recall, hit rate, or true positive rate \\[TPR]) is the ability of a detector to correctly identify content with sensitive findings.\n\n- Specificity (also known as: selectivity, true negative rate \\[TNR]) is the ability of a detector to correctly identify content without sensitive data.\n\nThe tradeoff between sensitivity and specificity occurs because you must choose whether to optimize a detector toward or away from flagging information. Higher sensitivities mean lower specificities and vice versa. For example, to optimize for sensitivity, you may enable more detectors at lower minimum confidences to catch more true positives. In doing so, you will open yourself up to more false positives, which will lower your specificity.\n\nAs a result, each organization should spend time optimizing its detectors to strike the right balance between sensitivity and specificity.\n\n## **Confidence Levels**[](https://help.nightfall.ai/detection_platform/overview_platform#confidence-levels)\n\nA confidence level represents Nightfall’s confidence in the accuracy of a given detection. Each detector is a unique model and will have its own confidence level profile. For details on how confidence level is determined for a given detector, please reach out to us.\n\nConfidence may be any of the following values corresponding to the given confidence intervals:\n\nEach info type is unique, so it is not possible to dictate that what yields a “Very Likely” match for one detector, will yield a “Very Likely” result for another. Nonetheless, we can provide some high-level guidance. Generally speaking, higher confidence detections may have certain features that increase confidence in the detection being accurate - some examples of the features include:\n\n- Formatting of token\n\n- Passes validation functions\n\n- Passes substring checks\n\n- Context clues that are indicative of that info type\n\n- Model scoring\n","2026-08-04T17:12:51.667Z","2026-08-04T18:29:06.265Z",[],[],[],[],[],[],"https://kb.nightfall.ai/collections/4598309553-detection","Why a Government ID (SSN, National ID, Tax ID, Passport) Was Not Detected\n\n›\n","2026-08-03T17:22:50.943Z","2026-08-04T19:49:20.488Z",[],[],[],"Deploy a File Scanner for Sensitive Data in 40 Lines of Code | Developer APIs | Nightfall Documentation","deploy-a-file-scanner-for-sensitive-data-in-40-lines-of-code-developer-apis-nightfall-documentation","https://help.nightfall.ai/developer-api/nightfall-use-cases/file_scanner","# Deploy a File Scanner for Sensitive Data in 40 Lines of Code | Developer APIs\n\nThe service ingests a local file, scans it for sensitive data with Nightfall, and displays the results in a simple table UI.\n\nWe'll deploy the server on Render (a PaaS Heroku alternative) so that you can serve your application publicly in production instead of running it off your local machine. You'll build familiarity with the following tools and frameworks: Python, Flask, Nightfall, Ngrok, Jinja, Render.\n\n## Key Concepts[](https://help.nightfall.ai/developer-api/nightfall-use-cases/file_scanner#key-concepts)\n\nBefore we get started on our implementation, start by familiarizing yourself with [how scanning files works](about:/docs/scanning-files#prerequisites) with Nightfall, so you're acquainted with the flow we are implementing.\n\nIn a nutshell, file scanning is done asynchronously by Nightfall; after you upload a file to Nightfall and trigger the scan, we perform the scan in the background. When the scan completes, Nightfall delivers the results to you by making a request to your webhook server. This asynchronous behavior allows Nightfall to scan files of varying sizes and complexities without requiring you to hold open a long synchronous request, or continuously poll for updates. The impact of this pattern is that you need a webhook endpoint that can receive inbound notifications from Nightfall when scans are completed - that's what we are building in this tutorial.\n\n## Getting Started[](https://help.nightfall.ai/developer-api/nightfall-use-cases/file_scanner#getting-started)\n\nYou can fork the sample repo and view the complete code [here](https://github.com/nightfallai/file-scanner-tutorial), or follow along below. If you're starting from scratch, create a new GitHub repository.\n\n## Setting Up Dependencies[](https://help.nightfall.ai/developer-api/nightfall-use-cases/file_scanner#setting-up-dependencies)\n\nFirst, let's start by installing our dependencies. We'll be using Nightfall for data classification, the [Flask](https://flask.palletsprojects.com/en/2.0.x/) web framework in Python, and [Gunicorn](https://gunicorn.org/) as our web server. Create `requirements.txt` and add the following to the file:\n\nThen run `pip install -r requirements.txt` to do the installation.\n\n## Configuring Detection with Nightfall[](https://help.nightfall.ai/developer-api/nightfall-use-cases/file_scanner#configuring-detection-with-nightfall)\n\nNext, we'll need our Nightfall API Key and Webhook Signing Secret; the former authenticates us to the Nightfall API, while the latter authenticates that incoming webhooks are originating from Nightfall. You can retrieve your API Key and Webhook Signing Secret from the Nightfall [Dashboard](https://app.nightfall.ai/). Complete the Nightfall Quickstart for a more detailed walk-through. [Sign up](https://app.nightfall.ai/sign-up) for a free Nightfall account if you don't have one.\n\nThese values are unique to your account and should be kept safe. This means that we will store them as environment variables and should not store them directly in code or commit them into version control. If these values are ever leaked, be sure to visit the Nightfall Dashboard to re-generate new values for these secrets.\n\n## Setting Up Our Server[](https://help.nightfall.ai/developer-api/nightfall-use-cases/file_scanner#setting-up-our-server)\n\nLet's start writing our Flask server. Create a file called `app.py`. We'll start by importing our dependencies and initializing the Flask and Nightfall clients:\n\nNext, we'll add our first route, which will display \"Hello World\" when the client navigates to `/ping` simply as a way to validate things are working:\n\nRun `gunicorn app:app` on the command line to fire up your server, and navigate to your local server in your web browser. You'll see where the web browser is hosted in the Gunicorn logs, typically it will be `127.0.0.1:8000` aka `localhost:8000`.\n\nTo expose our local webhook server via a public tunnel that Nightfall can send requests to, we'll use ngrok. Download and install ngrok via their quickstart documentation [here](https://ngrok.com/docs/guides/quickstart). We'll create an ngrok tunnel as follows:\n\nAfter running this command, `ngrok` will create a tunnel on the public internet that redirects traffic from their site to your local machine. Copy the HTTPS tunnel endpoint that ngrok has created: we can use this as the webhook URL when we trigger a file scan.\n\nLet's set this HTTPS endpoint as a local environment variable so we can reference it later:\n\nTip: With a Pro ngrok account, you can create a subdomain so that your tunnel URL is consistent, instead of randomly generated each time you start the tunnel.\n\n## Handling an Inbound Webhook[](https://help.nightfall.ai/developer-api/nightfall-use-cases/file_scanner#handling-an-inbound-webhook)\n\nBefore you send a file scan request to Nightfall, let's add logic for our incoming webhook endpoint, so that when Nightfall finishes scanning a file, it can successfully send the sensitive findings to us.\n\nFirst, what does it mean to have findings? If a file has findings, this means that Nightfall identified sensitive data in the file that matched the detection rules you configured. For example, if you told Nightfall to look for credit card numbers, any substring from the request payload that matched our credit card detector would constitute sensitive findings.\n\nWe'll host our incoming webhook at `/ingest` with a POST method.\n\nNightfall will POST to the webhook endpoint, and in the inbound payload, Nightfall will indicate if there are sensitive findings in the file, and provide a link where we can access the sensitive findings as JSON.\n\nRestart your server so the changes propagate. We'll take a look at the console output of our webhook endpoint and explain what it means in the next section.\n\n## Scan a File[](https://help.nightfall.ai/developer-api/nightfall-use-cases/file_scanner#scan-a-file)\n\nNow, we want to trigger a file scan request, so that Nightfall will scan the file and send a POST request to our `/ingest` webhook endpoint when the scan is complete. We'll write a simple script that sends a file to Nightfall to scan it for [credit card numbers](about:/docs/detector-glossary#finance). Create a new file called `scan.py`.\n\nFirst, we'll establish our dependencies, initialize the Nightfall client, and specify the filepath to the file we wish to scan as well as the webhook endpoint we created above. The filepath is a relative path to any file, in this case we are scanning the `sample-pci-xs.csv` file which is in the same directory as `scan.py`. This is a sample CSV file with 10 credit card numbers in it - you can download it in the tutorial's GitHub [repo](https://github.com/nightfallai/file-scanner-tutorial).\n\nNext, we will initiate the scan request to Nightfall, by specifying our filepath, webhook URL where the scan results should be posted, and our Detection Rule that specifies what sensitive data we are looking for.\n\nIn this simple example, we have specified an inline Detection Rule that detects Likely Credit Card Numbers. This Detection Rule is a simple starting point that just scratches the surface of the types of detection you can build with Nightfall. Learn more about building inline detection rules here or how to configure them in the Nightfall [Dashboard](https://app.nightfall.ai/developer-platform).\n\nThe `scan_id` is useful for identifying your scan results later.\n\n## View Sensitive Findings[](https://help.nightfall.ai/developer-api/nightfall-use-cases/file_scanner#view-sensitive-findings)\n\nLet's run `scan.py` to trigger our file scan job.\n\nOnce Nightfall has finished scanning the file, we'll see our Flask server receive the request at our webhook endpoint (`/ingest`). In our code above, we parse the webhook payload, and print the following when there are sensitive findings:\n\nIn our output, we are printing two URLs.\n\nThe first URL is provided to us by Nightfall. It is the temporary signed S3 URL that we can access to fetch the sensitive findings that Nightfall detected.\n\nThe second URL won't work yet, we'll implement it next. This URL a we constructed in our `ingest()` method above - the URL calls `/view` and passes the Findings URL above as a URL-escaped query parameter.\n\nLet's add a method to our Flask server that opens this URL and displays the findings in a formatted table so that the results are easier to view than downloading them as JSON.\n\nWe'll do this by adding a `view` method that responds to GET requests to the `/view` route. The `/view` route will read the URL to the S3 Findings URL via a query parameter. It will then open the findings URL, parse it as JSON, pass the results to an HTML template, and display the results in a simple HTML table using [Jinja](https://jinja.palletsprojects.com/en/3.0.x/). Jinja is a simple templating engine in Python.\n\nAdd the following to our Flask server in `app.py`:\n\n## Create the Table View[](https://help.nightfall.ai/developer-api/nightfall-use-cases/file_scanner#create-the-table-view)\n\nTo display the findings in an HTML table, we'll create a new Flask template. Create a folder in your project directory called `templates` and add a new file within it called `view.html`.\n\nOur template uses Jinja to iterate through our findings, and create a table row for each sensitive finding.\n\nNow, if we restart our Flask server, trigger a file scan request, and navigate to the \"View\" URL printed in the server logs, we should see a formatted table with our results! In fact, we can input any Nightfall-provided signed S3 URL (after URL-escaping it) in the `findings_url` parameter of the `/view` route to view it.\n\n## Deploy on Render[](https://help.nightfall.ai/developer-api/nightfall-use-cases/file_scanner#deploy-on-render)\n\nAs a longtime Heroku user, I was initially inclined to write this tutorial with instructions to deploy our app on Heroku. However, new PaaS vendors have been emerging and I was curious to try them out and see how they compare to Heroku. One such vendor is Render, which is where we'll deploy our app.\n\nDeploying our service on Render is straightforward. If you're familiar with Heroku, the process is quite similar. Once you've signed up or logged into Render (free), we'll do the following:\n\n1. Create a new `Web Service` on Render, and permit Render to access your new repo.\n\n2. Use the following values during creation:\n\n- Environment: Python\n\n- Build Command: `pip install -r requirements.txt`\n\n- Start Command: `gunicorn app:app`\n\nLet's also set our environment variables during creation. These are the same values we set locally.\n\n## Scan a file (in production)[](https://help.nightfall.ai/developer-api/nightfall-use-cases/file_scanner#scan-a-file-in-production)\n\nOnce Render has finished deploying, you'll get the base URL of your application. Set this as your `NIGHTFALL_SERVER_URL` locally and re-run `scan.py` - this time, the file scan request is served by your production Flask server running on Render!\n\nTo confirm this, navigate to the `Logs` tab in your Render app console, you'll see the webhook's output of your file scan results:\n\nNavigate to the `View` link above in your browser to verify that you can see the results formatted in a table on your production site.\n\nCongrats, you've successfully created a file scanning server and deployed it in production! You're now ready to build more advanced business logic around your file scanner. Here are some ideas on how to extend this tutorial:\n\n- Use WebSockets to send a notification back from the webhook to the client that initiated the file scan request\n\n- Build a more advanced detection rule using pre-built or custom detectors\n\n- Add a user interface to add more interactive capabilities, for example allowing users to upload files or read files from URLs\n","2026-08-04T17:13:00.807Z","2026-08-04T17:13:00.849Z","3799e5f7-3c40-423c-b088-6dda535d95c4",[],[],[],"Data Encryption: How to Perform the One-Time Local Approval of the Extension | Nightfall AI Knowledge Base","data-encryption-how-to-perform-the-one-time-local-approval-of-the-extension-nightfall-ai-knowledge-b","https://kb.nightfall.ai/articles/7699220704-data-encryption-how-to-perform-the-one-time-local-approval-of-the-extension","# Data Encryption: How to Perform the One-Time Local Approval of the Extension\n\nLast updated 1 month ago\n\n## Purpose\n\nTo locally approve the Google connection and extension on a machine for the first- and only-time\n\n## Environment\n\n- Google Chrome: All versions\n\n- Google Workspace: Gmail\n\n- Nightfall Extension: All versions\n\n## Resolution\n\n### Enable the Extension\n\n1. Click on the Nightfall extension at the top-right of the Chrome browser.\n\n NOTE: It is normal to see a red square with a black exclamation mark.\n\n2. Click the \"**Grant Permissions**\" button.\n\n![image.png](/api/knowledge-base/images/894460cf-8de6-46a0-81f7-e9c888749a3f \"image.png\")\n\n3. Follow the prompts to enable the Nightfall DLP extension.\n\n ![image.png](/api/knowledge-base/images/461eec8a-e27d-496e-930c-949b0cc0de42 \"image.png\")\n\n### Connect the Gmail Account\n\n_This requires the user to send their very first email with data encryption being enabled._\n\n1. Send a real or test email.\n\n 1. **Log** into Gmail\n\n 2. **Click** Compose\n\n 3. **Type** out the email\n\n 4. **Send** the email\n2. After sending, follow the prompts.\n\n 1. Select your email when prompted.\n\n ![image.png](/api/knowledge-base/images/45b095cd-7fa5-499d-89f3-08163f7a303d \"image.png\")\n 2. Click \"**Continue**\" to allow Nightfall DLP to access your work info related your email.\n\n ![image.png](/api/knowledge-base/images/02230f72-565d-4c8f-9def-cd64db20bd3a \"image.png\")\n 3. Lastly, checkmark \"**Select All**\" and click \"**Continue**\".\n\n ![image.png](/api/knowledge-base/images/ce43a204-ae18-4f12-b17a-549061ae1d46 \"image.png\")\n\nHow helpful was this article?\n","2026-08-03T17:22:54.262Z","2026-08-04T19:49:25.778Z","1a2cc70e-47fb-40b7-8212-7ca45448e463",[],[],[],"Data Discovery and Classification | Data Classification and Discovery | Nightfall Documentation","data-discovery-and-classification-data-classification-and-discovery-nightfall-documentation","https://help.nightfall.ai/audit","# Data Discovery and Classification | Data Classification and Discovery\n\nFor the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). This page is also available as [Markdown](https://help.nightfall.ai/audit/data-discovery-and-classification.md).\n\n![Cover](/api/knowledge-base/images/32688f30-26d7-480e-8d3c-fd78161d1911)\n\nIntroduction\n\n![Cover](/api/knowledge-base/images/be154424-7079-43b4-9dc9-07c039b67b0f)\n\nGoogle Drive Audit\n\n![Cover](/api/knowledge-base/images/db8ebfe1-7459-4bc9-a9a4-ef4103b88c01)\n\nGitHub Audit\n\nLast updated 1 year ago\n\nWas this helpful?\n","2026-08-04T17:12:40.899Z","2026-08-04T18:29:02.706Z","50b16a71-6ad0-45c3-a99d-6524e2f3551a",[],[],[],"Data Detection and Response Events | Nightfall Documentation","data-detection-and-response-events-nightfall-documentation","https://help.nightfall.ai/dashboard/sdp_events","# Data Detection and Response Events\n\nAn Event is an incident that is triggered when a data leak is detected by Nightfall. The Data data detection and response (aka sensitive data protection) Events page displays all the details about the data sensitive events recorded in Nightfall from all the integrations.\n\nBefore we proceed further, let's understand what exactly is a Finding and a Event.\n\n**Finding:** A Finding refers to a single instance of a data leak incident detected during scanning.\n\n**Event:** An Event is an incident of data leaks, and a collection of findings that were detected while scanning an entire document or data in your database.\n\n## Events vs Findings[](https://help.nightfall.ai/dashboard/sdp_events#events-vs-findings)\n\nWhen Nightfall scans data, a single Event can have multiple findings. For instance, consider that you upload a document to Google Drive. This document has 10 instances of secret information (10 API keys or 10 credit card numbers). These 10 instances are known as Findings. Since Nightfall scans the entire Google document at once, these 10 Findings are recorded as a single Event.\n\n## Event List View[](https://help.nightfall.ai/dashboard/sdp_events#event-list-view)\n\nThe sensitive data Event list view page consists of a table that displays the details of each Event. The contents consist of columns which are described as follows.\n\n## Event Likelihood[](https://help.nightfall.ai/dashboard/sdp_events#event-likelihood)\n\nThe **Finding** column displays the name of the detector whose condition was violated thus resulting in the generation of the Event. The Finding column displays a list of Events that originated from scanning a single file, a web page, or any other publicly available entity.\n\nEach Event's name is the same as the Detector's name whose condition was violated. You can also view the Likelihood or confidence level (Possible, Likely, Very Likely) of an Event being an actual case of data leak and also the number of instances for each Likelihood. The **Possible** Likelihood Findings are displayed in blue color with a fully dotted blue circle. The **Likely** Finding is displayed in yellow color with a half-dotted and half-shaded yellow circle. The **Very Likely** Finding is displayed in red color with a red circle.\n\nFor instance, in the following image, a detector called Person name violated 28 times. Of these 28 instances of violations, 1 is **Possible Event** (in blue), 5 are **Likely Events** (in yellow), and 22 are **Very Likely** Events (in red).\n\n## Event Detail View[](https://help.nightfall.ai/dashboard/sdp_events#event-detail-view)\n\nThe Event detail view consists of various sections. These sections are as follows.\n\n### Event Detail View First Section[](https://help.nightfall.ai/dashboard/sdp_events#event-detail-view-first-section)\n\nEach field is highlighted and a number is associated with the highlighted field. Using the number, you can refer to the section that follows the image to learn more about the field associated with that number.\n\n1 - Name of the Event\n\n2 - Current Status of the Event. For more information on Event status, refer to the [Event Status](https://help.nightfall.ai/dashboard/sdp_events/status) document.\n\n3 - The nature (Credit card in the above image) and number of Findings (1 in the above image) in the Event.\n\n4 - The name of the document in which the sensitive data was found (TEst Automation Action.Docx in the above image). If there are multiple documents that contain sensitive data, each document is listed here. However, in this case only one document contained sensitive data.\n\n5 - The actual sensitive data found in the document (4242-4242-4242-4242 in the above image). The sensitive data is highlighted in yellow which indicates the Likelihood is **Likely**. Findings whose Likelihood are **Very Likely** are highlighted in red and Findings with Likelihood of Possible are highlighted in blue. For more information on Likelihood, see [Working on Events](https://help.nightfall.ai/dashboard/sdp_events#working-on-events)document.\n\n6 - Number of Findings in the selected document. In the above case there is only one finding and it has a Likelihood is **Possible**.\n\n### Event Detail View Second Section[](https://help.nightfall.ai/dashboard/sdp_events#event-detail-view-second-section)\n\nThe contents of this section vary for each integration. You can view the complete list of fields available in the second section after you click the **Expand Details** button.\n\nThe following section contains tabs for each integration. Each tab represents an integration and contains an image of the second section followed by the description of each fields.\n\nThe second section of the OneDrive detail view is as shown in the following image. The section after the image describes each field.\n\nThe various fields in the above section are as follows.\n\n- **Actions Taken** - The latest action taken on the Event. If no action is taken yet, this field is empty.\n\n- **When** - The time period when the Event was registered.\n\n- **Integration Name** - The Nightfall integration in which the Event was registered (OneDrive in this case).\n\n- **User** - The user whose actions triggered the Event.\n\n- **Violated Policy** - The name(s) of the policy/policies that was violated and as a result of which the Event was triggered.\n\n- **Detection rule** - The name(s) of the detection rule(s) within the policy that was violated.\n\n- **Last modified by** - The name of the user who was the last person to act on the Event.\n\n- **Last modified time** - The date and time when the Event was last modified.\n\n- **File name** - The name of the file that contains sensitive data.\n\n- **OneDrive ID** - The ID of the OneDrive that contains the file holding sensitive data. This field is only available for OneDrive Events.\n\n- **OneDrive Owner** - The name of the user who owns the OneDrive containing file(s) with sensitive data. This field is only available for OneDrive Events.\n\n- **Size** - The size of the file that contains sensitive data.\n\nThe second section of the Google Drive detail view is as shown in the following image. The section after the image describes each field.\n\nThe various fields in the above section are as follows.\n\n- **Actions Taken** - The latest action taken on the Event. If no action is taken yet, this field is empty.\n\n- **When** - The time period when the Event was registered.\n\n- **Integration Name** - The Nightfall integration in which the Event was registered (Google Drive in this case).\n\n- **User** - The user whose actions triggered the Event.\n\n- **Violated Policy** - The name(s) of the policy/policies that was violated and as a result of which the Event was triggered.\n\n- **Detection rule** - The name(s) of the detection rule(s) within the policy that was violated.\n\n- **Type** - The type of the document in which sensitive data exists.\n\n- **Size** - The size of the document in which sensitive data exists.\n\n- **Link Permissions** - The link permissions of the file in which the sensitive data exists.\n\n- **Viewers can Download** - This is a boolean field (Yes/No) which indicates whether users can download the file that contains sensitive data.\n\n- **File Owner** - The email ID of the user who owns the file that contains sensitive data.\n\n- **In Trash** - This is a boolean field (Yes/No) which indicates whether file that contains sensitive data is moved to trash or not.\n\n- **Date Created** - The date and time when the file containing sensitive data was created.\n\n- **Date Last Modified** - The date and time when the file containing sensitive data was last modified.\n\n- **Shared Drive Name** - The name of the shared drive in which the file containing sensitive data resides.\n\n- **Shared With - Internal** - The list of internal users with whom the file is shared.\n\n- **Shared With - External** - The list of internal users with whom the file is shared.\n\n- **Last Edited By** - The email ID of the user who last edited the file that contains sensitive data.\n\nThe second section of the JIRA detail view is as shown in the following image. The section after the image describes each field.\n\nThe various fields in the above section are as follows.\n\n- **Actions Taken** - The latest action taken on the Event. If no action is taken yet, this field is empty.\n\n- **When** - The time period when the Event was registered.\n\n- **Integration Name** - The Nightfall integration in which the Event was registered (JIRA in this case).\n\n- **User** - The user whose actions triggered the Event.\n\n- **Violated Policy** - The name of the policies that was violated and as a result of which the Event was triggered.\n\n- **Detection rule** - The name of the detection rule(s) within the policy that was violated.\n\n- **Event Type** - The type of the event.\n\n- **Project Name** - The name of the project that contains the ticket with sensitive data.\n\n- **Project Type** - The type of the project that contains the ticket with sensitive data.\n\n- **Ticket Number** - The ID of the ticket that contains the ticket with sensitive data.\n\n- **Site** - The URL of the JIRA site that contains the ticket with sensitive data.\n\nThe second section of the Confluence detail view is as shown in the following image. The section after the image describes each field.\n\nThe various fields in the above section are as follows.\n\n- **Actions Taken** - The latest action taken on the Event. If no action is taken yet, this field is empty.\n\n- **When** - The time period when the Event was registered.\n\n- **Integration Name** - The Nightfall integration in which the Event was registered (Confluence in this case).\n\n- **User** - The user whose actions triggered the Event.\n\n- **Violated Policy** - The name of the policies that was violated and as a result of which the Event was triggered.\n\n- **Detection rule** - The name of the detection rule(s) within the policy that was violated.\n\n- **Item Name -** The name of the Confluence entity that contains sensitive data.\n\n- **Site -** The link to the Confluence site that contains sensitive data.\n\n- **Item Type -** The type of the item that contains sensitive data.\n\n- **Is Archived -** This is a boolean field (Yes/No). It states if the Confluence entity containing sensitive data is archived or not.\n\n- **Date Created -** The date and time when the Confluence entity containing sensitive data, was created.\n\n- **Date Last Modified -** The date and time when the Confluence entity containing sensitive data, was last modified.\n\n- **Labels -** The Labels attached to the Confluence entity containing sensitive data, was last modified.\n\n- **Space Name -** The name of the Confluence space that contains sensitive data.\n\n- **Author Name -** The name of the user who created the Confluence entity containing sensitive data.\n\n- **Author Email -** The Email ID of the user who created the Confluence entity containing sensitive data.\n\nThe second section of the Confluence detail view is as shown in the following image. The image The section after the image describes each field.\n\nThe various fields in the above section are as follows.\n\n- **Actions Taken** - The latest action taken on the Event. If no action is taken yet, this field is empty.\n\n- **When** - The time period when the Event was registered.\n\n- **Integration Name** - The Nightfall integration in which the Event was registered (Salesforce in this case).\n\n- **User** - The user whose actions triggered the Event.\n\n- **Violated Policy** - The name of the policies that was violated and as a result of which the Event was triggered.\n\n- **Detection rule** - The name of the detection rule(s) within the policy that was violated.\n\n- **Object Name -** The name of the Salesforce Object that contains sensitive data.\n\n- **Record -** The unique Record ID of the row that contains sensitive data.\n\n- **Content Type -** The format of the file that contains sensitive data.\n\n- **Event Type - The type of the event that resulted in sensitive data creation.**\n\n- **User -** The name of the User who added sensitive data.\n\n- **Organization ID -** The Org ID of the Salesforce org that contains the sensitive data.\n\n- **Organization Type -** The nature of the Salesforce org (Production/Sandbox) that contains the sensitive data.\n\n- **Organization Name -** The name of the Salesforce org that contains the sensitive data.\n\n- **Modified At - The date and time when the record containing sensitive data was last modified.**\n\nThe second section of the Gmail detail view is as shown in the following image. The image The section after the image describes each field.\n\nThe various fields in the above section are as follows.\n\n- **Actions Taken** - The latest action taken on the Event. If no action is taken yet, this field is empty.\n\n- **When** - The time period when the Event was registered.\n\n- **Integration Name** - The Nightfall integration in which the Event was registered (Gmail in this case).\n\n- **User** - The user whose actions triggered the Event.\n\n- **Violated Policy** - The name of the policies that was violated and as a result of which the Event was triggered.\n\n- **Detection rule** - The name of the detection rule(s) within the policy that was violated.\n\n- **Send Date -** The date and time when the Email containing sensitive data was sent.\n\n- **Subject -** The Subject line of the Email that contains sensitive data.\n\n- **From -** The Email ID of the user who sent the Email that contains sensitive data.\n\n- **To -** The Email ID(s) of the recipient user who received the Email that contains sensitive data.\n\n- **Cc -** The Email ID(s) of the user(s) who were included in the CC field of the Email that contains sensitive data.\n\n- **Bcc -** The Email ID(s) of the user(s) who were included in the Bcc field of the Email that contains sensitive data.\n\n- **Thread ID**\n\nThe second section of the Zendesk detail view is as shown in the following image. The image The section after the image describes each field.\n\nThe various fields in the above section are as follows.\n\n- **Actions Taken** - The latest action taken on the Event. If no action is taken yet, this field is empty.\n\n- **When** - The time period when the Event was registered.\n\n- **Integration Name** - The Nightfall integration in which the Event was registered (Zendesk in this case).\n\n- **User** - The user whose actions triggered the Event.\n\n- **Violated Policy** - The name of the policies that was violated and as a result of which the Event was triggered.\n\n- **Detection rule** - The name of the detection rule(s) within the policy that was violated.\n\n- Ticket ID\n\n- Ticket Title\n\n- Date Created\n\n- Date Updated\n\n- User Role\n\n- Zendesk instance\n\n- Ticket Requestor\n\n- Group assignee\n\n- Agent Assignee\n\n- Event Type\n\n- Ticket Type\n\n- Ticket Priority\n\n- Ticket Status\n\n- Ticket Followera\n\nThe second section of the GitHub detail view is as shown in the following image. The image The section after the image describes each field.\n\nThe various fields in the above section are as follows.\n\n- **Actions Taken** - The latest action taken on the Event. If no action is taken yet, this field is empty.\n\n- **When** - The time period when the Event was registered.\n\n- **Integration Name** - The Nightfall integration in which the Event was registered (Confluence in this case).\n\n- **User** - The user whose actions triggered the Event.\n\n- **Violated Policy** - The name of the policies that was violated and as a result of which the Event was triggered.\n\n- **Detection rule** - The name of the detection rule(s) within the policy that was violated.\n\n- **Commit Date** - The date and time when the code containing sensitive information was committed.\n\n- **Organization** - The name of the GitHub organization that contains the code containing data.\n\n- **Branch** - The GitHub branch that contains the code which has sensitive data.\n\n- **Repository** - The GitHub Repository name that contains the code which has sensitive data.\n\n- **Repository Type** - The nature of the repository that contains the code which has sensitive data.\n\nThe second section of the Notion detail view is as shown in the following image. The section after the image describes each field.\n\nThe various fields in the above section are as follows.\n\n- **Actions Taken** - The latest action taken on the Event. If no action is taken yet, this field is empty.\n\n- **When** - The time period when the Event was registered.\n\n- **Integration Name** - The Nightfall integration in which the Event was registered (Confluence in this case).\n\n- **User** - The user whose actions triggered the Event.\n\n- **Violated Policy** - The name of the policies that was violated and as a result of which the Event was triggered.\n\n- **Detection rule** - The name of the detection rule(s) within the policy that was violated.\n\n- **Workspace -** The link to the Notion Workspace that contains sensitive data.\n\n- **Page -** The link to the Notion Page that contains sensitive data.\n\n- **Page Created Date -** The date and time when the Notion page containing sensitive data was created.\n\n- **Last updated Date -** The date and time when the Notion page containing sensitive data was last modified.\n\n- **Created By -** The name of the user who created the Notion page containing sensitive data.\n\n- **Last Edited By -** The name of the user who last edited the Notion page containing sensitive data.\n\n- **Location -** The location of the sensitive data.\n\n- **Page ID -** The unique ID of the Notion page containing sensitive data.\n\n- **Shared Externally -** This is a Boolean field (Yes/No) in dicating if the Notion page containing sensitive data is shared externally or not.\n\nThe second section of the MS Teams detail view is as shown in the following image. The section after the image describes each field.\n\nThe various fields in the above section are as follows.\n\n- **Actions Taken** - The latest action taken on the Event. If no action is taken yet, this field is empty.\n\n- **When** - The time period when the Event was registered.\n\n- **Integration Name** - The Nightfall integration in which the Event was registered (Confluence in this case).\n\n- **User** - The user whose actions triggered the Event.\n\n- **Violated Policy** - The name of the policies that was violated and as a result of which the Event was triggered.\n\n- **Detection rule** - The name of the detection rule(s) within the policy that was violated.\n\n- **Team Name -** The name of the team that contains sensitive data.\n\n- **Team ID -** The unique ID of the team that contains sensitive data.\n\n- **Channel Name -** The name of the Channel that contains sensitive data.\n\n- **Channel Membership -** The membership of the Channel that contains sensitive data.\n\n- **Creation Time -** The date and time when the channel containing sensitive data was created.\n\n- **From -** The Email ID of the user who sent the message containing sensitive data.\n\n- **Message Priority -**\n\n- **Last Edit Time -** The date and time when the message was last edited.\n\n- **Chat Participants -**\n\nThe second section of the Slack detail view is as shown in the following image. The section after the image describes each field.\n\nThe various fields in the above section are as follows.\n\n- **Actions Taken** - The latest action taken on the Event. If no action is taken yet, this field is empty.\n\n- **When** - The time period when the Event was registered.\n\n- **Integration Name** - The Nightfall integration in which the Event was registered (Confluence in this case).\n\n- **User** - The user whose actions triggered the Event.\n\n- **Violated Policy** - The name of the policies that was violated and as a result of which the Event was triggered.\n\n- **Detection rule** - The name of the detection rule(s) within the policy that was violated.\n\n- **File Name -** The name of the file that contains sensitive data.\n\n- **File Type -** The type of the file that contains sensitive data.\n\n- **Location -** The name of the channel that contains sensitive data.\n\n- **Channel Type -** The type of the channel that contains sensitive data.\n\n- **Members -** The number of members that are present in the Channel\\*\\*.\\*\\*\n\n### Event Detail View Third Section[](https://help.nightfall.ai/dashboard/sdp_events#event-detail-view-third-section)\n\nThe third section contains Event logs and comments. These sections are highlighted in the following image.\n\n- **Event logs** - The event logs section contains a log of activities performed on the Event. By default, the first log activity recorded is the Event creation activity. The next set of activities generally provide information about Event notifications sent via various notification channels and actions taken on the Event.\n\n- **Comments** - The comments section allows you to enter comments on the Event. The maximum character limit for the comment is 300.\n\n## Working on Events[](https://help.nightfall.ai/dashboard/sdp_events#working-on-events)\n\nIf a single scanned entity (file or web page) violates multiple detector rules, Nightfall displays the list of all the detectors that the finding has violated. Such Events are displayed with a detector name, followed by a **+1** (if two detectors are violated), **+2** (if three detectors are violated), and so on, on the Event List view.\n\nIn the following image, you can see that the Finding has violated a detector called Credit card number and also another detector. Hence a **+1** is displayed.\n\nIn the above case, if the Finding violated three detectors, **+2** is displayed. If the Finding violated 4 detectors, **+3** is displayed.\n\nTo view the list of detectors violated and the Likelihood (Possible, Likely, and Very Likely) of each finding discovered in the file, click the Event. This opens the Event detail view. You can view the names of the violated detectors and the number of findings on the Event detail view.\n\nIn the following image, a single file **Automated upload 1728418320** has violated three detectors. The detectors are **Person name, Tom Cruise with Exclusions** and **Phone number**. The **Person name** detector has been violated 22 times and hence there are 22 findings for this detector. You can view each of these 22 instances of findings by clicking the **22 Person name** tab and scrolling down. The findings that are highlighted in Blue are **Possible** findings, findings highlighted in Red are **Most Likely** findings, and the findings highlighted in yellow are **Likely** findings. There is a **Showing** field which displays the number of Findings and the likelihood of each finding. In the following image, the **Showing** field displays 22 in red. It implies that all 22 findings have the **Most Likely** likelihood.\n\nThe **Tom Cruise with Exclusions** detector has 3 findings. You can view the Likelihood of each of the 3 findings. You can view the findings that violated this detection rule by clicking the **3 tom cruise with exclusions** tab.\n\nSimilarly, you can click the 3 Phone Number to view the details of the findings that violated the **Phone number** detector.\n\n## Annotating Findings[](https://help.nightfall.ai/dashboard/sdp_events#annotating-findings)\n\nAs learned above, a Event can have multiple findings. If you find that any of the findings discovered by Nightfall is not an actual case of data leak, you can use the **Annotate** feature to annotate the specific finding as a false positive. Furthermore, you can also annotate those findings, which surely are a case of data leak, as true positives. Each finding has the annotate option.\n\nTo annotate a finding:\n\n1. Hover the mouse on the finding that you wish to annotate.\n\n2. Click the annotation icon.\n\n3. Select one of the following annotation options.\n\n- **Not a Credit card number:** Select this option if you feel that the Credit card number discovered by Nightfall is not a credit card number but some other number. This marks the finding as a False positive.\n\n- **Not a violation**: Select this option if you feel the finding discovered by Nightfall is not a violation (an imaginary credit card number shared publicly as an example). This marks the finding as a False positive.\n\n- **True Positive:** Select this option if you feel that the finding discovered by Nightfall is an actual case of data leak. This marks the finding as True positive.\n\n1. (Optional) Enter comments for annotation.\n\n2. (Optional) Turn the **Apply to all identical findings** toggle switch to annotate all the similar findings. Click [Bulk Annotate](https://help.nightfall.ai/dashboard/sdp_events#bulk-annotate) to learn more about this feature.\n\n3. Click **Apply**.\n\nIn step 3, of the above task, you see three options for annotation. The name of the first option depends on the nature of the Finding. For instance, if the sensitive data found is a suspected API key, the option name changes to **Not an API key.** If it is a Personally Identifiable Information (PII), the option name changes to **Not a Personally Identifiable Information**, and so on.\n\nWhen you annotate a finding as **Not a credit card**, **Not an Address**, and so on, or annotate a finding as **Not a** **Violation,** the Finding is displayed as **False Positive** on the Finding column. If you annotate a Finding as **True Positive**, it is displayed as **True Positive** on the Finding column.\n\nIn the following image, a Violation has 25 **Very Likely** Findings and 28 **Possible** Findings. We annotate a **Very Likely** Finding as **True Positive** and a **Possible** Finding as **Not a Violation**. You can see that the values are reflected accordingly. Findings annotated as **True positive** are displayed in green color and Findings annotated as **False Positive** are displayed in grey color.\n\nThe Finding column also reflects the latest data on each finding. You can view that **Very Likely** Findings has reduced to 24. This is because one of them is annotated as **True Positive**. Similarly, **Likely** findings have reduced to 27. This is because one of them is annotated as **False Positive**.\n\nIf you accidentally annotate a Finding or annotate a Finding incorrectly, Nightfall provides remediation measures too. For accidentally annotated Findings, you can revert the annotation to return to the original Likelihood (Possible, Likely, Very Likely). For incorrectly annotated findings, you can modify the annotation.\n\n### Bulk Annotate[](https://help.nightfall.ai/dashboard/sdp_events#bulk-annotate)\n\nWhen the Apply to all identical findings toggle switch is enabled, the following events occur.\n\n- annotation is applied to all exact matches of the finding in all the existing Events.\n\n- annotation is applied to all exact matches of the findings in new Events.\n\nFurthermore, the Nightfall AI Smart Auto-Ignore feature performs the following tasks.\n\n- Events whose 100% of findings are annotated as false positives are automatically ignored.\n\n- When auto-ignored, an entry is added to the Event activity log for visibility\n\n- Auto-ignored Events are updated to \"Ignored\" status and moved to the \"Resolved\" tab for visibility, analysts' review, or audit.\n\n**Undo Auto-Ignore**\n\n- Undo is an action available on any Event that has been automatically ignored by Nightfall AI.\n\n- Taking the undo action reverts the status of the selected Event back to the pre-ignore state.\n\n**Undo Annotation and Disable Automatic Annotation**\n\n- The annotation for a specific token/finding can be undone by reverting the annotation (no change from current behavior).\n\n- When edited the \"apply to all...\" flag can be disabled. When disabled, future instances of the exact finding will not be automatically annotated.\n\n### View Event Details[](https://help.nightfall.ai/dashboard/sdp_events#view-event-details)\n\nYou can also find more details about the Event from the Event detail view. By default, only a few details are displayed on the Event detail view. You must click the **Expand details** button to view all the details of the Event. You can also view the chronological order of events (annotations applied, reverted, Event resolved, and so on) on the Event. The events start from the date on which the Event was created. You can also add comments on the Event.\n\n## Apply Actions on Events[](https://help.nightfall.ai/dashboard/sdp_events#apply-actions-on-events)\n\nYou can also apply various actions on the Events. The actions menu displays a list of actions that you can perform on an Event.\n\nTo learn more about Event actions, you can view the [Applying Actions on Events](https://help.nightfall.ai/dashboard/sdp_events/event_actions) document.\n\n## Bulk Actions[](https://help.nightfall.ai/dashboard/sdp_events#bulk-actions)\n\nWhen you wish to implement an action on multiple Events simultaneously, you can use the bulk action feature. To learn more about how to use this feature, refer to the [Applying Bulk Actions on Events](https://help.nightfall.ai/dashboard/sdp_events/bulk_actions) document.\n\n## Filtering Data[](https://help.nightfall.ai/dashboard/sdp_events#filtering-data)\n\nNightfall provides you with various filters to view Events specific to an integration, User, or Status. This ensures that you view data that is specific to your requirements. The various filters are described as follows.\n\n### Historic Data Filter[](https://help.nightfall.ai/dashboard/sdp_events#historic-data-filter)\n\nThis filter allows you to view historical data. You can choose to view data for the last 7, 30, 90, 120, or 180 days. You can also select a custom date range by entering the date in the MM/DD/YY format. When you apply a specific period, all the data on the Event management page is fetched from the selected period till the current date. For instance, assume that the current date is 1 December 2023. If you select the time filter as Last 7 days, the data is displayed from 25 Nov 2023 to 1 December 2023. Similarly, if you select the time filter as last 30 days, the data is displayed from November 2, 2023, to December 1, 2023. By default, this filter displays the data for the **Last 7 days**. You can click the Last 7 Days button to edit the date.\n\n### Miscellaneous Filters[](https://help.nightfall.ai/dashboard/sdp_events#miscellaneous-filters)\n\nThe miscellaneous filters allow you to apply filters on various Nightfall entities. The entities are described as follows.\n\n#### Detector[](https://help.nightfall.ai/dashboard/sdp_events#detector)\n\nThis filter facilitates you to view Event data specific to a Detecter.\n\n#### Integration[](https://help.nightfall.ai/dashboard/sdp_events#integration)\n\nThis filter facilitates you to view Event data specific to an Integration\n\n#### Likelihood[](https://help.nightfall.ai/dashboard/sdp_events#likelihood)\n\nThis filter facilitates you to view Event data specific to the Likelihood of sensitive data being detected.\n\n#### Status[](https://help.nightfall.ai/dashboard/sdp_events#status)\n\nThis filter facilitates you to view data specific to the status of Event\n\n#### User[](https://help.nightfall.ai/dashboard/sdp_events#user)\n\nThis filter facilitates you to view data specific to users who triggered Events.\n\nTo apply a filter:\n\n1. Click the **Filter** button.\n\n2. In the **When** drop-down menu select a filter.\n\n**Note**: The **Select an Option** drop-down menu is activated once you select a filter. The options in the drop-down menu vary for each filter selected.\n\n1. Select a filter value from the **Select an Option** drop-down menu. For some filters (like integration filter), you can select multiple values.\n\n2. (Optional) Click Add Filter to add multiple filters.\n\n3. (Optional) Repeat steps 2-3 to add multiple filters.\n\n4. Click **Apply**.\n\n- You can add multiple filters. Nightfall allows you to add a maximum of five filters.\n\n- When you add multiple filters, logical AND operation is applied between the filters. As a result, only the data that matches all the applied filters is displayed.\n\n- To remove the miscellaneous filters, click the **Reset** button.\n\n## Automated Event Duplication Management[](https://help.nightfall.ai/dashboard/sdp_events#automated-event-duplication-management)\n\nIf an Event is reported multiple times, Nightfall updates the Event to the new instance, instead of creating new Events. However, it maintains a trail of the Events to ensure no reporting is lost.\n\nFiltering duplicates reduces alerts. It also saves you the time spent on analyzing each finding.\n\nNightfall filters duplicate findings in multiple ways. New Events are not created when:\n\n- You remove a previously reported finding. The existing Event is updated. You can view the update in the Event metadata.\n\n- a duplicate of a finding previously reported is added. The existing Event is updated.\n\n**Note:** Filtering duplicate Events is currently available for Jira and Confluence.\n\nAn Event is auto-resolved:\n\n- When you remove all reported findings.\n\n- When you delete a resource (ex. ticket, comment, or page).\n\n### Examples[](https://help.nightfall.ai/dashboard/sdp_events#examples)\n\nConsider the case of JIRA integration. If Nightfall detects a data Event in either your JIRA ticket description or JIRA ticket comments an Event is created. This Event has a single finding which was detected in the JIRA ticket. You can view the history of this Event as highlighted in the following image.\n\nNow, consider that you add more sensitive data in the ticket. When Nightfall scans the ticket again the following events occur\n\n- A new Event is created with a single finding. This finding refers to the new sensitive data detected during the second scan.\n\n- The previous Event record is updated. It now has two findings (even more than two if multiple findings are detected on the same ticket).\n\nYou can now find the duplicate ticket information in the ticket history section.\n\n## Searching Events[](https://help.nightfall.ai/dashboard/sdp_events#searching-events)\n\nThe search bar in Events allows you to search Events in two ways as described in the following sections.\n\n### Keyword Based Search[](https://help.nightfall.ai/dashboard/sdp_events#keyword-based-search)\n\nYou can search for Events using a keyword. The search returns all Events that contain all the keywords submitted.\n\n- For instance, searching for a Credit Card returns all Events that contain Credit AND Card in any of the indexed Event properties.\n\n- You can search for an exact phrase. Use double quotes around the phrase (ex.\"Credit Card Number\").\n\n- Use the AND to search for Credit Card Number Events by John Doe (ex. \"Credit Card Number\" AND \"John Doe\")\n\n- Use the Not operator to exclude Events from your search query (ex.\"Credit Card Number\" AND \"John Doe\" NOT Confluence)\n\n### Operator Based Search[](https://help.nightfall.ai/dashboard/sdp_events#operator-based-search)\n\nNightfall provides you with search operators to search for the exact Event required. A search operator is an entity that you can use as a filtering factor. For instance, **Detector\\_name** is an operator that you can use to view Events specific to a detector. Similarly, Confidence is an operator that you can use to filter Events based on confidence levels (Very Likely, Likely, Possible).\n\nYou can use an operator as shown in the following image.\n\nYou can see that when you search for Events with **Likely** Confidence, the search returns all the Events in which at least one instance of **Likely** Finding. Similarly, when you search for **Possible** Confidence, the search returns all the Events that have at least one instance of **Possible** finding.\n\nNightfall also displays the last five search terms for each user. These values are stored in the user's browser cache.\n\nNightfall provides two types of search operators.\n\n- **General Search Operators**: These operators are based on Nightfall entities. These can be confidence level, Nightfall actions, Event status, and so on. To view the complete list of general search operators, see [General Operators](https://help.nightfall.ai/dashboard/sdp_events/filter_operators#general-operators).\n\n- **Integration Search Operators**: These are the search operators based on specific integrations. These operators vary for each integration. To view the complete list of integration-based search operators, see [Integration Operators](https://help.nightfall.ai/dashboard/sdp_events/filter_operators#integration-operators).\n\nYou can use multiple operators to refine your search. When you use multiple operators, Nightfall applies the AND logic between the operators. So, if you wish to view all the active Events in the Zendesk integration, you can accomplish it as shown in the following image.\n\nYou can also use a single operator to filter multiple values. For instance, to view all the Events of Zendesk and Salesforce integrations, you can use the search as shown below.\n\n**Note**\n\n`**:**` is used as an operator delimiter for search as so `**:**` cannot be used as a search string. If you wish to search a text with `**:**` colon in it, replace it with `?` or `*` and submit the query, else the prefix to colon would be considered an operator.\n\n### Special Characters[](https://help.nightfall.ai/dashboard/sdp_events#special-characters)\n\nWhile `**:**` is a special character that is an operator seperator for search actions, there are other special characters that cannot be used directly in the search bar. The complete list of special characters that cannot be searched directly, are as follows.\n\nSo, if your policy name contains reserved characters like && {}, you cannot use these characters directly in the search bar. You must make some changes to your search query before using them. To search any of the above special characters, you must perform any one of the following tasks:\n\n- Use an escape character \\ before the special character (_this will work with all special characters but not with_ `**:**` )\n\n- Replace the special character with the wildcard (\\*).\n\n- Replace the special character with a question mark (?).\n\nSome of the examples are as follows.\n\n- To search the policy name `Google Drive! Critical_Document`_,_ you must use one of the following search terms.\n\n- To search the policy name `H&&M,` you must use one of the following search terms.\n\n- To search the policy name `Google !`, you must use one of the following search terms.\n\nNightfall allows you to share and download the Event data. The Share option creates a link to the current view with all the filters applied. When you click this link,the Events page opens with all the filters applied.\n\nThe Export option, creates a CSV file with all the event data. The CSV file is mailed to the logged in user's Email ID. The CSV file contains all the filters which were applied before initiating the download process. Click **Export to CSV** to start the export process.\n\nOnce you click **Export to CSV**, a pop up window is displayed. You can select one of the following options and click **Send Download Link.**\n\n- **Redacted Findings**: In this report, all the findings of an Event are grouped in a single row. The report is available only for 24 hours, once delivered. You cannot access the report after 24 hours.\n\n- **Un-redacted Findings**: Users with [System administrator](https://help.nightfall.ai/sensitive-data-protection/nightfall_settings/role_based_access_control#roles-and-permissions) role can view un-redacted findings by selecting this option. Only those findings that are not older than 30 days can be viewed in un-redacted format. Findings older than 30 days are redacted. In this report, each finding is available in a separate row. The report is available only for 24 hours, once delivered. You cannot access the report after 24 hours.\n\nYou receive an Email from Nightfall with the subject line **Nightfall - Report .** You must click the **Download Report** button in the email. The link to the report expires 7 days after you receive the email.\n\nThe CSV table contains the same columns as in case of the Event list view. The file looks as follows.\n","2026-08-04T17:12:53.731Z","2026-08-04T18:29:07.459Z","ff1f0067-9755-4815-8e6d-50026a5e45a7",[],[],[],"Customer Referral Program | Nightfall Documentation","customer-referral-program-nightfall-documentation","https://help.nightfall.ai/nightfall_settings/customer-referral-program","Share your love for Nightfall and earn rewards. You'll receive $1000 for each successful referral.\n\n**How It Works:**\n\nHave a friend or colleague who could benefit from modern, all-in-one data loss prevention? Here’s how you can both earn rewards:\n\n1. **Share the referral link**\n\nSpread the word by sharing our referral page via email or social media:\n\n[**https://www.nightfall.ai/referral**](https://www.nightfall.ai/referral)\n\n1. **Submit details**\n\nMake sure your referral includes your name, email, and company when they fill out the referral form.\n\n1. **Earn rewards**\n\nWhen your referral becomes a Nightfall customer, you’ll get a $1000 Visa gift card, and they’ll receive 10% off their first year with Nightfall.\n","2026-08-04T17:12:51.371Z","2026-08-04T18:28:53.516Z","a9dd3df5-9139-49f8-8137-ddc74ada1ef7",[],[],[],"Custom Branding | Nightfall Documentation","custom-branding-nightfall-documentation","https://help.nightfall.ai/nightfall_settings/custom-branding","## Overview[](https://help.nightfall.ai/nightfall_settings/custom-branding#overview)\n\nAdd your organization's logo to all Nightfall email notifications by using the custom branding feature. After you upload your logo, it appears on:\n\n- Admin alert emails across all sensitive data protection, posture management and exfiltration prevention\n\n- End-user email notification about sensitive data exposure, posture or exfiltration prevention\n\n- Encrypted emails sent to recipients either via on-demand or automated encryption\n\n## Important notes[](https://help.nightfall.ai/nightfall_settings/custom-branding#important-notes)\n\n- Once you upload a logo, custom branding is automatically enabled\n\n- To disable custom branding, delete your uploaded logo\n\n- When no custom logo is present, Nightfall's default logo appears on all emails\n\n## Add your organization's logo[](https://help.nightfall.ai/nightfall_settings/custom-branding#add-your-organizations-logo)\n\n1. Select **Settings**\n\n2. Select the **Custom Branding** tab\n\n3. In the Custom Logo dialog box, select **Upload a logo**.\n\n4. Select your organization's logo file.\n\n5. Click **Save**.\n\nTo use the custom branding feature, you must upload your organization logo. Once you upload the logo, all the email notifications are delivered with the logo. You cannot disable this feature once you upload a logo. To disable this feature, you must delete the logo. Once you delete a logo, the Nightfall logo is appended to all the communication emails.\n","2026-08-04T17:12:50.838Z","2026-08-04T18:28:53.441Z","58ef25b6-49d5-45f7-a994-c2af4c9ac234",[],[],[],"Creating Policies | Nightfall Documentation","creating-policies-nightfall-documentation","https://help.nightfall.ai/detection_platform/policies","This document applies only to the Nightfall SaaS application customer. If you are a Nightfall Firewall for AI customer, refer to [this document](https://help.nightfall.ai/nightfall-developer-platform/getting-started-with-developer-platform/creating-policies).\n\n## Background Knowledge[](https://help.nightfall.ai/detection_platform/policies#background-knowledge)\n\nAn Integration in Nightfall refers to a SaaS application in which your organization's data resides. This SaaS application can be Google Drive, JIRA, Notion, GitHub, and so on. The sensitive data residing in these applications is highly prone to data leakage, accidentally by your employees.\n\nYou can connect your SaaS applications to Nightfall by adding them as integrations. Once a SaaS application is added as an integration, Nightfall continuously scans it to check if there is any sensitive data leakage.\n\n## Understanding Policies[](https://help.nightfall.ai/detection_platform/policies#understanding-policies)\n\nA Policy in Nightfall allows you to define a specific part of your integration or the entire integration to be monitored for sensitive data leakage, by Nightfall. Apart from monitoring your environment, Policies in Nightfall also allow you to configure alerts and automatic actions if Nightfall discovers sensitive information in the integration being scanned.\n\nOnce you create a policy, if there is any instance of data leakage, Nightfall sends notifications to the audience configured by you in the policy. It also takes automated actions, configured by you in the policy. If you have disabled automated actions and no action is taken by you, Nightfall also sends reminders, as per the frequency set by you in the policy. All these actions are done automatically by Nightfall, as per the policy settings, configured by you.\n\nA Policy in Nightfall is always associated with integration. You can create multiple policies on a single integration. Before creating a policy for an integration, you must first ensure that the integration is added to Nightfall.\n\n## Policy Stages[](https://help.nightfall.ai/detection_platform/policies#policy-stages)\n\nA Nightfall Policy has multiple stages. You can configure various settings like adding specific sections of integration to be scanned, configuring alert notifications, end-user actions, and so on. The various stages of a policy are described in the following document.\n\n[Selecting Integration](https://help.nightfall.ai/detection_platform/policies/integration)\n\n[Scope of the Policy](https://help.nightfall.ai/detection_platform/policies/scope)\n\n[Detection Rules](https://help.nightfall.ai/detection_platform/policies/detection_rules)\n\n[Advanced Settings](https://help.nightfall.ai/detection_platform/policies/advanced_settings)\n\n[Name and Risk Score](https://help.nightfall.ai/detection_platform/policies/risk_score)\n","2026-08-04T17:12:51.965Z","2026-08-04T18:29:06.517Z","975b933e-32e5-49da-9745-b244de305ae2",[],[],[],"Creating Custom Detectors | Nightfall Documentation","creating-custom-detectors-nightfall-documentation","https://help.nightfall.ai/detection_platform/custom_detectors","Nightfall allows you to create custom detectors that match your organization's requirements. If none of the existing Nightfall detectors match your requirements, you can use this option to create a custom detector.\n\nNightfall provides you with five types of custom detectors.\n\n- **Dictionary**: This Detector allows you to upload a text file. The text file must have a specific token which is sensitive data for your organization. The Detector looks for this token in all the data and if a match is found, it flags it as sensitive data found.\n\n- **File Type**: This Detector allows you to select a [MIME](https://www.geeksforgeeks.org/multipurpose-internet-mail-extension-mime-protocol/) (Multipurpose Internet mail extension). (roughly speaking, every file on the Internet is recognized by its format which is called MIME). The Detector scans all your data to check if it has a file with the selected MIME type.\n\n- **File Fingerprint**: This Detector accepts a file as input. You can add all the content that you feel is sensitive to your organization. The detector uses this file as the base and scans your data to check if any matching content is present. If found, it flags it as sensitive data.\n\n- **Regular Expression**: This Detector allows you to define regular expressions matching the [RE2 syntax](https://github.com/google/re2/wiki/Syntax/). The Detector scans all your data to find any content that matches the regular expression. If found, it flags it as sensitive data.\n\n- _**NEW**_ **- Prompt-Based Entity Detector**: This Detector allows you to define sensitive entities using natural language. Instead of relying on fixed formats or patterns, the Detector uses semantic understanding to identify custom or proprietary sensitive entities based on your description.\n\n- _**NEW**_ **- Prompt-Based File Classifier**: This Detector allows you to classify entire documents based on their intent and meaning. You describe the type of document you want to detect, and the Detector evaluates the full content of the file to determine whether it matches.\n\n- **Extend a Nightfall Detector**: This Detector type allows you to customize an out-of-the-box Detector by defining Context Rules and Token rules.\n\n#### Prompt-Based Detectors[](https://help.nightfall.ai/detection_platform/custom_detectors#prompt-based-detectors)\n\nPrompt-based detectors use large language models (LLMs) to identify sensitive data based on meaning and context, rather than fixed patterns or schemas. These detectors are especially useful for identifying proprietary, evolving, or business-specific data that is difficult to capture using traditional detectors.\n\nPrompt-based detectors are best suited for:\n\n- Custom or organization-specific sensitive data\n\n- Documents where sensitivity is determined by intent, not keywords\n\n- Rapid iteration without writing regex or training custom models\n\nApart from the above custom Detectors, you can also use the **Request a new detector** option to request an entirely new custom Detector created by Nightfall. **Prompt-based detectors** provide a faster alternative for defining custom detection logic without engineering effort.\n\nTo view only custom detectors created by you, click the CUSTOM filter in the left pane.\n\nTo learn more about how to create each of the custom detectors, you can refer to the following documents.\n","2026-08-04T17:12:51.110Z","2026-08-04T18:29:06.085Z","91c4eb0b-6036-484a-a79e-ced9df6c18cb",[],[],[],"Create MX Record | Nightfall Documentation","create-mx-record-nightfall-documentation","https://help.nightfall.ai/microsoft-exchange/getting_started/installing-microsoft-exchange/create-mx-record","This process helps Nightfall identify your Exchange online account in Microsoft. This process is executed in the Nightfall console.\n\n### Prerequisites[](https://help.nightfall.ai/microsoft-exchange/getting_started/installing-microsoft-exchange/create-mx-record#prerequisites)\n\nYou must execute the following steps to obtain domain name and MX record.\n\n1. In the Microsoft 365 Admin portal, expand **Settings** and select **Domains**.\n\n2. Note the Domain name of your organization.\n\n3. Click the domain name and select the **DNS records** tab.\n\n4. Navigate to the **Microsoft Exchange** section and click **MX**.\n\n5. Copy the URL under the **Points to address or Value** column. This is the MX record.\n\n## Installation Steps[](https://help.nightfall.ai/microsoft-exchange/getting_started/installing-microsoft-exchange/create-mx-record#installation-steps)\n\n1. Open the **Nightfall app** and navigate to **Integrations**.\n\n2. Click **Manage** for the **Exchange Online** widget.\n\n3. Click **Edit MX** record for **Exchange Online**.\n\n4. In the **Domain name** field enter the domain name obtained in the previous section.\n\n5. In the **MX Record Submission** field, enter the MX record value obtained in the previous section.\n\n6. Click **Add**.\n","2026-08-04T17:16:31.870Z","2026-08-04T17:16:31.895Z","77f79009-73d2-47fb-ae75-5752caf94e92",[],[],[],"Create Detection Rules | Nightfall Documentation","create-detection-rules-nightfall-documentation","https://help.nightfall.ai/detection_platform/create_detection_rules","As described in the [Nightfall Detection Platform](https://help.nightfall.ai/detection_platform/overview) once you have finalised the the Detectors to be used or created custom detectors which leverage your organization's sensitive data security requirements, you must add the detectors to a detection rule and then add the detection rule to a policy. You cannot use detectors directly. Detectors become useful only when you add them to a Detection rule and then add the detection rule to a policy.\n\nYou can add multiple detectors to a single detection rule. Nightfall does not restrict you on the type of detector that can be added to a detection rule. You can add both, a custom detector and a Nightfall detector to the same detection rule.\n\nYou can create multiple detection rules to detect different types of sensitive data. For example, you can add the Password detector to a Detection rule and use it to detect password leaks. You can add the API key detector to another detection rule and use it for detecting API key leaks.\n\nOnce you add all the required detectors to the detection rule, Nightfall allows you to test the detection rule in the Nightfall Playground. You can use the Nightfall playground only for testing if the detection rule works as expected. Once you confirm that the detection rule works as expected, you must add the detection rule to policy to leverage your data security requirements. Conversely, you can also have a single detection rule in which you add both Password and API key detectors.\n\nYou can access the Detection rules page by clicking **Detection** from the left pane and then clicking **Detection Rules**. To create a new Detection rule, you must click the **+ New Detection Rule** button the top right corner.\n\nIf you wish to get guidelines from Nightfall on what detectors must be included in your detection rules, refer to the [Detection Rules](https://help.nightfall.ai/nightfall_policy_templates/detection_rules) document.\n\n## Adding Detectors to Detection Rule[](https://help.nightfall.ai/detection_platform/create_detection_rules#adding-detectors-to-detection-rule)\n\nYou can add a Detector to the Detection rule by executing the following steps.\n\n1. Click the **+ New Detection Rule** button the top right corner.\n\n2. Enter a name for the detection rule in the **Name** field.\n\n3. (Optional) Enter a description for the detection rule in the **Description** field.\n\n4. Click **+ Add Detectors** to add detectors to the detection rule.\n\n5. Select the check box for the detectors that you wish to add to the detection rule. You can use the filters to view only the Nightfall detectors or the custom detectors or the search bar to search detectors.\n\n6. Click **Add**.\n\nYou can see that the selected detectors are added to the detection rule. In the following image two detectors have been added to the Detection rule.\n\n## Detection Rule Settings[](https://help.nightfall.ai/detection_platform/create_detection_rules#detection-rule-settings)\n\nOnce you add the required detectors to the detection rules, you can se that there are three columns; **Scope**, **Minimum Confidence**, and **Minimum # of Findings**. These settings define the weightage of the detector in the detection rule. You must configure these settings for each detector.\n\nThese settings are explained in the following sub-sections.\n\n### Scope[](https://help.nightfall.ai/detection_platform/create_detection_rules#scope)\n\nThe Scope setting allows you to define which part of the data the detector must scan. You can configure this setting to scan either the name of the file, the contents of the file or both.\n\nIf you select the **Content** option, this detector only scans the content of the files and not the name of the file, and vice versa, if you select **File Name**. However, if you select **Both**, the detector scans the file name as well the contents of the file.\n\nFor example, if the API key detector has to scan a Google Drive file and if you select, **File Name**, then the detector only scans the name of the file to check if the name has any API key. Similarly, if you select **Content**, then the detector only scans the content of the file and not the name. If you select **Both**, then the detector scans both; the name and the contents of the file.\n\n**Important**\n\nIf you wish to scan content that is not part of any file, you must either select the **Content** or **Both** option.\n\nFor example, if you wish to scan direct messages or group messages from Slack or MS Teams, these messages are not part of any files. In such cases, if you select the **File Name** option, the detector does not detect any violation because it considers direct messages as Content not part of any file. Hence to scan such types of content you must select either **Content** or **Both** options.\n\n### Minimum Confidence[](https://help.nightfall.ai/detection_platform/create_detection_rules#minimum-confidence)\n\nThe minimum confidence setting defines the probability of a detector's findings being actual violations. Nightfall provides you with three Minimum Confidence settings; Possible, Likely, and Very Likely.\n\nThe **Possible** option indicates that there is a **40-60%** chance of the Detector's finding being an actual case of data leak, Similarly, the **Likely** option indicates that there is a **61-80%** chance of the Detector's finding being an actual case of data leak. The **Very Likely** option indicates that there is a **81-100%** chance of the Detector's finding being an actual case of data leak.\n\nYou can set the Minimum Confidence setting for each detector. When the detector detects any data leak, it is logged in the [Data Detection and Response Events](https://help.nightfall.ai/dashboard/sdp_events) page with the Minimum Confidence setting configured here.\n\n### Minimum Number of Findings[](https://help.nightfall.ai/detection_platform/create_detection_rules#minimum-number-of-findings)\n\nThis setting defines the minimum number of data leak cases that a detector must encounter for it to be considered as a Violation by the Detection rule. You must configure this setting for each detector. For example, if you set this setting to 10, the detection rule does not consider the first 9 occurences of data leak encountered by the detector. Detection engine starts considering the 10th and all subsequent cases of data leak to be actual case of violations.\n\n## Applying Logical Operators Between Detectors[](https://help.nightfall.ai/detection_platform/create_detection_rules#applying-logical-operators-between-detectors)\n\nIf a detection rule has a single detector and if that detector detects a data leak, the detection rule is triggered and it is logged as a Finding.\n\nHowever, when you have multiple detectors in detection rule, you can choose to trigger the detection rule when any of the detector detects a data leak or when all the detectors detect a data leak.\n\nAs you can see in the above image, you can choose the flag a Finding of the detection rule either when any single detector detects a data leak or when all the detectors of the detection rule detect a data leak.\n\n## Understanding When the Detection Rule Triggers[](https://help.nightfall.ai/detection_platform/create_detection_rules#understanding-when-the-detection-rule-triggers)\n\nThe above image has two detectors. The following statements hold good.\n\n- The Scope of both the detectors is set to scan the file content and file name.\n\n- When any of these detectors detect a data leak, it is logged as a Finding in the Violations page and tagged as Very Likely.\n\n- The minimum number of findings for each detector is 1. So even if there is a single case of a data leak, a detector rule considers it as a finding.\n\n- The detection rule is triggered even if a single detector detects a data leak.\n\n## Testing Detection Rules in Nightfall Playground[](https://help.nightfall.ai/detection_platform/create_detection_rules#testing-detection-rules-in-nightfall-playground)\n\nOnce you create the detection rule, it is highly recommended that you test the rule to ensure that it returns the expected results, when added to policies. Nightfall provides you with a Playground to test the detection rules.\n\n### Prerequisites to use Nightfall Playground[](https://help.nightfall.ai/detection_platform/create_detection_rules#prerequisites-to-use-nightfall-playground)\n\n- You must have an API key to use the Nightfall Playground. You can [refer to this document](https://help.nightfall.ai/nightfall-developer-platform/getting-started-with-developer-platform/creating-api-key) to learn about how to create an API key.\n\n- You must have some sample data to test the Detection rule. This [Nightfall document](https://help.nightfall.ai/nightfall-ai/nightfall-detection-and-policy-templates/nightfall-sample-data-sets) has various types of sample data sets that you can use.\n\n### Capturing Detection Rule UUID[](https://help.nightfall.ai/detection_platform/create_detection_rules#capturing-detection-rule-uuid)\n\nEach Detection rule in Nightfall has a UUID. This is a unique ID assigned to each detector when it is created. You cannot edit the UUID of any detector. You must capture this UUID to use it in Playground to test the detection rule.\n\nTo capture Detection rule UUID:\n\n1. Navigate to Detection rules.\n\n2. Click the detection rule whose UUID has to be captured.\n\n3. Click the UUID to copy it.\n\n### Using the Nightfall Playground[](https://help.nightfall.ai/detection_platform/create_detection_rules#using-the-nightfall-playground)\n\nTo use the Nightfall playground:\n\n2. Use either the **I'm Scanning Text** or **I'm Scanning Files** tab based on whether you wish to scan text or file.\n\n3. Replace the existing sample data with your sample data in **Step 1: Payload.**\n\n4. Skip **Step 2: Pick Detection rule**.\n\n5. Expand **Advanced Detection Settings (Optional)**\n\n6. Paste the Nightfall API key in the **Nightfall API Key** field.\n\n7. Paste the Detection rule UUID in the **Detection Rules** field.\n\n8. Click **Start Scan.**\n\nIf sensitive data is found in the sample data, the Findings section looks as shown in the following image.\n\n1. Paste the file URL or upload the file in **Step 1: Files to scan**.\n\n2. Enter the Email to which the scan results must be sent in the **Step 2: Email** field.\n\n3. Skip **Step 2: Pick Detection rule**.\n\n4. Expand **Advanced Detection Settings (Optional)**\n\n5. Paste the Nightfall API key in the **Nightfall API Key** field.\n\n6. Paste the Detection rule UUID in the **Detection Rules** field.\n\n7. Click **Start Scan.**\n\n### [](https://help.nightfall.ai/detection_platform/create_detection_rules#undefined-1)\n","2026-08-04T17:12:51.493Z","2026-08-04T18:29:06.171Z","c67b3a90-17c1-45fc-9381-171cf853b907",[],[],[],"Contact Us | Developer APIs | Nightfall Documentation","contact-us-developer-apis-nightfall-documentation","https://help.nightfall.ai/developer-api/contact_nightfall_team","# Contact Us | Developer APIs\n\n## Schedule a Demo[](https://help.nightfall.ai/developer-api/contact_nightfall_team#schedule-a-demo)\n\nYou can schedule a demo or a meeting with our sales/solutions engineering team directly via Calendly [here](https://calendly.com/nightfallai/30min). If you don't see a suitable time, please email us at .\n\n## Email Us[](https://help.nightfall.ai/developer-api/contact_nightfall_team#email-us)\n\nFor support inquiries, please email us at .\n\nFor sales inquiries, please email us at .\n","2026-08-04T17:13:02.567Z","2026-08-04T17:13:02.592Z","1eef04a9-d47a-41de-ac55-7af783dc5d3b",[],[],[],"Contact Nightfall | Nightfall Documentation","contact-nightfall-nightfall-documentation","https://help.nightfall.ai/contact-us","## Schedule a Demo[](https://help.nightfall.ai/contact-us#schedule-a-demo)\n\nYou can schedule a demo or a meeting with our sales/solutions engineering team directly via Calendly [here](https://calendly.com/nightfallai/30min). If you don't see a suitable time, please email us at .\n\n## Email Us[](https://help.nightfall.ai/contact-us#email-us)\n\nFor support inquiries, please email us at .\n\nFor sales inquiries, please email us at .\n","2026-08-04T17:12:29.909Z","2026-08-04T18:29:09.078Z","4ec9295a-dc85-495c-8ce8-56527d8a1195",[],[],[],"Console | Nightfall AI Knowledge Base","console-nightfall-ai-knowledge-base","https://kb.nightfall.ai/collections/3558083637-console","[![Nightfall AI Knowledge Base](/api/knowledge-base/images/d508ed4c-3d82-4054-8dd1-858f868b3791)![Nightfall AI Knowledge Base](/api/knowledge-base/images/5d4d526d-807a-4130-99df-be097b556c4e)](https://kb.nightfall.ai/)\n\n\\[\n\nSSO\n\n1 article\n\n]\\()\n","2026-08-03T17:22:48.635Z","2026-08-04T19:49:19.801Z","9a6bc8e0-122c-457d-9d23-397589bdb364",[],[],[],"Confluence App Selection | Nightfall Documentation","confluence-app-selection-nightfall-documentation","https://help.nightfall.ai/confluence/policies/integration","In this stage, you select the Integration for which the policy is created. In this case, the Confluence integration must be selected.\n\n1. Click **Policies** from the left menu.\n\n2. Click **+ New Policy**.\n\n3. Select **Sensitive Data**.\n\n4. Select the **Confluence** integration.\n","2026-08-04T17:15:30.137Z","2026-08-04T17:15:30.162Z","b3cc9b17-b68f-47ba-8da9-aeb50134fcfd",[],[],[],"Configuring Policies for the Slack Enterprise Edition | Nightfall Documentation","configuring-policies-for-the-slack-enterprise-edition-nightfall-documentation","https://help.nightfall.ai/slack/enterprise_policy","# Configuring Policies for the Slack Enterprise Edition\n\nDLP policies are a set of rules that include specific conditions, actions, and exceptions that monitor and filter data. DLP policies help you to monitor and remediate the flow of sensitive data within your organization. Depending on your Nightfall policy configuration, you can set up policies to monitor data that is sent through some or all applications within your organization. You can configure policies and choose to not apply them all the time.\n\nBefore you define a policy, or a set of policies, you must define the objectives of each policy, which can then be fulfilled when you configure the policy. Here are a few important questions to ask before configuring your policies:\n\n• What data do you plan to monitor?\n\n• Where within the organization do you want to monitor?\n\n• What should be the scope of each policy?\n\n• What conditions must apply for the policy to match?\n\n• What exceptions/exclusions can be allowed?\n\n• What remediation actions should the policy take?\n\nYou can now set up policies to determine which Slack channels are monitored (and which are excluded) for violations and what actions Nightfall must take. Policies determine the content that will be scanned by Nightfall, and workflows that are followed to manage violations.\n\nPolicies for Slack integration allow you to define configurations specific to Slack, such as how to handle messages for particular channels or use automated actions such as Quarantine.\n\nCreating a Nightfall policy involves the following tasks:\n\n1. Create Policies\n\n2. Define the policy scope and exclusions\n\n3. Configure Detection Rule\n\n4. Configure Automated Actions\n\n**Note:** Instructions to configure policies differ for Slack Pro and Slack Enterprise options. Refer to the Slack tier that you are using.\n","2026-08-04T17:12:32.472Z","2026-08-04T18:28:53.648Z","f4255d8f-5428-46fa-a179-6c58280979ae",[],[],[],"Configuring Policies for Slack Pro and the Slack Business+ Editions | Nightfall Documentation","configuring-policies-for-slack-pro-and-the-slack-business-editions-nightfall-documentation","https://help.nightfall.ai/slack/slack_pro_policy","# Configuring Policies for Slack Pro and the Slack Business+ Editions\n\nDLP policies are a set of rules that include specific conditions, actions, and exceptions that monitor and filter data. DLP policies help you to monitor and remediate the flow of sensitive data within your organization. Depending on your Nightfall policy configuration, you can set up policies to monitor data that is sent through some or all applications within your organization. You can configure policies and choose to not apply them all the time.\n\nBefore you define a policy, or a set of policies, you must define the objectives of each policy, which can then be fulfilled when you configure the policy. Here are a few important questions to ask before configuring your policies:\n\n• What data do you plan to monitor?\n\n• Where within the organization do you want to monitor?\n\n• What should be the scope of each policy?\n\n• What conditions must apply for the policy to match?\n\n• What exceptions/exclusions can be allowed?\n\n• What remediation actions should the policy take?\n\nYou can now set up policies to determine which Slack channels are monitored (and which are excluded) for violations and what actions Nightfall must take. Policies determine the content that will be scanned by Nightfall, and workflows that are followed to manage violations.\n\nPolicies for Slack integration allow you to define configurations specific to Slack, such as how to handle messages for particular channels or use automated actions such as Quarantine.\n\nCreating a Nightfall policy involves the following tasks:\n\n1. Create Policies\n\n2. Define the policy scope and exclusions\n\n3. Configure Detection Rule\n\n4. Configure Automated Actions\n\n**Note:** Instructions to configure policies differ for Slack Pro and Slack Enterprise options. Refer to the Slack tier that you are using.\n","2026-08-04T17:12:32.320Z","2026-08-04T18:28:53.581Z","ad4ee658-b372-419c-ab12-35d07b0e630f",[],[],[],"Configuring Policies for Confluence | Nightfall Documentation","configuring-policies-for-confluence-nightfall-documentation","https://help.nightfall.ai/confluence/policies","DLP policies are a set of rules that include specific conditions, actions, and exceptions that monitor and filter data. DLP policies also enable you to remediate any leakage of sensitive information from within your organization.\n\n- You can set up policies to scan data that is sent through some or all applications within your organization.\n\n- You can configure policies and choose to not apply them all the time.\n\nBefore you define a policy, or a set of policies, we recommend that you define the objectives of each policy, which can then be fulfilled when you configure the policy.\n\nHere are a few important questions to ask before configuring your policies:\n\n- What data do you plan to monitor?\n\n- Where within the organization do you want to monitor?\n\n- What should be the scope of each policy?\n\n- What conditions must apply for the policy to match?\n\n- What exceptions/exclusions can be allowed?\n\n- What remediation actions should the policy take?\n\nYou can now configure policies on the Confluence integration to determine which workspaces and pages must be monitored, and which ones excluded. You can also automate the remediation actions that you want Nightfall to perform on a policy violation.\n\nConfiguring DLP policies on Confluence involves the following steps:\n","2026-08-04T17:12:34.969Z","2026-08-04T18:28:55.429Z","53b7f644-656f-42d5-8d16-f994850bf828",[],[],[],"Configuring Alerts for Jira | Nightfall Documentation","configuring-alerts-for-jira-nightfall-documentation","https://help.nightfall.ai/jira/installation/integration_alerts","The Nightfall for Jira integration supports the configuration of alerts at the policy level and the integration level. Alerts can be sent in Jira to the following alert destinations.\n\nWhen you configure alert settings at the integration level, the alert settings apply to all the policies, created for the JIRA integration. However, when you configure alert settings specifically for a policy, which is created in the JIRA integration, the alert settings are applicable only for that specific policy.\n\nThis document explains how to configure alerts at the integration level.\n\n## Prerequisites[](https://help.nightfall.ai/jira/installation/integration_alerts#prerequisites)\n\n- To use Slack as an alert platform, you must first perform the required Slack configurations. You can refer to [this document](https://help.nightfall.ai/nightfall-ai/detection/setting-up-slack-as-an-alert-channel-in-nightfall) to learn more about how to configure Slack as an Alert platform.\n\n- To use Webhook as an alert platform, you must first perform the required Webhook configurations. You can refer to [this document](https://help.nightfall.ai/nightfall-ai/operationalizing-dlp/integrating-with-security-tools/integrating-with-siem#configuring-outgoing-webhooks) [](https://help.nightfall.ai/nightfall-ai/operationalizing-dlp/integrating-with-security-tools/integrating-with-siem#configuring-outgoing-webhooks)to learn more about how to configure Webhook as an Alert platform.\n\n- To use JIRA as an alert platform, you must have the DLP for the JIRA app installed from the [Atlassian Marketplace](https://marketplace.atlassian.com/apps/1226823/dlp-for-jira-nightfall-ai?tab=overview\\&hosting=cloud). You can read more about the DLP for JIRA integration [here](https://help.nightfall.ai/nightfall-ai/nightfall-for-jira/getting-started/installing-nightfall-for-jira).\n\n## Configure Alerts at the Integration Level[](https://help.nightfall.ai/jira/installation/integration_alerts#configure-alerts-at-the-integration-level)\n\nYou can configure alerts at the integration level once you have installed the Nightfall for JIRA DLP integration.\n\nTo configure alerts at the integration level:\n\n1. Navigate to the JIRA integration.\n\n2. Scroll down to the JIRA section.\n\n3. You can configure one or multiple alert channels.\n\n### Configuring Slack as an Alert Channel[](https://help.nightfall.ai/jira/installation/integration_alerts#configuring-slack-as-an-alert-channel)\n\n1. To configure Slack as an alert channel, click **+ Slack channel**.\n\n2. In the **Slack alert channel** field, enter the name of the Slack channel in which you wish to receive the alerts.\n\n3. Click **Save**.\n\nA confirmation pop-up box is displayed to confirm if the Slack channel (entered in the second step) must be used only for JIRA DLP integration or all the Nightfall integrations.\n\n1. Select **No, only integration level** to use the Slack channel only for JIRA DLP, or select **Yes, please** to use the selected Slack channel for all the Nightfall integrations.\n\n### Configuring Email as an Alert Channel[](https://help.nightfall.ai/jira/installation/integration_alerts#configuring-email-as-an-alert-channel)\n\n1. Click **+ Email**.\n\n2. Enter the Email ID of the recipient who should receive the notifications\\*\\*.\\*\\*\n\n3. Click **Save.**\n\nA confirmation pop-up box is displayed to confirm if the Email ID (entered in the second step) must be used only for JIRA DLP integration or all the Nightfall integrations.\n\n1. Select **No, only integration level** to use the Slack channel only for JIRA DLP, or select **Yes, please** to use the selected Slack channel for all the Nightfall integrations.\n\n### Configuring Webhook as an Alert Channel[](https://help.nightfall.ai/jira/installation/integration_alerts#configuring-webhook-as-an-alert-channel)\n\n1. Click **+ Webhook**.\n\n2. Enter the Webhook URL.\n\n3. Click **Test**. If the test result is not successful, check the Webhook URL.\n\n4. (Optional) Click **Add Header** to add headers.\n\n5. Click **Save**.\n\nWhen you configure alerts to a Webhook, Nightfall AI sends occasional posts to:\n\n- To validate that the Webhook is properly configured before the policy is saved.\n\n- Periodically thereafter to ensure that the Webhook is still valid.\n\nThe response to the test Webhooks is `200` status code if successful.\n\nAn example of Webhook request is as follows.\n\n```\n{\n \"service\": \"nightfall\",\n \"test\": true,\n \"timestamp\": \"2024-03-07T23:18:39Z\"\n}\n```\n\nThis is part of alert event consumption and can be ignored.\n\n### **Configuring Jira as an Alert Channel**[](https://help.nightfall.ai/jira/installation/integration_alerts#configuring-jira-as-an-alert-channel)\n\n1. Click **+ Jira Ticket.**\n\n2. Select a JIRA project from the **Jira Project** drop-down menu.\n\n3. Select an issue type from the **Issue Type** drop-down menu.\n\n4. (Optional) Add comments to be added in the JIRA ticket.\n\n5. Click **Save changes**.\n\nA confirmation pop-up box is displayed to confirm if the JIRA settings configured for the JIRA DLP integration must be applied to all the other Nightfall integrations too.\n\n1. Select **No, only integration level** to use the configurations only for JIRA DLP, or select **Yes, please** to use the selected JIRA configurations for all the Nightfall integrations.\n\n## Configure End-User Notification[](https://help.nightfall.ai/jira/installation/integration_alerts#configure-end-user-notification)\n\nWhen an Event is triggered, Nightfall sends a notification to the end-user whose actions triggered the Event. While notifying the end-user, Nightfall also sends a text message. You can draft the text message to be sent to the end-user. This message applies to all the policies. Click **Save changes** once done.\n","2026-08-04T17:15:32.340Z","2026-08-04T17:15:32.397Z","90b9b940-f4fc-4796-a476-6064beef40f5",[],[],[],"Configuring Advanced Settings in Nightfall for JIRA | Nightfall Documentation","configuring-advanced-settings-in-nightfall-for-jira-nightfall-documentation","https://help.nightfall.ai/jira/policies/advanced_settings","# Configuring Advanced Settings in Nightfall for JIRA\n\nThis stage allows you to select notification channels if a policy violation occurs. The advanced settings page consists of the following configurations.\n\n[Admin Alerting](https://help.nightfall.ai/jira/policies/advanced_settings#admin-alerting): This section describes the process of setting alerts for Nightfall administrators when a policy violation is detected.\n\n[Automated Actions](https://help.nightfall.ai/jira/policies/advanced_settings#automated-actions): This section describes the automated actions that can be taken when a policy violation is detected.\n\n[End User Notification](https://help.nightfall.ai/jira/policies/advanced_settings#end-user-notification): This section describes the process of setting alerts for end users (a person whose action caused a violation) when a policy violation is detected.\n\n## Admin Alerting[](https://help.nightfall.ai/jira/policies/advanced_settings#admin-alerting)\n\nThe alert configurations configured in this section describe the process of creating alerts at the policy level. Policy-level alerts apply only to the policy on which they are configured. To configure an alert on all the Slack policies, you must configure alerts at the integration level. To learn more about how to configure integration-level policies for Slack integration, read [this document](https://help.nightfall.ai/nightfall-ai/nightfall-for-jira/installing-nightfall-for-jira/configuring-integration-alerts).\n\nThe steps to configure alert channels for policy-level integration are the same as in the case of integration-level alerts. You can refer to [this document](https://help.nightfall.ai/nightfall-ai/nightfall-for-jira/installing-nightfall-for-jira/configuring-integration-alerts#configure-alerts-at-the-integration-level) for steps.\n\n## Automated Actions[](https://help.nightfall.ai/jira/policies/advanced_settings#automated-actions)\n\nThis section describes the various actions that Nightfall takes automatically when a violation is detected. You must turn on the toggle switch to enable an action. All the automated actions are permanent and cannot be reversed once applied. You can also set the timeline as to when an action must be taken (immediately after detecting a violation or after some time).\n\nThe various automated actions are described as follows.\n\n### Conflict Management in Automated Actions[](https://help.nightfall.ai/jira/policies/advanced_settings#conflict-management-in-automated-actions)\n\nAutomated actions in policies can sometimes conflict. This article explains how Nightfall manages these conflicts.\n\nConflicts can arise in two main scenarios:\n\n1. Both the automated actions are configured in a single policy.\n\n2. Multiple policies with different automated actions were violated simultaneously within the same file, message or record.\n\nWhen conflicts occur, Nightfall implements the most severe automated action.\n\n- In JIRA policies, conflicts can arise in both single-policy and multi-policy scenarios.\n\n- In a conflict situations, Nightfall implements the **Delete** action to resolve the conflict.\n\n## End User Notification[](https://help.nightfall.ai/jira/policies/advanced_settings#end-user-notification)\n\nThis section allows you to configure notifications to be sent to the end user whose actions triggered the violation.\n\n- **Custom Message**: Enter a custom message to be sent to the end user. This message is sent in an Email. You can modify the default message provided by Nightfall and draft your message. The total character length allowed is 1000 characters. You can also add hyperlinks in the custom message. The syntax is \\. For example, to hyperlink [https://www.nightfall.ai](https://www.nightfall.ai/) with the text **Nightfall website**, you must write <[https://www.nightfall.ai](https://www.nightfall.ai/) | Nightfall website>.\n\n- **Automation**: You can either select Email, Slack, or both as an automated notification method. You must turn the toggle switch to use this option. Based on the options selected, end-users receive notification on their Email account associated with JIRA, or Slack account configured.\n\nEnd-User remediation (also known as Human Firewall) allows you to configure remediation measures that end users can take when a violation is detected on their JIRA environment. You must turn on the toggle switch to use this option. The various available options are as follows.\n\n- **Redact:** This action redacts all the sensitive information found in the JIRA ticket's comments. To allow end-users to implement this action, you must disable it from the [Automated Actions](https://help.nightfall.ai/jira/policies/advanced_settings#automated-actions) section.\n\n- **Delete**: This action deletes any attachments in the JIRA ticket's comments that contain sensitive information. To allow end-users to implement this action, you must disable it from the [Automated Actions](https://help.nightfall.ai/jira/policies/advanced_settings#automated-actions) section.\n\n- **Report as False Positive with Business Justification**: This option allows end users to report false positive alerts and provide a business justification as to why the alert is considered to be false positive.\n\n- **Report as False Positive**: This option allows end users to report false positive alerts.\n\n- **When a Violation is Reported as False Positive**: You can use this option to set actions to be taken when a violation is reported as false positive by the end-user. You can either set the remediation to be automatic or manual.\n\n- **Remind Every (until Violation expires)**: You can use this option to set a reminder for the end-user to take action on the violation. You can choose to remind the end user every 24, 48, or 72 hours.\n","2026-08-04T17:15:42.148Z","2026-08-04T17:15:42.182Z","05c5f349-8cf8-41fe-bd8c-b501b466a1f6",[],[],[],"Configure Scope in Nightfall for JIRA | Nightfall Documentation","configure-scope-in-nightfall-for-jira-nightfall-documentation","https://help.nightfall.ai/jira/policies/scope","# Configure Scope in Nightfall for JIRA\n\nNightfall can scan all Jira item types (Tickets, Attachments, and Comments). Scans will include archived items, but not deleted items. Only fields of type free-text fields are scanned: Summary (title), Description (body), Labels, and all custom fields. Fields such as Assignee, and Reporter, are not scanned.\n\nTo configure Policy Scope:\n\n1. Click **+ Add Instances** and select an instance.\n\n2. Select one of the following options under the **Include in Monitoring** section. The scope of this policy is limited to only those categories of tickets which are selected in this section.\n\n- **All Projects:** This option ensures that all the projects in your JIRA environment are monitored by Nightfall.\n\n- **Choose Projects**: This option allows you to select the projects in your JIRA environment that you wish to be monitored by Nightfall.\n\nThe **Exclude from Monitoring** section allows you to exclude Projects. You can use this option to exclude projects if you have selected the **All Projects** option in Step 2.\n\nClick **Next**.\n","2026-08-04T17:15:41.447Z","2026-08-04T17:15:41.471Z","171f6d91-22e2-48d7-8529-619e942a8feb",[],[],[],"Configure Scope for Zendesk | Nightfall Documentation","configure-scope-for-zendesk-nightfall-documentation","https://help.nightfall.ai/zendesk/policies/scope","The Scope stage allows you to select the Zendesk tenant in which the policy can be created.\n\nTo configure Policy Scope:\n\n1. Click **+ Add Instances** and select an instance.\n\n2. Select one of the following options under the **Include in Monitoring** section. The scope of this policy is limited to only those categories of tickets which are selected in this section.\n\n- **New:** This option adds all the newly created tickets to be monitored.\n\n- **Pending:** This option adds all the pending tickets to be monitored.\n\n- **Open:** This option adds all the open tickets to be monitored.\n\n- **Solved:** This option adds all the solved tickets to be monitored.\n\n1. To select all the tickets, click **Select All**.\n\n2. Select the tags to be included from the **Tags Inclusion** section. Only tickets which have the selected tags are monitored by Nightfall.\n\nThe **Exclude from Monitoring** section allows you to exclude Groups and Agents from the policy scope. It is optional and you can proceed without configuring this section, if you wish to maintain the scope of the policy to all the Groups and Agents, selected in Step 2.\n\n1. Select the Groups and Agents to be excluded.\n\n- **Groups Exclusion**: This option displays a drop-down menu of all the Groups selected in Step 2. You can select any Group to exclude it from the scope of the policy.\n\n- **Agents (User) Exclusion**: This option displays a drop-down menu of all the Agents (basically users) selected in Step 2. You can select any Agent to exclude them from the scope of the policy.\n\n- **Tags Exclusion**: This option displays a drop-down menu of all the tags in your Zendesk account. You can select tickets with specific tags to be excluded from being moniored.\n\n1. Click **Next**.\n\n## Example Scenario[](https://help.nightfall.ai/zendesk/policies/scope#example-scenario)\n\nConsider that you wish to scan all the tickets irrespective of their status. However, there is a specific group called **Support.** You do not wish to scan tickets from this group (assuming it's an internal support group). You can accomplish this by using the **Groups Exclusion** field as shown in the following image.\n\nSimilarly, you can also exclude a specific user by using the **Agents Exclusion** field.\n","2026-08-04T18:30:39.017Z","2026-08-04T18:30:39.047Z","fcabea43-2b5d-4ba6-a8e1-b939b1c47202",[],[],[],"Configure Scope for Slack Pro and Slack Business+ | Nightfall Documentation","configure-scope-for-slack-pro-and-slack-business-nightfall-documentation","https://help.nightfall.ai/slack/slack_pro_policy/scope","# Configure Scope for Slack Pro and Slack Business+\n\nThis document explains how to set up the Policy Scope for Slack Pro and Slack Business+ editions. If you are using a Slack Enterprise edition, you must refer to [this document](https://help.nightfall.ai/nightfall-ai/nightfall-for-slack/installation-instructions-nightfall-for-slack-2/scope).\n\nThe Scope stage allows you to select Slack Channels and Connections which must be scanned by the policy.\n\nTo configure Policy Scope:\n\n1. Select one of the following options under the **Select Channels** section. The scope of this policy is limited to only those channels and connections which you select in this section.\n\n- **Channels**: Select the **Select All** check box to scan the data in all your Slack channels. Select the **Public Channels** check box to scan data only in your Public Slack Channels. Select the **Private Channels** check box to scan data only in your private Slack channels.\n\n- **Connections**: Select the **Select All** check box to scan the data in all your Slack connections. Select the **Public Connect Channels** check box to scan data only in your Public connect Slack Channels. Select the **Private Connect Channels** check box to scan data only in your private connect Slack channels.\n\nYou must add the Nightfall Pro Slack application to all the channels that you wish to scan with Nightfall.\n\n## Applying Filters[](https://help.nightfall.ai/slack/slack_pro_policy/scope#applying-filters)\n\nThe Filters section provides you an added level of granularity in setting the Scope. You can use specific filters to filter data based on Users, Groups, Channels, or Apps.\n\n## How Slack Filters Work[](https://help.nightfall.ai/slack/slack_pro_policy/scope#how-slack-filters-work)\n\nSlack policies support filtering based on users, user groups, and apps. These options provide flexible, granular control on whom to apply the monitoring. The **Only Include** option is very useful to pick specific required users, groups or apps for monitoring. particularly useful for creating broad policies with specific exceptions. Combining user and group options allows for complex, layered access control. The **exclude** option allows you to exclude the monitoring of unwanted users, user groups and apps, thus reducing the unwanted noise from secure entities.\n\n### Filtering by Users[](https://help.nightfall.ai/slack/slack_pro_policy/scope#filtering-by-users)\n\n- **Only Include**: Only messages sent by selected users are scanned for sensitive data.\n\n- **Exclude**: Messages sent by excluded users are not scanned.\n\n### Filtering by Groups[](https://help.nightfall.ai/slack/slack_pro_policy/scope#filtering-by-groups)\n\n- **Only Include**: Only messages sent by users in included Slack groups are scanned for sensitive data.\n\n- **Exclude**: Messages sent by users in excluded Slack groups are not scanned.\n\n### Filtering by Apps[](https://help.nightfall.ai/slack/slack_pro_policy/scope#filtering-by-apps)\n\n- **Only Include**: Only messages sent by included Slack apps are scanned for sensitive data.\n\n- **Exclude**: Messages sent by excluded Slack apps are not scanned.\n\n## Priority Order for Conflict Management[](https://help.nightfall.ai/slack/slack_pro_policy/scope#priority-order-for-conflict-management)\n\nNightfall uses prioritization to decide which messages to scan when multiple filters are configured in a policy. The order of priority is:\n\n1. User Exclusion\n\n2. User Inclusion\n\n3. Group Exclusion\n\n4. Group Inclusion\n\n**How it works:**\n\n1\\. Initially, Nightfall checks if the file owner is on the User Exclusion list. If they are, their messages are not scanned, no matter how other filters are configured in a policy.\n\n2\\. If the user isn't excluded, Nightfall then checks if they're on the User Inclusion list. If they are, all their messages are scanned for that policy.\n\n3\\. If the user isn't on either the exclusion or inclusion lists, Nightfall looks at group memberships. It checks if the user belongs to any excluded groups. If they do, their messages are not scanned for that policy.\n\n4\\. Finally, if none of the above apply, Nightfall checks if the user is in any included groups. If they are, their messages are scanned for that policy. If not, the messages are not scanned.\n","2026-08-04T17:13:05.133Z","2026-08-04T18:33:00.475Z","fb9c6f81-88e0-42ee-93ba-67b5700da022",[],[],[],"Configure Scope for Slack Enterprise | Nightfall Documentation","configure-scope-for-slack-enterprise-nightfall-documentation","https://help.nightfall.ai/slack/enterprise_policy/scope","# Configure Scope for Slack Enterprise\n\nThis document explains how to set up the Policy Scope for the Slack Enterprise edition. If you are using a Slack Slack Pro or Slack Business+ editions, you must refer to [this document](https://help.nightfall.ai/nightfall-ai/nightfall-for-slack/installation-instructions-nightfall-for-slack-1/scope).\n\nThe Scope stage allows you to select Slack Channels, Connections, and Direct Messages (DMs) which must be scanned by the policy.\n\nYou must add the Nightfall Pro Slack application to all the channels that you wish to scan with Nightfall.\n\nThe Scope page allows you to set the Scope for one of the following entities.\n\n- **Workspaces:** Select the Workspaces radio button to configure the scope at the Workspace level. If you select the Workspace option, you can configure the Workspaces to be included in the scope. Within the Workspaces, you can choose to monitor specific types of Channels and Connections. Finally, you can also add filters to zero down on specific users, groups, channels, and apps.\n\n- **Specific Channel(s)**: Select the **Specific Channel(s)** radio button to monitor only specific Slack channels. Once you select the required Slack channels, you can add filters on the selected channels to monitor only specific users, groups, or apps.\n\n## Workspaces[](https://help.nightfall.ai/slack/enterprise_policy/scope#workspaces)\n\nIn the Workspaces section, you must first select the Slack Workspaces to be monitored by the policy.\n\n### Select Channel Types and Connections[](https://help.nightfall.ai/slack/enterprise_policy/scope#select-channel-types-and-connections)\n\nYou can choose to monitor the following. You must select the check box for the channel type to be monitored.\n\n#### Channel Types[](https://help.nightfall.ai/slack/enterprise_policy/scope#channel-types)\n\n- **Public Channel**: Select this option to monitor all the messages sent by users in all the public Slack channels of the selected workspace(s).\n\n- **Private Channel**: Select this option to monitor all the messages sent by users in all the private Slack channels of the selected workspace(s).\n\n- **Direct Messages**: Select this option to monitor all the direct messages exchanged between users in the selected workspace(s).\n\n#### Connections[](https://help.nightfall.ai/slack/enterprise_policy/scope#connections)\n\n- **Public Connect Channel**: Select this option to monitor all the messages sent by users in all the public Slack connect channels of the selected workspace(s).\n\n- **Private Connect Channel**: Select this option to monitor all the messages sent by users in all the private Slack connect channels of the selected workspace(s).\n\n- **Direct Messages**: Select this option to monitor all the direct messages exchanged between users in the selected workspace(s).\n\n## Applying Filters[](https://help.nightfall.ai/slack/enterprise_policy/scope#applying-filters)\n\nThe Filters section provides you an added level of granularity in setting the Scope. You can use specific filters to filter data based on Users, Groups, or Apps.\n\n## How Slack Filters Work[](https://help.nightfall.ai/slack/enterprise_policy/scope#how-slack-filters-work)\n\nSlack policies support filtering based on users, user groups, channels, and apps. These options provide flexible, granular control on whom to apply the monitoring. The **Only Include** option is very useful to pick specific required users, groups, channels or apps for monitoring. particularly useful for creating broad policies with specific exceptions. Combining user and group options allows for complex, layered access control. The **exclude** option allows you to exclude the monitoring of unwanted users, user groups, channels, and apps, thus reducing the unwanted noise from secure entities.\n\n### Filtering by Users[](https://help.nightfall.ai/slack/enterprise_policy/scope#filtering-by-users)\n\n- **Only Include**: Only messages sent by selected users are scanned for sensitive data.\n\n- **Exclude**: Messages sent by excluded users are not scanned.\n\n### Filtering by Groups[](https://help.nightfall.ai/slack/enterprise_policy/scope#filtering-by-groups)\n\n- **Only Include**: Only messages sent by users in included Slack groups are scanned for sensitive data.\n\n- **Exclude**: Messages sent by users in excluded Slack groups are not scanned.\n\n### Filtering by Channels[](https://help.nightfall.ai/slack/enterprise_policy/scope#filtering-by-channels)\n\n- **Exclude**: Messages sent by users in excluded Slack Channels are not scanned. Enter the channel ID of the channel to be excluded.\n\n### Filtering by Apps[](https://help.nightfall.ai/slack/enterprise_policy/scope#filtering-by-apps)\n\n- **Only Include**: Only messages sent by included Slack apps are scanned for sensitive data.\n\n- **Exclude**: Messages sent by excluded Slack apps are not scanned.\n\n### Slack Tools (Slack Canvas)[](https://help.nightfall.ai/slack/enterprise_policy/scope#slack-tools-slack-canvas)\n\nThe Slack Canvas filter allows you to scan edits made to a Slack Canvas and files embedded within a Slack Canvas. You can choose to scan the required canvases or exclude the scanning of certain canvases. The filter options available are as follows.\n\n- **Specific Canvases**: This option scans all your Slack Canvases and also files embedded within the Canvas.\n\n- **Specific Canvases**: This option allows you to select specific Slack Canvases. Only the selected Canvases and the files embedded within the Canvas are scanned.\n\n- **All Canvases, except for**: This option allows you to select specific Slack Canvases. The selected Canvases and files embedded within these Canvases are not scanned and all other Canvases are scanned.\n\n**Note**: If you do not configure the Slack Canvases filter, Nightfall still scans Canvases shared in direct messages and groups. Enabling this footer ensures that Canvases not shared in any messages or groups are also scanned\n\n## Priority Order for Conflict Management[](https://help.nightfall.ai/slack/enterprise_policy/scope#priority-order-for-conflict-management)\n\nNightfall uses prioritization to decide which messages to scan when multiple filters are configured in a policy. The order of priority is:\n\n1. User Exclusion\n\n2. User Inclusion\n\n3. Group Exclusion\n\n4. Group Inclusion\n\n**How it works:**\n\n1\\. Initially, Nightfall checks if the file owner is on the User Exclusion list. If they are, their messages are not scanned, no matter how other filters are configured in a policy.\n\n2\\. If the user isn't excluded, Nightfall then checks if they're on the User Inclusion list. If they are, all their messages are scanned for that policy.\n\n3\\. If the user isn't on either the exclusion or inclusion lists, Nightfall looks at group memberships. It checks if the user belongs to any excluded groups. If they do, their messages are not scanned for that policy.\n\n4\\. Finally, if none of the above apply, Nightfall checks if the user is in any included groups. If they are, their messages are scanned for that policy. If not, the messages are not scanned.\n\n## Channels[](https://help.nightfall.ai/slack/enterprise_policy/scope#channels)\n\nTo select specific channels to be scanned, you must first click the **Specific channel(s)** radio button. You must then enter the Slack channel ID of the channels that you wish to be scanned. To learn more about how to find the Channel ID of a Slack channel, see [View Channel ID](https://help.nightfall.ai/slack/enterprise_policy/scope#view-channel-id).\n\n## View Channel ID[](https://help.nightfall.ai/slack/enterprise_policy/scope#view-channel-id)\n\nTo view and copy the Channel ID of a Slack channel:\n\n1. Click the required Slack Channel.\n\n2. Click the **Get channel details** button.\n\n3. Navigate to the bottom and click the **Copy channel id** button.\n","2026-08-04T17:13:05.885Z","2026-08-04T18:33:01.176Z","18061ba0-416d-4bf8-8538-795088f728ab",[],[],[],"Configure Scope for Salesforce | Nightfall Documentation","configure-scope-for-salesforce-nightfall-documentation","https://help.nightfall.ai/salesforce/policies/scope","The Scope stage allows you to select the Salesforce org in which the policy can be created.\n\nTo configure Policy Scope:\n\n1. Click **+ Add Org** and select a Salesforce org.\n\n2. Select the Salesforce object that must be scanned by Nightfall. Currently, Nightfall only displays the standard Salesforce objects.\n\n3. Select the check box for the Salesforce fields that must be scanned by Nightfall. Nightfall displays a list of Salesforce fields (from the selected Salesforce Object) that are vulnerable to data leaks (including custom fields). This includes fields whose data type is Number, Name, Description, and so on.\n\nYou must select the **Select all** check box to include all the displayed fields for scanning.\n\n1. (Optional) Click the **<-** arrow to navigate back to the Object list, select another object, and subsequently the fields of the objects to be scanned.\n\nYou can view the number of Objects and fields selected for scanning in the top right corner. See [High Risk Objects](https://help.nightfall.ai/salesforce/policies/high-risk-salesforce-objects-and-fields-for-data-loss-prevention-dlp) for recommendations on objects and fields to be scanned.\n\nCertainly! Here's a more concise version with grammatical accuracy and short sentences:\n\n## **Apply Filters**[](https://help.nightfall.ai/salesforce/policies/scope#apply-filters)\n\nAfter selecting Salesforce Objects and Fields, you can refine your policy scope. Filters allow you to scan files owned or shared by specific users, groups, or profile members. You can also exclude files owned or shared by them.\n\nFilters are optional. If you want to scan all users, groups, and profiles, you can skip this step.\n\nTo apply a filter, click **Add Filter** and select an option. Nightfall provides the following filters:\n\n### **Internal Users**[](https://help.nightfall.ai/salesforce/policies/scope#internal-users)\n\nScan files owned or shared by specific internal users. You can also exclude files owned or shared by them.\n\n### **Internal Groups**[](https://help.nightfall.ai/salesforce/policies/scope#internal-groups)\n\nScan files owned or shared by specific internal groups. You can also exclude scanning of files owned or shared by members of internal groups.\n\n**Note**: This filter cannot be used with the Salesforce Profiles filter.\n\n### **Salesforce Profiles**[](https://help.nightfall.ai/salesforce/policies/scope#salesforce-profiles)\n\nScan files owned or shared by members with specific Salesforce profiles.\n\n**Note**: This filter cannot be used with the Internal Groups filter.\n","2026-08-04T18:30:40.678Z","2026-08-04T18:30:40.719Z","a34cd896-1b31-4578-843f-40e48a8b3a94",[],[],[],"Configure Scope for Google Drive | Nightfall Documentation","configure-scope-for-google-drive-nightfall-documentation","https://help.nightfall.ai/google-drive/policies/scope","# Configure Scope for Google Drive\n\nThe Scope stage allows you to include or exclude various Google drives, files, and folders from being monitored.\n\nThe Scope stage consists of two main sections.\n\n- **Drive Selection**: This section allows you to include various files and drives for monitoring. In this section, you can select various drives to be monitored.\n\n- **Permission**: This section allows you to select files with specific permissions, shared with any internal or external users or user groups.\n\n- **Add Filters**: This section allows you to scrutinize your policy scope at more granular levels. While the Permission section allows you to select all the files belonging to a specific permission type and all the internal or external users and groups, in this section you can add filters to include or exclude individual files, users, and groups from being monitored or being excluded from monitoring.\n\n## Configuring the Drive Selection Section[](https://help.nightfall.ai/google-drive/policies/scope#configuring-the-drive-selection-section)\n\nThe **Drive Selection** section allows you to select various drives for monitoring. You can select either User Drives or Shared drives to be monitored by Nightfall for sensitive data.\n\n### Select Drives[](https://help.nightfall.ai/google-drive/policies/scope#select-drives)\n\nThis section allows you to select various drives in your Google Drive to be monitored. There are two options in this section. You can either choose to scan the User drives, Shared drives, or both.\n\n- **User Drives**: The User Drives is the personal drive of the user. The files in this drive are visible only to the owner of the file and other users to whom the owner has given access. User Drive is commonly known as **My Drive** in Google Drive. To select the User drive for scanning, you must select the **User drives** check box.\n\n**IMPORTANT**\n\nIf you choose to monitor the User drives, all the User drives in your Google domain are selected for monitoring. You do not have the option to choose specific User drives for monitoring.\n\n- **Shared Drives**: Shared drives are common storage locations accessed by all the users in your organization. To select this option, you must select the **Shared drives** check box.\n\n**IMPORTANT**\n\nIf you choose to monitor the Shared drives, you can select whether to monitor all the Shared drives or only specific shared drives.\n\n- If you select the **All Drives** option, all the Shared drives in your Google domains are selected for monitoring.\n\n- If you select the **All Drives, except for** option, you can exclude some shared drives from being monitored.\n\n- If you select the **Specific Shared Drives** option, you get the option to choose specific Shared drives for monitoring.\n\nThe following image displays the scenario when you select the **All Shared drives** check box.\n\nIf you select the **All Drives, except for** option, you must also select the shared drives which must be excluded from monitoring.\n\nSimilarly, if you select the **Specific Drive(s)** option, you must also select the specific shared drives which must be monitored.\n\n## Configuring the Permission Section[](https://help.nightfall.ai/google-drive/policies/scope#configuring-the-permission-section)\n\nThe Permission section allows you to add all the files, users, and user groups that match a certain criteria, to the scope of the policy. This section has the following configurations.\n\nIf you wish to scan all the files in the selected drive(s), you can skip this section.\n\n### General Access[](https://help.nightfall.ai/google-drive/policies/scope#general-access)\n\nThe general access feature in Google Workspace consists of three types of access, which are as follows.\n\n- **Restricted**: Files with this permission can only be accessed by users or groups who have been granted direct access.\n\n- **Target Audience**: Files with this permission can be accessed by the users of the selected target audience group. There is a default target audience that gets created when the Google workspace is provisioned. This target audience has the same name as provisioned in the Google Workspace and includes all members of the organization. You can refer to this [Google document](https://support.google.com/a/answer/9934697?hl=en) to learn more about the target audiences.\n\n- **Anyone with the Link**: Files with this permission can be accessed by any user who has the file link.\n\nThe Nightfall **General Access** permission options map 1x1 to the General Access sharing principle in Google Workspace.\n\n- **Restricted**: If you select this option, all the files from within the selected drive (User Drive or Shared Drive) which have the Restricted permission are monitored by the policy.\n\n- **Shared with target audiences**: If you select this option, all the files from within the selected drive (User Drive or Shared Drive), which have general access set to any of the target audiences, are monitored by the policy.\n\n- **Anyone with the link**: If you select this option, all the files from within the selected drive (User Drive or Shared Drive), which have the Anyone with the Link permission are monitored by the policy.\n\n### Shared With[](https://help.nightfall.ai/google-drive/policies/scope#shared-with)\n\nThe **Shared With** section allows you to select the files which are directly shared with any internal users/groups and any external users/groups.\n\n- **Internal users or groups**: If you select this option, all the files which are accessible by any internal user(s) or internal group(s) via direct access (not via link or target audience), are monitored by the policy.\n\n- **External users or groups**: If you select this option, all the files which are accessible by any external user(s) or external group(s) via direct access (not via link or target audience), are monitored by the policy.\n\nFor instance, let’s assume that Acme corp has 10 external users. They select the **External users or groups** option. Now, even if one of the 10 external users has direct access to a file, it will be monitored by the policy. In this case, only if a file is not shared with any of the 10 external users, the file will be excluded from being monitored.\n\nNightfall does not check the membership details for external groups.\n\n## Configuring Add Filter Section[](https://help.nightfall.ai/google-drive/policies/scope#configuring-add-filter-section)\n\nThe **Add Filter** lets you precisely control which users and files are included in a policy by applying granular filters.\n\nTo effectively limit scope, it’s important to understand that policies evaluate files using **two independent paths**:\n\n- **Ownership**: Checks if the file owner is an included user\n\n- **Sharing**: Checks if the file is shared with any users allowed by your policy settings\n\nA file will trigger if it matches **either** path.\n\nBecause these paths operate independently, restricting only ownership (e.g., selecting a single user) does **not** fully limit scope. Files may still match if they are shared with other users in scope.\n\nTo fully restrict scope, you must configure both:\n\n- User filters (ownership), and\n\n- Sharing controls (e.g., domain restrictions)\n\n#### **Example: Testing with one user and all Permissions options:**[](https://help.nightfall.ai/google-drive/policies/scope#example-testing-with-one-user-and-all-permissions-options)\n\n- Include: `test-user@your-company.com`\n\n- All groups except for: `*@your-company.com`\n\n#### When to Use Filters[](https://help.nightfall.ai/google-drive/policies/scope#when-to-use-filters)\n\nIf you select **Permissions: Internal users or groups**, all internal users and groups are included by default. In this mode, you cannot directly pick specific users to include or exclude.\n\nTo apply more targeted control, use the **Add Filter** section.\n\nNightfall allows filters across the following entities:\n\n### Internal Users[](https://help.nightfall.ai/google-drive/policies/scope#internal-users)\n\n- **Specific User(s)**: You must choose this option to monitor files that are owned by or accessible to specific internal users. Once you choose this option, Nightfall populates the list of users from the synced IdPs in [Directory Sync](https://help.nightfall.ai/nightfall_settings/directory_sync). You must select the required users.\n\n- **All Users, except for**: You must select this option to exclude files which are owned by or accessible to specific internal users. Once you choose this option, Nightfall populates the list of users from the synced IdPs in [Directory Sync](https://help.nightfall.ai/nightfall_settings/directory_sync). You must select the required users.\n\n**Note**\n\nIf you have not configured the [Directory Sync](https://help.nightfall.ai/nightfall-ai/nightfall-settings/directory-sync) feature, the users list is populated from the [Google Drive integration setup](https://help.nightfall.ai/nightfall-ai/nightfall-for-google-drive/installation-instructions-nightfall-for-google-drive/installing-nightfall-for-google-drive). As a result, you can see the Google Drive icon before the user name. However, if you have set up Directory sync, the users list is fetched from the IdP used for the configuration. In the above image, the users list is populated from the Microsoft Azure IdP and hence you can see the Azure icon before the users’ names.\n\n**Important**\n\nFor exclusions, Nightfall only checks the file ownership (\\*Nightfall also checks for shared access, but for exclusion to work for shared access, no user or group that is otherwise included should have access to the file, for it to be considered excluded). For inclusions, Nightfall checks both file ownership and shared access. This rule is applicable to all the filters.\n\n**Example Scenario**\n\nFor instance, let’s assume that Acme corp has 4 users who are part of Acme’s Google Workspace. The four users are Tom, Rick, Harry, and Steve. All four users have access to a file. Acme corp wishes to scan only those files which are owned or accessed only by Harry and Steve. They select the Internal users or groups option under the Shared With section. They apply the Internal Users filter, set the filter as Monitor specific and select Harry and Steve. Now only those files which are owned or accessible to either Harry, Steve, or both, are monitored by the policy.\n\n### External Users[](https://help.nightfall.ai/google-drive/policies/scope#external-users)\n\n- **Specific User(s)**: You must choose this option to monitor files that are accessible to specific external users. Once you choose this option, you must manually type the email ID of the required users and hit the enter key.\n\n- **All Users, except for**: You must choose this option to exclude files which are accessible by specific external users, from being monitored. Once you choose this option, you must manually type the email ID of the required users and hit the enter key.\n\n**Example Scenario**\n\nFor instance, let’s assume that Acme corp has 4 users who are external to Acme’s Google Workspace. The four users are **Tom, Rick, Harry**, and **Steve**. All four users have access to a file. Acme corp wishes to scan only those files which are accessed only by **Harry** and **Steve**. They select the **External users or groups** option under the **Shared With** section. They apply **External Users** filter, set the filter as **Monitor specific** and select **Harry** and **Steve**. Now only those files which are accessible to either Harry, Steve, or both, are monitored by the policy.\n\n### Internal Groups[](https://help.nightfall.ai/google-drive/policies/scope#internal-groups)\n\n- **Specific Group(s)**: You must choose this option to monitor files that are accessible to specific internal groups. Once you choose this option, Nightfall populates the list of internal groups from the synced IdPs in [Directory Sync](https://help.nightfall.ai/nightfall_settings/directory_sync). You must select the required users.\n\n- **All Groups, except for**: You must choose this option to exclude files which are accessible by specific internal groups, from being monitored. Once you choose this option, Nightfall populates the list of internal groups from the synced IdPs in [Directory Sync](https://help.nightfall.ai/nightfall_settings/directory_sync). You must select the required users.\n\n**Example Scenario**\n\nFor instance, let’s assume that Acme corp has three internal groups. The three groups are **Development**, **Testing**, and **Customer Success**. Acme Corp wishes to scan only those files accessed by the **Customer Success** group since the users of this group interact with customers and Acme does not wish them to leak any file with sensitive data to customers. Acme Corp selects the **Internal users or groups** option under the **Shared With** section. They apply the **Internal Groups** filter, set the filter as **Monitor specific** and select **Customer Success**. Now only those files which are accessible to the group email ID of Customer Success, are monitored by the policy.\n\n### External Groups[](https://help.nightfall.ai/google-drive/policies/scope#external-groups)\n\n- **Specific Group(s)**: You must choose this option to monitor files that are accessible to specific external groups.\n\n- **All Groups, except for:** You must choose this option to exclude files which are accessible by specific external groups from being monitored.\n\n**Example Scenario**\n\nFor instance, let’s assume that Acme corp has three external groups. The three groups are **Sales**, **Marketing**, and **Customer Success**. Acme Corp wishes to scan only those files accessed by the **Customer Success** group. Acme Corp selects the **External users or groups** option under the **Shared With** section. They apply **External Groups** filter, set the filter as **Monitor specific** and select **Customer Success**. Now only those files which are accessible to the group email ID of Customer Success, are monitored by the policy.\n\n**Important**\n\nIf you have not configured Directory sync, in case of internal and external groups, Nightfall can only compare the entered group mail ID with the email ID of the group, and cannot check for the members of the groups. To check group membership, you must configure Directory Sync. Without Directory sync configured, if you enter a group mail ID, Nightfall does not display the number of users who are part of the group.\n\n### Labels[](https://help.nightfall.ai/google-drive/policies/scope#labels)\n\nA Label is a metadata that you can create to help users organize, find, and apply policy to files in Google Drive. To learn more about Google Drive Labels, refer to this [Google document](https://developers.google.com/drive/api/guides/about-labels).\n\nBefore utilizing filters for Labels, you must [enable Google Drive Labels](https://help.nightfall.ai/nightfall-ai/nightfall-for-google-drive/installation-instructions-nightfall-for-google-drive/enabling-google-drive-labels) as per instructions and create labels in your Google Drive.\n\nYou can choose one of the following options.\n\n- **Specific Label(s)**: You must choose this option to monitor only those files that contain the selected Labels. Once you choose this option, you must select the Labels. Nightfall only monitors those files that have the selected labels.\n\n- **All Labels, except for**: You must choose this option to exclude the monitoring of files that contain the selected Labels. Once you choose this option, you must select the Labels. Nightfall does not monitor the files that contain the selected labels.\n\n### Domains[](https://help.nightfall.ai/google-drive/policies/scope#domains)\n\nA Domain typically refers to an organization's email domain or Google Workspace domain. You can configure Nightfall to monitor specific domains or exclude certain domains from monitoring.\n\n- **Specific Domain(s)**: Nightfall will only monitor files associated with the specified domains. You can choose the option to monitor files that have been shared with specific domains. Once you choose this option, you must manually enter the domain (for example, abcd.com) and hit the enter key. Nightfall only monitors those files that belong to the selected domains.\n\nTo include personal email domains (e.g., gmail.com, yahoo.com), check the \"Add free personal email domains\" box. This automatically includes files shared with common personal email services such as gmail.com, yahoo.com, etc for scanning.\n\n- **All Domains, except for**: You must choose this option to exclude the monitoring of files that are shared with the selected domains. Once you choose this option, you must manually enter the domain (for example, abcd.com) and hit the enter key. Nightfall does not monitor those files that belong to the selected domains.\n\n### Files[](https://help.nightfall.ai/google-drive/policies/scope#files)\n\nYou can choose to monitor or exclude monitoring of specific files. To include or exclude files for monitoring, you must enter the file ID of the required file(s). You can find the File ID of a Google Drive file from the file URL. The format is as follows.\n\n- **Specific Files(s):** You must choose this option to monitor only the selected files. Once you choose this option, you must manually enter the file ID of the file and hit the enter key. Nightfall only monitors those files whose IDs are entered here. No other filters are evaluated if this filter is configured and only the selected files are scanned.\n\n- **All Files, except for**: You must choose this option to exclude the monitoring of specific files. Once you choose this option, you must manually enter the file ID of the file and hit the enter key. Nightfall does not monitor those files whose IDs are entered here.\n\n## Conflict Management[](https://help.nightfall.ai/google-drive/policies/scope#conflict-management)\n\nWhen setting up Google Drive policies, you can include or exclude specific users, user groups, and drives. Users and groups are synced via Okta, Entra, or Google directory. Here's how Nightfall resolves conflicts across configured filters in a sensitive data protection policy for Google Drive:\n\n### **1. Drive Filters**[](https://help.nightfall.ai/google-drive/policies/scope#id-1.-drive-filters)\n\n- **Drive Inclusions**: Specify drives to be scanned in this policy.\n\n- **Drive Exclusions**: Specify drives to be exempt from scanning in this policy.\n\n### **2. General Access** Filters[](https://help.nightfall.ai/google-drive/policies/scope#id-2.-general-access-filters)\n\n**a. If no options are selected in this filter**:\n\n- No files will be automatically included for scanning based solely on their general access settings.\n\n- Files may still be scanned based on other filter criteria in the policy.\n\n- The policy will rely on other configured filters to determine which files should be scanned. At least one of the options in general access filters or shared with filters need to be selected for any files to be scanned via a policy.\n\n**b. Options:**\n\n- \"Restricted\": Files with this setting are included for further filtering.\n\n- \"Shared with target audience\": Files with ANY target audience setting are included for further filtering.\n\n- \"Anyone with link\": Files with this setting are included for further filtering.\n\n### **3. Shared With** Filters[](https://help.nightfall.ai/google-drive/policies/scope#id-3.-shared-with-filters)\n\n**a. If no options are selected in this filter**:\n\n- Files that are shared directly with ANY user or user groups will be ineligible for scanning specifically for this check.\n\n- Files that are not shared at all may still be eligible for scanning based on other filter criteria.\n\n- The policy will rely on other configured filters to determine which files should be scanned.\n\n- The policy will rely on other configured filters to determine which files should be scanned. At least one of the options in general access filters or shared with filters needs to be selected for any files to be scanned via a policy.\n\n**b. Options**:\n\n- **Internal users or groups**: Files not shared directly with ANY internal user or group are ineligible for scanning specifically for this check.\n\n- **External users or groups**: Files not shared directly with ANY external user or group are ineligible for scanning specifically for this check.\n\n### 4. File Filters[](https://help.nightfall.ai/google-drive/policies/scope#id-4.-file-filters)\n\n- **File Inclusions**: If left unconfigured, all files are included for further filtering. When specific files are listed, they are always scanned and all other filters are ignored.\n\n- **File Exclusions**: If left unconfigured, no files are automatically excluded. Listed files are never scanned under this policy.\n\nFiles can be included or excluded by specifying the file ID. File IDs can be found directly in their URL. The format is ID]/…\n\n### 5. Label Filters[](https://help.nightfall.ai/google-drive/policies/scope#id-5.-label-filters)\n\n1. **Label Inclusions**: If left unconfigured, labels on files are not evaluated for inclusions. When specific labels are listed, only files with these labels are scanned for this specific policy check.\n\n2. **Label Exclusions**: If left unconfigured, labels on files are not evaluated for automatic exclusion of files. Files with listed labels are ineligible for scanning specifically for this policy check.\n\n### **6. User Filters**[](https://help.nightfall.ai/google-drive/policies/scope#id-6.-user-filters)\n\n- **User Inclusions**: If left unconfigured, all users are included. For listed internal users, files neither owned nor shared with them are ineligible for this specific check. For listed external users, files not shared with them are ineligible for this specific check.\n\n- **User Exclusions**: If left unconfigured, no users are automatically excluded. For listed internal users, files they own or are ONLY accessible by them are ineligible for this specific check. For listed external users, files ONLY accessible by them are ineligible for this specific check.\n\n### **7. Group Filters**[](https://help.nightfall.ai/google-drive/policies/scope#id-7.-group-filters)\n\n- **Group Inclusions**: If left unconfigured, all groups are included. For listed internal groups, files neither owned nor shared with any member of these groups are ineligible for this scan. For listed external groups, files neither owned nor shared with the external group email are ineligible for this scan.\n\n- **Group Exclusions**: If left unconfigured, no groups are automatically excluded.\n\n### 8. Domain Filters[](https://help.nightfall.ai/google-drive/policies/scope#id-8.-domain-filters)\n\n- **Domain Inclusions**: If left unconfigured, all domains are included. For listed domains, files neither owned nor shared with at least one user belonging to the specified domains are not eligible to be scanned.\n\n- **Domain Exclusions**: If left unconfigured, no domains are automatically excluded. For listed domains, files owned or shared only with users belonging to the specified domains are eligible to be excluded from scanning.\n","2026-08-04T17:14:20.555Z","2026-08-04T18:41:18.672Z","e1a31fe9-c9f6-4ced-860e-b2e35c809145",[],[],[],"Configure Scope for Gmail | Nightfall Documentation","configure-scope-for-gmail-nightfall-documentation","https://help.nightfall.ai/gmail/policies/scope","The Gmail Scope configuration page allows you to set filters to perform the following tasks.\n\n- **Monitor or Exclude Monitoring of Emails sent by Specific Users and Groups**: You can set up the Gmail scope to monitor only the required emails that were sent by either specific users or from a user group ID. Similarly, you can also choose to exclude certain user and group mail IDs from being monitored.\n\n- **Monitor or Exclude Monitoring of Emails sent to Specific Recipients and Domains**: You can choose specific email IDs that you wish to monitor or skip monitoring.\n\nThe Scope section is divided into the following two sub-sections.\n\n- **Senders**: Select this option if you wish to monitor or exclude monitoring of outgoing mails from specific users or user groups.\n\n- **Recipients**: Select this option to monitor or exclude monitoring of emails sent to specific recipients. The recipients can be a user or a user group. Additionally, you can also choose to exclude an entire domain. All the emails sent to the mail IDs of the excluded domain(s) are not monitored by Nightfall.\n\n## Key principles and Priority Order in Which Filters are Evaluated[](https://help.nightfall.ai/gmail/policies/scope#key-principles-and-priority-order-in-which-filters-are-evaluated)\n\n### Key Principles:[](https://help.nightfall.ai/gmail/policies/scope#key-principles)\n\n- Exclusions are evaluated before inclusions\n\n- Recipient filters are validated before the sender filters\n\n- User-level filters take priority over group-level filters\n\n- Domain-level filters, for recipients, have the highest priority\n\n- If no filters match, the default action is to scan the email\n\n### Priority order for filters[](https://help.nightfall.ai/gmail/policies/scope#priority-order-for-filters)\n\n**Important**\n\nThe following list represents both the order and priority in which filters are evaluated when multiple filters are configured in a policy. Filters higher on the list take precedence over those lower down.\n\n1. Recipient Domain Exclusions\n\n2. Recipient Domain Inclusions\n\n3. Recipient User Exclusions\n\n4. Sender User Exclusions\n\n5. Sender Group Exclusions\n\n6. Recipient User Inclusions\n\n7. Sender User Inclusions\n\n8. Sender Group Inclusions\n\n9. Default to scan all emails, if no other filters apply\n\nNow, let's take a look at an example scenario to describe the behavior.\n\n**Example Scenario**:\n\nA marketing team member () sends an email to:\n\nLet's examine how different filter configurations would affect this email:\n\n1. **Recipient Domain Exclusions**:\n\n - If configured: external-partner.com is excluded\n\n - Result: Email will still be scanned because not all recipients are in the excluded domain.\n2. **Recipient Domain Inclusions**:\n\n- If configured: external-partner.com is included\n\n- Result: Email will be scanned given one of the domain is included.\n\n1. **Recipient User Exclusions**:\n\n- If configured: is excluded\n\n- Result: Email will still be scanned because not all recipients are excluded.\n\n1. **Sender User Exclusions**:\n\n- If configured: is excluded\n\n- Result: Email won't be scanned, regardless of recipients.\n\n1. **Sender Group Exclusions**:\n\n- If configured: Marketing group is excluded\n\n- Result: Email won't be scanned if sender is in the Marketing group.\n\n1. **Recipient User Inclusions**:\n\n- If configured: is included\n\n- Result: Email will be scanned because at least one recipient is included.\n\n1. **Sender User Inclusions**:\n\n- If configured: is included\n\n- Result: Email will be scanned due to sender inclusion.\n\n1. **Sender Group Inclusions**:\n\n- If configured: Marketing group is included\n\n- Result: Email will be scanned if sender is in the Marketing group.\n\n1. **Default to scan all emails**:\n\n- If no other filters apply, the email will be scanned.\n\n**Notes**:\n\n- The first matching filter as per the priority listed above determines if the email is scanned.\n\n- For recipient-based filters, ALL recipients must match for exclusions, but ANY match triggers inclusions such that the email is scanned.\n\nThis priority order ensures that the most specific and restrictive rules are applied first, allowing for precise control over email scanning while maintaining a clear hierarchy for conflict resolution when multiple filters are in place.\n\n## Configuring Senders[](https://help.nightfall.ai/gmail/policies/scope#configuring-senders)\n\nThe **Senders** section is used to configure specific email IDs that must be monitored or excluded from monitoring. The mail IDs of individual users and user group mail IDs can be configured.\n\nTo configure the Sender section, you must select the **Sender** option by clicking the **Add Filter** drop-down menu.\n\nOnce you select the **Sender** option, you can configure **Users** and **User groups**.\n\n### Users Configuration[](https://help.nightfall.ai/gmail/policies/scope#users-configuration)\n\n- **Monitor all:** Select this option to monitor all the emails sent by users whose data was synced from an IdP through the [Directory Sync](https://help.nightfall.ai/nightfall-ai/nightfall-settings/directory-sync) feature.\n\n- **Monitor specific**: Select this filter to monitor all the emails being sent by specific user(s). Once you select this option, you must also select specific user(s) from the search bar. Nightfall populates the name and email IDs of all the users whose data was synced from an IdP through the [Directory Sync](https://help.nightfall.ai/nightfall-ai/nightfall-settings/directory-sync) feature. You must select the required users' mail IDs. All the emails sent by selected users are monitored by Nightfall for sensitive data.\n\n- **Monitor all, except**: Select this filter to exclude user(s). Emails sent by the excluded users are not monitored by the policy. Once you select this option, you must also select specific user(s) from the search bar. Nightfall populates the name and email IDs of all the users whose data was synced from an IdP through the [Directory Sync](https://help.nightfall.ai/nightfall-ai/nightfall-settings/directory-sync) feature. You must select the required user groups. The emails sent by selected users are not monitored by Nightfall.\n\n### User Groups Configuration[](https://help.nightfall.ai/gmail/policies/scope#user-groups-configuration)\n\n- **Monitor all:** Select this option to monitor all the emails sent by users whose data was synced from an IdP through the [Directory Sync](https://help.nightfall.ai/nightfall-ai/nightfall-settings/directory-sync) feature.\n\n- **Monitor Specific**: Select this option to monitor all the emails being sent from specific user group mail IDs. Nightfall populates the name and email IDs of all the user groups whose data was synced from an IdP through the [Directory Sync](https://help.nightfall.ai/nightfall-ai/nightfall-settings/directory-sync) feature. You must select the required user group mail IDs. All the emails sent from the selected user group mail IDs are monitored by Nightfall for sensitive data.\n\n- **Monitor all, except**: Select this option to exclude user group(s). Emails sent from the excluded user group mail IDs are not monitored by the policy. Once you select this option, you must also select specific user group(s) from the search bar. Nightfall populates the name and email IDs of all the user groups whose data was synced from an IdP through the [Directory Sync](https://help.nightfall.ai/nightfall-ai/nightfall-settings/directory-sync) feature. You must select the required user groups. The emails sent from the selected user group mail IDs are not monitored by Nightfall.\n\n## Configuring Recipients and Domains[](https://help.nightfall.ai/gmail/policies/scope#configuring-recipients-and-domains)\n\nThe Recipients and Domains section allows you to monitor or exclude monitoring of emails sent to specific recipients. Additionally, you can also exclude monitoring of an entire domain.\n\nYou can perform the following operations on the recipients section:\n\n- Monitor emails sent to specific recipients. Recipients can be internal/external or users/user groups.\n\n- Exclude monitoring of emails sent to specific recipients. Recipients can be internal/external or users/user groups.\n\n- Include or exclude monitoring of all the mails sent to the email IDs of a specific domain.\n\nTo configure the Recipient section, you must select the **Recipients** option by clicking the **Add** **Filter** drop-down menu.\n\nOnce you select the **Recipient** option, you must configure the internal and external Recipients, and the Domains sections.\n\n### Internal Recipients[](https://help.nightfall.ai/gmail/policies/scope#internal-recipients)\n\n- **Only Include**: Select this option to monitor emails sent to specific recipient email IDs which are generally part of your organization. The email IDs can belong to a user or a user group. Once you select this option, you must also select specific users or group(s) from the search bar. Nightfall populates the name and email IDs of all the users and user groups whose data was synced from an IdP through the [Directory Sync](https://help.nightfall.ai/nightfall-ai/nightfall-settings/directory-sync) feature. You must select the required user(s) and user group(s). All the emails sent to the selected user or user group email IDs are monitored by Nightfall for sensitive data.\n\n- **Exclude**: Select this option to exclude the monitoring of emails sent to specific recipient email IDs. The email IDs can belong to a user or a user group. Once you select this option, you must also select specific users or group(s) from the search bar. Nightfall populates the name and email IDs of all the users and user groups whose data was synced from an IdP through the [Directory Sync](https://help.nightfall.ai/nightfall-ai/nightfall-settings/directory-sync) feature. You must select the required user(s) and user group(s). All the emails sent to the selected user or user group email IDs are not monitored by Nightfall for sensitive data.\n\n### External Recipients[](https://help.nightfall.ai/gmail/policies/scope#external-recipients)\n\n- **Only Include**: Select this option to monitor emails sent to specific external recipient email IDs. The email IDs can belong to a user or a user group. Once you select this option, you must also enter the email ID of users or group(s) and hit the enter key. All the emails sent to the external user or user group email IDs are monitored by Nightfall for sensitive data.\n\n- **Exclude**: Select this option to exclude the monitoring of emails sent to specific external recipient email IDs. The email IDs can belong to a user or a user group. Once you select this option, you must also enter the email ID of users or group(s) and hit the enter key. All the emails sent to the external user or user group email IDs are not monitored by Nightfall for sensitive data.\n\n### Domains[](https://help.nightfall.ai/gmail/policies/scope#domains)\n\nThe Domains section allows you to include or exclude an entire domain from being monitored. All the mails sent to the email IDs of the excluded domain are not monitored by Nightfall. Similarly, all the emails sent to the email ID of the included domain are monitored by Nightfall.\n\n- **Only Include**: Select this option to monitor emails sent to specific domain(s). All the email IDs which belong to the included domain(s) are monitored by Nightfall. Once you select this option, you must also enter the domain name (example contoso.com) and hit the enter key. All the emails sent to email ID(s) that belong to the selected domain(s) are monitored by Nightfall for sensitive data.\n\n- **Exclude**: Select this option to exclude the monitoring of emails sent to specific domain(s). All the email IDs which belong to the excluded domain(s) are not monitored by Nightfall. Once you select this option, you must also enter the domain name (example contoso.com) and hit the enter key. All the emails sent to email ID(s) that belong to the excluded domain(s) are not monitored by Nightfall for sensitive data.\n","2026-08-04T18:29:59.307Z","2026-08-04T18:29:59.361Z","799f0a64-63c6-46d7-b1e0-4e0f6f97eacc",[],[],[],"Configure Scope for GitHub | Nightfall Documentation","configure-scope-for-github-nightfall-documentation","https://help.nightfall.ai/github/policies/scope","The Scope stage allows you to select a GitHub org in which you can the policy can be created.\n\nTo configure Policy Scope:\n\n1. Click **+ Org** and select the GitHub org.\n\n2. Select one of the following options under the **Include in Monitoring** section. The scope of this policy is limited to only those repositories which you select in this section.\n\n- **All Repositories:** This option adds all the repositories (public and private) in your GitHub org to the policy scope.\n\n- **Public Repositories:** This option adds all the public repositories in your GitHub org to the policy scope.\n\n- **Private Repositories:** This option adds all the private repositories in your GitHub org to the policy scope.\n\nThe **Total Monitoring Scope** section displays the number of GitHub repositories that will be monitored, based on your selection.\n\nThe **Exclude Repositories** section allows you to exclude repositories, files, and directories from the policy scope. It is optional and you can proceed without configuring this section, if you wish to maintain the scope of the policy to all the repositories and its directories, selected in Step 2.\n\n1. Select a method to exclude repositories.\n\n- **Select Repository**: This option displays a drop-down menu of all the repositories selected in Step 2. You can directly select any repository to exclude it from the scope of the policy.\n\n- **Enter pattern to exclude**: Select a text pattern to be matched for excluding repositories from policy scope.\n\n - **Starts With**: All repositories that start with the mentioned text will be excluded.\n\n - **Ends With**: All repositories that end with the mentioned text will be excluded.\n\n - **Contains**: All repositories that contain the mentioned text will be excluded.\n\n- **File Extension Exclusion**: Select a file extension. All the files with the selected extension are excluded from the policy scope.\n\n- **Directory Exclusion**: Enter a regular expression pattern to match a directory and file path. All file directories and file paths that match the pattern are excluded from the policy scope. All standard regular expressions are accepted, and you can refer to the documentation [here](https://github.com/google/re2/wiki/Syntax) for examples of regular expressions. You can also refer to [this link](https://regex-generator.olafneumann.org/?sampleText=2020-03-12T13%3A34%3A56.123Z%20INFO%20%20%5Borg.example.Class%5D%3A%20This%20is%20a%20%23simple%20%23logline%20containing%20a%20%27value%27.\\&flags=i) to generate regular expressions.\n\n1. Click **Next**.\n\n## Example Scenario[](https://help.nightfall.ai/github/policies/scope#example-scenario)\n\nConsider that you wish to scan all public repositories of your GitHub account with Nightfall. However, there are a few public repositories that were created for testing purposes. These test repositories contain the word \"test\" in their names. You can use the **Repository Exclusion** drop-down menu to choose each repository that contains the word test. However, this task can be cumbersome.\n\nYou can use the **Enter pattern to Exclude** menu with the Contains option and enter the term **test** in the field as shown in the following image.\n\nConsider another scenario in which you wish to include all the repositories but wish to exclude files with the \"cert\" extensions. You can accomplish this as shown in. the following image.\n","2026-08-04T17:13:11.242Z","2026-08-04T18:41:07.455Z","98b2cc9b-db9e-4255-94a2-6cf81490a9b4",[],[],[],"Configure Scope for Confluence | Nightfall Documentation","configure-scope-for-confluence-nightfall-documentation","https://help.nightfall.ai/confluence/policies/scope","Nightfall can monitor all your Confluence spaces for sensitive data. However, you can choose to monitor only specific spaces. Additionally, irrespective of whether you have chosen all the spaces or specific spaces for monitoring, Nightfall allows you to exclude specific pages from being monitored, within the selected spaces. You can configure the required spaces and pages within the spaces on the scope page\n\nTo configure Policy Scope:\n\n1. Click **+ Add Site** and select a Confluence instance.\n\nIf you have configured only a single Confluence site, the configured site is automatically selected and you need not choose from multiple sites. If you wish to monitor multiple Confluence sites, you must create a separate policy for each site.\n\nOnce you choose the site, there are two configurations; **Include In Monitoring** and **Exclude From Monitoring**. The **Include In Monitoring** section allows you to choose specific Confluence Spaces for monitoring. The **Exclude From Monitoring** section is optional and allows you to exclude specific pages from being monitored, from within the selected Spaces.\n\n## Configure Include in Monitoring Section[](https://help.nightfall.ai/confluence/policies/scope#configure-include-in-monitoring-section)\n\nBy default, all the Spaces are selected for monitoring. To choose only a specific set of Space(s) to be monitored, you must click the **Choose Spaces** radio button.\n\nOnce you select the Choose Spaces option, a new search field is displayed. This field lists all the Confluence Spaces configured in the selected Confluence site. You can choose the required Space(s).\n\n## Configure Exclude From Monitoring Section[](https://help.nightfall.ai/confluence/policies/scope#configure-exclude-from-monitoring-section)\n\nThis section allows you to exclude specific page(s) (from within the selected Space(s)) from being monitored by Nightfall for sensitive data. You can skip this section if you wish to monitor all the pages from the selected Space(s).\n\nNightfall lists all the pages from the selected Spaces in the drop-down menu. To exclude specific pages, select the required pages from the drop-down menu.\n","2026-08-04T17:15:30.462Z","2026-08-04T17:15:30.505Z","0cd7eac2-8ec5-4aae-b517-e13881dfd17c",[],[],[],"Configure Routing Rules - SMTP Relay Settings | Nightfall Documentation","configure-routing-rules-smtp-relay-settings-nightfall-documentation","https://help.nightfall.ai/gmail/installation/content_compliance_rules/smtp_relay_settings","# Configure Routing Rules - SMTP Relay Settings\n\nOnce you create the content compliance rules, you must set up the routing rules to configure SMTP relay settings. This ensures that you receive emails only from Nightfall's trusted IP addresses.\n\n## Prerequisites[](https://help.nightfall.ai/gmail/installation/content_compliance_rules/smtp_relay_settings#prerequisites)\n\nIn the Nightfall UI, navigate to **Integrations** from the left navigation bar and click the **Manage** button for the Gmail integration.\n\nAll the headers and expressions required to create the compliance rules are available in the **Installation** section under Gmail settings as displayed in the image below. Keep this screen open to copy/paste the headers as you create the routing rules in Google Workspace. We will refer to this page as the **Gmail settings** page throughout the document.\n\n## Configure Routing Rules[](https://help.nightfall.ai/gmail/installation/content_compliance_rules/smtp_relay_settings#configure-routing-rules)\n\nTo configure routing rules:\n\n1. Login to your Google Workspace with an admin account.\n\n2. Navigate to the admin console.\n\n3. From the left menu, expand **Apps** > **Google Workspace > Gmail.**\n\n4. Scroll down and select **Routing**.\n\n5. Scroll down to the **SMTP relay service** section and click **ADD ANOTHER RULE** (the button can be displayed as **CONFIGURE** if you have not created any SMTP rules).\n\n6. Enter a name for the SMTP rule (the name\"Routing\" is used in this case).\n\n7. Select the **Only accept mail from the specified IP addresses** check box.\n\n8. Click **ADD.**\n\n9. In the **Add Setting** dialog box, enter a description in the **Description** field (\"Nightfall IP\" is used in this case).\n\n10. Navigate to the **Gmail settings** page on the Nightfall UI and copy the value from the **IP Address 1** field, located under the **Routing - SMTP Relay Service** section.\n\n11. Return to the Google Admin Workspace window and paste the copied value in the **Enter IP address/range** field.\n\n12. Click **SAVE**.\n\nThe IP address is added as shown in the following image.\n\n1. Repeat steps 8-12 to add the other two Nightfall IP addresses (In step 10, copy the values under **IP address 2** and I**P address 3** fields).\n\n2. Select the **Require TLS encryption** check box.\n\n3. Click **SAVE**.\n","2026-08-04T18:29:58.597Z","2026-08-04T18:29:58.622Z","78a160b8-6ba0-458e-90e5-1d9cc042c294",[],[],[],"Configure Risk Score for Jira | Nightfall Documentation","configure-risk-score-for-jira-nightfall-documentation","https://help.nightfall.ai/jira/policies/risk_score","# Configure Risk Score for Jira\n\nIn this final stage, you assign a name to the policy, verify your configurations, and create the policy.\n\n1. Enter a name for the policy.\n\n2. (Optional) Enter a description for the policy.\n\n3. Choose the Policy risk score. By default the risk score is set to **Nightfall Risk Score**. You can set it to **Custom Risk score**, and select one of the risk levels, if required. To learn more about Risk scoring, refer to the [Risk Scoring](https://help.nightfall.ai/detection_platform/policies/risk_score#risk-scoring) document.\n\n4. Click **Next**.\n\n5. Verify if all the policy configurations are set up as per your requirements.\n\n6. (Optional) Click **Back** or click on any specific stage to modify any of the policy configurations.\n\n7. Click **Submit**.\n","2026-08-04T17:15:42.010Z","2026-08-04T17:15:42.038Z","3035d2e3-aad5-4fa6-8942-4141ffe1ed86",[],[],[],"Configure Risk Score for Gmail | Nightfall Documentation","configure-risk-score-for-gmail-nightfall-documentation","https://help.nightfall.ai/gmail/policies/risk_score","# Configure Risk Score for Gmail\n\nIn this final stage, you assign a name to the policy, verify your configurations, and create the policy.\n\n1. Enter a name for the policy.\n\n2. (Optional) Enter a description for the policy.\n\n3. Choose the Policy risk score. By default the risk score is set to **Nightfall Risk Score**. You can set it to **Custom Risk score**, and select one of the risk levels, if required. To learn more about Risk scoring, refer to the [Risk Scoring](https://help.nightfall.ai/detection_platform/policies/risk_score#risk-scoring) document.\n\n4. Click **Next**.\n\n5. Verify if all the policy configurations are set up as per your requirements.\n\n6. (Optional) Click back or click on any specific stage to modify any of the policy configurations.\n\n7. Click **Submit.**\n","2026-08-04T18:29:59.487Z","2026-08-04T18:29:59.513Z","a24afdab-b691-4961-9533-f0ef737125ef",[],[],[],"Configure Risk Score for GitHub | Nightfall Documentation","configure-risk-score-for-github-nightfall-documentation","https://help.nightfall.ai/github/policies/risk_score","# Configure Risk Score for GitHub\n\nIn this final stage, you assign a name to the policy, verify your configurations, and create the policy.\n\n1. Enter a name for the policy.\n\n2. (Optional) Enter a description for the policy.\n\n3. Choose the Policy risk score. By default the risk score is set to **Nightfall Risk Score**. You can set it to **Custom Risk score**, and select one of the risk levels, if required. To learn more about Risk scoring, refer to the [Risk Scoring](https://help.nightfall.ai/detection_platform/policies/risk_score#risk-scoring) document.\n\n4. Click **Next**.\n\n5. Verify if all the policy configurations are set up as per your requirements.\n\n6. (Optional) Click back to modify any of the policy configurations.\n\n7. Click **Submit**.\n","2026-08-04T17:13:11.883Z","2026-08-04T18:41:07.712Z","24fbc7d3-40f1-4d55-8d9e-cb9ff9f24fc5",[],[],[],"Configure Risk Score for Confluence | Nightfall Documentation","configure-risk-score-for-confluence-nightfall-documentation","https://help.nightfall.ai/confluence/policies/risk_score","# Configure Risk Score for Confluence\n\nIn this final stage, you assign a name to the policy, verify your configurations, and create the policy.\n\n1. Enter a name for the policy.\n\n2. (Optional) Enter a description for the policy.\n\n3. Choose the Policy risk score. By default the risk score is set to **Nightfall Risk Score**. You can set it to **Custom Risk score**, and select one of the risk levels, if required. To learn more about Risk scoring, refer to the [Risk Scoring](https://help.nightfall.ai/detection_platform/policies/risk_score#risk-scoring) document.\n\n4. Click **Next**.\n\n5. Verify if all the policy configurations are set up as per your requirements.\n\n6. (Optional) Click **Back** or click on any specific stage to modify any of the policy configurations.\n\n7. Click **Submit**.\n","2026-08-04T17:15:32.075Z","2026-08-04T17:15:32.101Z","a8d579aa-8b1b-4a62-868d-0be0d4c01a1c",[],[],[],"Configure Policies in Nightfall for Jira | Nightfall Documentation","configure-policies-in-nightfall-for-jira-nightfall-documentation","https://help.nightfall.ai/jira/policies","# Configure Policies in Nightfall for Jira\n\nDLP policies are a set of rules that include specific conditions, actions, and exceptions that monitor and filter data. These policies also enable you to remediate any leakage of sensitive information from within your organization.\n\n- You can set up policies to scan data that is sent through some or all applications within your organization.\n\n- You can configure policies and choose to not apply them all the time.\n\nBefore you define a policy, or a set of policies, we recommend that you define the objectives of each policy, which can then be fulfilled when you configure the policy.\n\nHere are a few important questions to ask before configuring your policies:\n\n- What data do you plan to monitor?\n\n- Where within the organization do you want to monitor?\n\n- What should be the scope of each policy?\n\n- What conditions must apply for the policy to match?\n\n- What exceptions/exclusions can be allowed?\n\n- What remediation actions should the policy take?\n\nYou can now configure policies on the Jira integration to determine which projects must be monitored, and which ones excluded. You can also automate the remediation actions that you want Nightfall to perform on a policy violation.\n\nConfiguring DLP policies on Jira involves the following steps:\n\n[Jira App Selection](https://help.nightfall.ai/jira/policies/integration)[Configure Scope in Nightfall for JIRA](https://help.nightfall.ai/jira/policies/scope)[Select Detection Rules in Nightfall for JIRA](https://help.nightfall.ai/jira/policies/detection_rules)[Configuring Advanced Settings in Nightfall for JIRA](https://help.nightfall.ai/jira/policies/advanced_settings)[Configure Risk Score for Jira](https://help.nightfall.ai/jira/policies/risk_score)[Manage Jira Events](https://help.nightfall.ai/jira/policies/events)\n","2026-08-04T17:12:35.345Z","2026-08-04T18:28:55.043Z","82665607-d76e-463a-bb69-0239368520d1",[],[],[],"Configure Policies for Zendesk | Nightfall Documentation","configure-policies-for-zendesk-nightfall-documentation","https://help.nightfall.ai/zendesk/policies","DLP policies are a set of rules that include specific conditions, actions, and exceptions that monitor and filter data. These policies also enable you to remediate any leakage of sensitive information from within your organization.\n\n- You can set up policies to scan data that is sent through some or all applications within your organization.\n\n- You can configure policies and choose to not apply them all the time.\n\nBefore you define a policy, or a set of policies, we recommend that you define the objectives of each policy, which can then be fulfilled when you configure the policy.\n\nHere are a few important questions to ask before configuring your policies:\n\n- What data do you plan to monitor?\n\n- Where within the organization do you want to monitor?\n\n- What should be the scope of each policy?\n\n- What conditions must apply for the policy to match?\n\n- What exceptions/exclusions can be allowed?\n\n- What remediation actions should the policy take?\n\nYou can now configure policies on the Zendesk integration to determine which instances and files must be monitored, and which ones excluded. You can also automate the remediation actions that you want Nightfall to perform on a policy violation.\n\nYou can now set up policies on Nightfall that will be applied on the Zendesk integration, and monitor data on Zendesk for policy violations.\n\nThe following documents help you create Policies specifically for the Zendesk integration.\n\n[Zendesk App Selection](https://help.nightfall.ai/zendesk/policies/integration)[Configure Scope for Zendesk](https://help.nightfall.ai/zendesk/policies/scope)[Configure Detection Rules for Zendesk DLP](https://help.nightfall.ai/zendesk/policies/detection_rules)[Configure Advanced Settings in Zendesk](https://help.nightfall.ai/zendesk/policies/advanced_settings)[Risk Score for Zendesk](https://help.nightfall.ai/zendesk/policies/risk_score)[Manage Zendesk Events](https://help.nightfall.ai/zendesk/policies/events)\n","2026-08-04T17:12:48.870Z","2026-08-04T18:28:51.908Z","3c40217e-7ab4-4026-a4fa-46f38fd99abd",[],[],[],"Configure Policies for Notion | Nightfall Documentation","configure-policies-for-notion-nightfall-documentation","https://help.nightfall.ai/notion/policies","DLP policies are a set of rules that include specific conditions, actions, and exceptions that monitor and filter data. These policies also enable you to remediate any leakage of sensitive information from within your organization.\n\n- You can set up policies to scan data that is sent through some or all applications within your organization.\n\n- You can configure policies and choose to not apply them all the time.\n\nBefore you define a policy, or a set of policies, we recommend that you define the objectives of each policy, which can then be fulfilled when you configure the policy.\n\nHere are a few important questions to ask before configuring your policies:\n\n- What data do you plan to monitor?\n\n- Where within the organization do you want to monitor?\n\n- What should be the scope of each policy?\n\n- What conditions must apply for the policy to match?\n\n- What exceptions/exclusions can be allowed?\n\n- What remediation actions should the policy take?\n\nYou can now configure policies on the Notion integration to determine which instances and files must be monitored, and which ones excluded. You can also automate the remediation actions that you want Nightfall to perform on a policy violation.\n\nYou can now set up policies on Nightfall that will be applied on the Notion integration, and monitor data on Notion for policy violations.\n\nThe following documents help you create Policies specifically for the Notion integration.\n\n[Notion App Selection](https://help.nightfall.ai/notion/policies/integration)[Configure Detection Rules for Notion](https://help.nightfall.ai/notion/policies/detection_rules)[Configure Advanced Settings in Zendesk](https://help.nightfall.ai/zendesk/policies/advanced_settings)[Risk Score for Notion](https://help.nightfall.ai/notion/policies/risk_score)[Manage Notion Events](https://help.nightfall.ai/notion/policies/events)\n","2026-08-04T17:12:50.308Z","2026-08-04T18:28:52.842Z","1d9e46b6-bebb-4162-9462-81d9e30b05a1",[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],{"_74":2547,"_2548":2549,"_2550":-5,"_70":2551,"_2552":2553,"_129":2554,"_131":2555,"_22":80,"_24":25},"Customer Support","supportName","Nightfall AI Agent","supportLogo","External support for customer inquiries and issues","defaultTriageChannelId","C0BMQ119FCJ","2026-08-03T16:57:14.215Z","2026-08-13T19:39:27.964Z","user",{"_2559":2560,"_2558":27},"anonymous","uid","anon_1791017097010_yqaix3z","apiKey","AIzaSyDCG_xdkCxQ0mNJT1LKg2XIf0cHJwSISYU","authDomain","unthread"]

Detection Platform FAQs | Nightfall Documentation