When to use this rule
You want a catch-all rule that covers every not-permitted app, not just the ones you've created specific redirect rules for
You want to send a clear signal that accounts on not-permitted apps should be removed after a new signup has been detected
You want your team alerted whenever someone signs up for a not-permitted app, regardless of which one it is
Key distinction: This is an Account rule that uses the Approval Status condition rather than targeting a specific app. That means it automatically applies to any app you've marked as Not Permitted - including apps you mark in the future. You don't need to update this rule when you add new apps to your not-permitted list.
Prerequisite: You need to have set approval statuses on the relevant apps before this rule will work. If you haven't done that yet, see Define your SaaS landscape.
How to set it up
Go to Automations → Rules in the left nav
Click Create New Rule
Select the Account tile
Click Add Condition, select Approval Status, and set it to Not Permitted
Add your actions:
Nudge the end user to delete their account
Action: Nudge the end user
Click Add Action → Nudge
Select Request account deletion
The user receives a message explaining that the app isn't permitted by your organization and asking them to delete their account. Like all nudges, it's a request - it doesn't force the account to be deleted or block access.
Alert your team that someone signed up for a not-permitted app
Action: Email alert (to you or a team member)
Click Add Action → Email
Enter recipient email addresses
Add multiple recipients by adding additional email actions
Action: Slack channel alert (follow the same instructions for Teams channel alerts)
Click Add Action → Slack Channel
Select the channel you want to send the alert to
Add multiple channels by adding additional Slack channel actions
Action: Slack user alert (follow the same instructions for Teams user alerts)
Click Add Action → Slack User
Select the user you want to send the alert to
Add multiple users by adding additional Slack user actions
Action: Webhook (use this to surface an alert to a SIEM tool or ticketing tool like Jira)
Click Add Action → Webhook
Paste in the webhook URL
Add multiple webhooks by adding additional webhook actions
Once you're all set make sure to click the Save rule button.
How this works with your rule to alert for new accounts and redirect users away from not-permitted apps
A rule to alert for new accounts and redirect users away from not-permitted apps handles specific not-permitted apps where you have an approved alternative to recommend. It sends a nudge saying "use this instead."
Whereas, this request account deletion rule is the safety net. It catches every not-permitted app - including ones you haven't created a specific redirect rule for - and sends a nudge asking the user to delete the account.
If an app triggers both rules (for example, someone signs up for ChatGPT and you have both a redirect rule pointing to Gemini and this blanket rule), the user receives both nudges. That's fine - one says "use this alternative" and the other says "delete the account you just created." The messaging reinforces the same outcome.
What happens after the rule fires
When someone creates a new account for a not-permitted app:
The user receives a nudge via email/Slack/Teams asking them to delete the account
Your team gets an alert (email, Slack/Teams, or webhook - depending on how you configured it)
You can check the user's nudge response in Automations → Nudge History to see whether they confirmed the deletion, declined, or haven't responded yet
If a user doesn't respond or declines, that's your cue to follow up directly. The nudge is a first touch, not the only enforcement mechanism.
Considerations
Hold off on the nudge action if you haven't communicated Nudge Security to your workforce yet. Start with alerts only. An account deletion request from a tool they've never heard of is more likely to generate confusion than compliance. Add the nudge once you've prepared your workforce.
This rule only fires for new accounts going forward. It won't retroactively nudge people who already had accounts on not-permitted apps before you created the rule. For existing accounts, you can send nudges manually from the app's record.
The rule automatically picks up new not-permitted apps. Because it uses the Approval Status condition rather than targeting specific apps, any app you mark as Not Permitted in the future is immediately covered. No rule updates needed.
"Delete account" is a request, not an action. Nudge Security asks the user to delete their account - it doesn't delete it for them or revoke access. If the user ignores the nudge, the account still exists. You'll need a follow-up process for non-responders.
Tips
This is the kind of rule you set up once and leave running - it scales automatically as you update your approval statuses
Pair it with the browser extension for pre-signup intervention. The extension can show a warning when someone visits the login page of a not-permitted app, before they create an account. This rule handles the cases where they sign up anyway.
Review nudge responses regularly in Automations → Nudge History. A pattern of non-responses on a particular app might mean employees don't have a good alternative - that's useful signal for your approval decisions