# Deny PLUS redirect in Action Triggers

**URL:** <https://community.auth0.com/t/deny-plus-redirect-in-action-triggers/170287>\
**Category:** Get Help\
**Tags:** quickstarts-backend-api, sdks-quickstarts\
**Created:** [January 25, 2025, 4:18pm UTC](https://community.auth0.com/t/deny-plus-redirect-in-action-triggers/170287 "2025-01-25T16:18:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sumansaurav](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sumansaurav/32/70627_2.png) [@sumansaurav](https://community.auth0.com/u/sumansaurav)\
**Post date:** [January 27, 2025, 4:06pm UTC](https://community.auth0.com/t/deny-plus-redirect-in-action-triggers/170287/2 "2025-01-27T16:06:01Z")

</div>

The most correct and complete approach would be:

```auto
exports.onExecutePostLogin = async (event, api) => {
  return api.access.deny('Deny example.');
};

```

Here’s why:

1. You should always `return` the `api.access.deny()` call. This ensures:

- The action stops executing immediately
- No token is issued
- The denial is properly propagated

1. Trying to use `api.redirect.sendUserTo()` after `api.access.deny()` won’t work because:

- The deny action terminates the authentication flow
- Any code after the deny won’t execute
- The redirect would never be reached

1. If you need custom error handling, you should handle this on the client side. Here’s how:

```auto
// In your NextJS app or whatever framwork you using. Customize accordiingly
const { handleRedirectCallback } = useAuth0();

try {
  await handleRedirectCallback();
} catch (error) {
//Customize based on what you see in response also check for error_description in query param when auth0 redirect
  if (error.error === 'access_denied' || error.error === 'unauthorized') { 
    // Redirect to your custom error page
    router.push('/access-denied');
  }
}

```

If you really need custom redirection on denial, you could use Auth0’s Error Pages customization:

1. Go to Auth0 Dashboard → Settings → Tenant Settings → General → Error Pages
2. Choose “Custom” error page
3. Set your URL (e.g., `https://my-app.exampleco.com/access-denied`)

This would handle all authentication errors, including denials from your Actions, in a more standard way.

The approach of redirecting to logout isn’t recommended because:

1. It’s unnecessary - no session was created to logout from

---

_[View the full topic](https://community.auth0.com/t/deny-plus-redirect-in-action-triggers/170287)._