# API keys - administrator ability to delete, create, update

**URL:** <https://forum.dimagi.com/t/api-keys-administrator-ability-to-delete-create-update/8294>\
**Category:** Developers\
**Created:** [July 5, 2021, 11:19am UTC](https://forum.dimagi.com/t/api-keys-administrator-ability-to-delete-create-update/8294 "2021-07-05T11:19:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![erobinson](https://dimagi.b-cdn.net/user_avatar/forum.dimagi.com/erobinson/32/2652_2.png) [@erobinson](https://forum.dimagi.com/u/erobinson)\
**Post date:** [July 5, 2021, 11:19am UTC](https://forum.dimagi.com/t/api-keys-administrator-ability-to-delete-create-update/8294/1 "2021-07-05T11:19:05Z")

</div>

Is there a way in the UI for an admin of a project space to create or delete API keys for user accounts? e.g. If an API key is known to be compromised, what is the process for an administrator to revoke / recreate it or is it left up to individual web users?

---

<div class="post-metadata">

**Author:** ![Simon\_Kelly](https://dimagi.b-cdn.net/user_avatar/forum.dimagi.com/simon_kelly/32/494_2.png) [@Simon\_Kelly](https://forum.dimagi.com/u/Simon_Kelly)\
**Post date:** [July 6, 2021, 8:28am UTC](https://forum.dimagi.com/t/api-keys-administrator-ability-to-delete-create-update/8294/2 "2021-07-06T08:28:37Z")

</div>

Hi Ed

If you are a superuser you can do it via the Django Admin site: [https://my.commcare.org/admin/users/hqapikey/](https://my.commcare.org/admin/users/hqapikey/)

Otherwise there is a way to remove a different user's API Key.

---

<div class="post-metadata">

**Author:** ![erobinson](https://dimagi.b-cdn.net/user_avatar/forum.dimagi.com/erobinson/32/2652_2.png) [@erobinson](https://forum.dimagi.com/u/erobinson)\
**Post date:** [July 6, 2021, 10:01am UTC](https://forum.dimagi.com/t/api-keys-administrator-ability-to-delete-create-update/8294/3 "2021-07-06T10:01:29Z")

</div>

Great, I suspected it may be done via Django admin, I just hadn't had the time to go through everything to confirm, thanks Simon!
