# Getting "This action requires elevated permissions" error when creating an app

**URL:** <https://community.hubspot.com/t/getting-this-action-requires-elevated-permissions-error-when-creating-an-app/87586>\
**Category:** APIs & Integrations\
**Tags:** oauth, webhooks\
**Created:** [August 16, 2023, 6:29am UTC](https://community.hubspot.com/t/getting-this-action-requires-elevated-permissions-error-when-creating-an-app/87586 "2023-08-16T06:29:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![FSAdmin](https://avatars.discourse-cdn.com/v4/letter/f/b4bc9f/32.png) [@FSAdmin](https://community.hubspot.com/u/FSAdmin)\
**Post date:** [August 16, 2023, 6:29am UTC](https://community.hubspot.com/t/getting-this-action-requires-elevated-permissions-error-when-creating-an-app/87586/1 "2023-08-16T06:29:39Z")

</div>

I am trying to create a public app within Hubspot. I just started out by adding some basic details like the app name, logo, but all the buttons to Save changes or Delete the app are greyed out

On hovering, it says “This action requires elevated permissions” Can someone please help?

 ![Screenshot 2023-08-16 at 11.51.05 AM.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/f/b/fbbbb2f0ee5b7f9aac0df33be96f20b7fe3a2b48.png)

---

<div class="post-metadata">

**Author:** ![coldrickjack](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/coldrickjack/32/6684_2.png) [@coldrickjack](https://community.hubspot.com/u/coldrickjack)\
**Post date:** [August 16, 2023, 9:33am UTC](https://community.hubspot.com/t/getting-this-action-requires-elevated-permissions-error-when-creating-an-app/87586/2 "2023-08-16T09:33:44Z")

</div>

Hi @FSAdmin,

I’m not sure why this is occuring as if you’ve created a fresh new developer account you should automatically have super admin privledges. I helped a similar member of our community with this exact same issue last week - the [solution](https://community.hubspot.com/t5/APIs-Integrations/Unable-to-create-app-and-test-account/td-p/833059) was to simply setup a new developer account using the same email address and that resolved the issues.
