# Guardian-push restricting me from editing app config

**URL:** <https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299>\
**Category:** Get Help\
**Tags:** push-via-auth0-guardian-factor, mfa\
**Created:** [November 11, 2025, 6:49am UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299 "2025-11-11T06:49:50Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![NoahMo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/noahmo/32/77399_2.png) [@NoahMo](https://community.auth0.com/u/NoahMo)\
**Post date:** [November 11, 2025, 6:49am UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/1 "2025-11-11T06:49:50Z")

</div>

I didn’t turn on MFA configuration. Somehow when i change CORS configuration, it keeps the following error:

**Error!**  
Please upgrade your subscription to use the async approval notification channels: guardian-push

how do i solve it?

---

<div class="post-metadata">

**Author:** ![alberto.leal](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/alberto.leal/32/70995_2.png) [@alberto.leal](https://community.auth0.com/u/alberto.leal)\
**Post date:** [November 11, 2025, 7:39am UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/2 "2025-11-11T07:39:52Z")

</div>

I have same issue when I try to change callback url, it stared today I think

---

<div class="post-metadata">

**Author:** ![james30](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/james30/32/66686_2.png) [@james30](https://community.auth0.com/u/james30)\
**Post date:** [November 11, 2025, 2:51pm UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/3 "2025-11-11T14:51:18Z")

</div>

I’m just trying to change my logout URL and I’m getting the same error. I’ve confirmed that all MFA settings are disabled in my tenant.

---

<div class="post-metadata">

**Author:** ![matthew.hartz](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/matthew.hartz/32/12776_2.png) [@matthew.hartz](https://community.auth0.com/u/matthew.hartz)\
**Post date:** [November 11, 2025, 4:21pm UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/4 "2025-11-11T16:21:14Z")

</div>

same. Trying to update callback URLs

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [November 11, 2025, 4:24pm UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/6 "2025-11-11T16:24:35Z")

</div>

Hi everyone!

I will investigate the issue and come back with an update ASAP! Thanks for letting us know about the issue that you are experiencing!

By any chance, do any of you have any actions bounded which would enforce guardian MFA?

Kind Regards,  
Nik

---

<div class="post-metadata">

**Author:** ![james30](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/james30/32/66686_2.png) [@james30](https://community.auth0.com/u/james30)\
**Post date:** [November 11, 2025, 4:41pm UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/7 "2025-11-11T16:41:25Z")

</div>

I’m using one post login action that does not to my knowledge enforce guardian MFA. It makes a call out to my server to check for pending invitations and potentially sets the user app metadata.

---

<div class="post-metadata">

**Author:** ![surfer789](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/surfer789/32/70813_2.png) [@surfer789](https://community.auth0.com/u/surfer789)\
**Post date:** [November 11, 2025, 5:14pm UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/8 "2025-11-11T17:14:09Z")

</div>

We’ve encountered the same issue. We do have enterprise plan.

---

<div class="post-metadata">

**Author:** ![aaron6](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/aaron6/32/70921_2.png) [@aaron6](https://community.auth0.com/u/aaron6)\
**Post date:** [November 11, 2025, 6:53pm UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/9 "2025-11-11T18:53:02Z")

</div>

We are also seeing this issue.

---

<div class="post-metadata">

**Author:** ![gautam](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/gautam/32/74277_2.png) [@gautam](https://community.auth0.com/u/gautam)\
**Post date:** [November 11, 2025, 8:50pm UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/10 "2025-11-11T20:50:49Z")

</div>

Running into the same problem when trying to update the callback URI on an existing SPA. Any updates?

---

<div class="post-metadata">

**Author:** ![Elaskanator](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/elaskanator/32/73264_2.png) [@Elaskanator](https://community.auth0.com/u/Elaskanator)\
**Post date:** [November 11, 2025, 8:52pm UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/11 "2025-11-11T20:52:02Z")

</div>

I am also having this issue which is preventing me from saving any changes to my Application in the Dashboard.  
I have never touched any of these features, and this issue seems to have begun now that my free trial period has ended (today). This continues even after manually going to the “Multi-factor Auth” page and clicking Save with everything (already) disabled there.

---

<div class="post-metadata">

**Author:** ![deedarby](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/deedarby/32/74493_2.png) [@deedarby](https://community.auth0.com/u/deedarby)\
**Post date:** [November 11, 2025, 9:05pm UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/12 "2025-11-11T21:05:55Z")

</div>

We are also having this issue on any application or machine created Nov 8th. (network panel shows 403) when any edit is made, haven’t been able to submit a ticket from the support center either (might be related)

---

<div class="post-metadata">

**Author:** ![DBDEric](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dbderic/32/77406_2.png) [@DBDEric](https://community.auth0.com/u/DBDEric)\
**Post date:** [November 11, 2025, 10:32pm UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/13 "2025-11-11T22:32:33Z")

</div>

Same issue happening here. Also, like others, I cannot submit a support ticket about the issue.

---

<div class="post-metadata">

**Author:** ![aaron6](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/aaron6/32/70921_2.png) [@aaron6](https://community.auth0.com/u/aaron6)\
**Post date:** [November 11, 2025, 10:47pm UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/14 "2025-11-11T22:47:17Z")

</div>

This issue is preventing us from deploying an update for a customer that is due tomorrow. An update on potential resolution would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [November 11, 2025, 11:14pm UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/15 "2025-11-11T23:14:14Z")

</div>

Hi everyone,

Just for further confirmation regarding the issue, are you receiving the aforementioned error when trying to update an application only in the Auth0 Dashboard, Auth0 Deploy CLI(if you are using it) or both?

Additionally, are you able to save the tenant configuration if you disable the **Cross-Origin Authentication** option for your application?

For the applications that you cannot configure, do you have the _**Client Initiated Backchannel Authentication (CIBA)**_ enabled by any chance?

If you are using Deploy CLI, does your application configuration include the following flag:

```auto
async_approval_notification_channels: - guardian-push

```

If this flag is included in your configuration, I would recommend disabling/removing it, let me know if that changes anything regarding the matter.

Kind Regards,  
Nik

---

<div class="post-metadata">

**Author:** ![surfer789](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/surfer789/32/70813_2.png) [@surfer789](https://community.auth0.com/u/surfer789)\
**Post date:** [November 11, 2025, 11:35pm UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/16 "2025-11-11T23:35:48Z")

</div>

Hi Nik,

All we did is try to rename our app name under Auth0 Dashboard and receiving the following error:  
**`Error!`** `Please upgrade your subscription to use the async approval notification channels: guardian-push`

---

<div class="post-metadata">

**Author:** ![DBDEric](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dbderic/32/77406_2.png) [@DBDEric](https://community.auth0.com/u/DBDEric)\
**Post date:** [November 11, 2025, 11:50pm UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/17 "2025-11-11T23:50:53Z")

</div>

I’m in the Auth0 Dashboard, trying to save my Single Page Application. I do not currently have ‘Allow Cross-Origin Authentication’ enabled. If I load the Settings page and click Save with making no changes, I even receive the error.

---

<div class="post-metadata">

**Author:** ![aaron6](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/aaron6/32/70921_2.png) [@aaron6](https://community.auth0.com/u/aaron6)\
**Post date:** [November 12, 2025, 12:39am UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/18 "2025-11-12T00:39:55Z")

</div>

> [@nik.baleca](#):
>
> `async_approval_notification_channels`

using the CLI worked after removing the async\_approval\_notification\_channels entries.

---

<div class="post-metadata">

**Author:** ![leigh.gordon](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/leigh.gordon/32/71521_2.png) [@leigh.gordon](https://community.auth0.com/u/leigh.gordon)\
**Post date:** [November 12, 2025, 1:10am UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/19 "2025-11-12T01:10:04Z")

</div>

I can confirm that I am also randomly receiving this error today when simply trying to rename an application:

`Error!`  
`Please upgrade your subscription to use the async approval notification channels: guardian-push`

I have not to my knowledge ever knowingly or intentionally enabled guardian-push on anything, it simply broke today when it was previously working.

EDIT: Further to this…

I had created all of the affected applications through the web interface some time ago, not using the API/CLI.

If I now query the applications through `https://TENANT.REGION.auth0.com/api/v2/clients` I can see that they all contain the following:

```auto
 "async_approval_notification_channels": [
            "guardian-push"
],

```

This is despite never configuring them (in fact in many cases, the applications are pretty much completely default, i.e. I clicked Create and then Next/Finish, without further configuring them).

If I now create a new application, it does _not_ contain this `async_approval_notification_channels` section.

So I can only assume that _something_ behind the scenes has modified these already existing applications to add this `guardian-push` to them.

Question:  
Can these applications be fixed through the UI to remove this config (which I did not add), or do I need to try and patch them all through the API to remove this?

EDIT2:

If I update the application through the API as follows, I am then able to edit the application through the web UI again as before:

PATCH `https://TENANT.REGION.auth0.com/api/v2/clients/CLIENT_ID`

Body: `{"async_approval_notification_channels": null}`

I’d like to re-iterate though, that I did not do anything to enable this in the first place.

---

<div class="post-metadata">

**Author:** ![phong.le](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/phong.le/32/60908_2.png) [@phong.le](https://community.auth0.com/u/phong.le)\
**Post date:** [November 12, 2025, 4:21am UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/20 "2025-11-12T04:21:15Z")

</div>

Hi everyone, @leigh.gordon@nik.baleca I am trying to update the Auth0 setting by using Management API, but it returned me the 401 invalid token issue every time even I already used the latest token from Management API. Do you know what happen with Auth0 today?

---

<div class="post-metadata">

**Author:** ![Soufian](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/soufian/32/77419_2.png) [@Soufian](https://community.auth0.com/u/Soufian)\
**Post date:** [November 12, 2025, 12:02pm UTC](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299/21 "2025-11-12T12:02:09Z")

</div>

I have a fresh account updated to a paid plan today, can’t update any of my apps for the same reason. Turned it on and off in the security tab but no luck

[Next page](https://community.auth0.com/t/guardian-push-restricting-me-from-editing-app-config/194299.md?page=2)
