# User Administration

**URL:** <https://community.noloco.io/t/user-administration/1431>\
**Category:** Ask for Help\
**Created:** [November 12, 2024, 9:20am UTC](https://community.noloco.io/t/user-administration/1431 "2024-11-12T09:20:34Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pablo10](https://avatars.discourse-cdn.com/v4/letter/p/779978/32.png) [@Pablo10](https://community.noloco.io/u/Pablo10)\
**Post date:** [November 12, 2024, 9:20am UTC](https://community.noloco.io/t/user-administration/1431/1 "2024-11-12T09:20:34Z")

</div>

Hi All,

I have a client with 50+ active users and growing, and I would like to transition the management of these users to them.

Ideally, I would like them to be able to execution the following actions:  
• Add Users  
• Remove Users  
• Send Invite Reminders  
• Assign Roles (but not control of role setup/admin)  
• Password resets

My core data is contained in AirTable, but my users are set up in Noloco.

Any advice is greatly appreciated.

P.

---

<div class="post-metadata">

**Author:** ![carlos](https://avatars.discourse-cdn.com/v4/letter/c/ecae2f/32.png) [@carlos](https://community.noloco.io/u/carlos)\
**Post date:** [November 12, 2024, 2:55pm UTC](https://community.noloco.io/t/user-administration/1431/2 "2024-11-12T14:55:13Z")

</div>

Hi @Pablo10,

The client should be a **team admin** to manage users and perform those actions in the app. It’s not possible with a different user role.

> **[User Management | Noloco](https://guides.noloco.io/users-and-permissions/user-management)**
>
> Manage your existing users and invite new users to your app from the User Management tab

Hope this helps!

---

<div class="post-metadata">

**Author:** ![Pablo10](https://avatars.discourse-cdn.com/v4/letter/p/779978/32.png) [@Pablo10](https://community.noloco.io/u/Pablo10)\
**Post date:** [November 13, 2024, 8:57am UTC](https://community.noloco.io/t/user-administration/1431/3 "2024-11-13T08:57:17Z")

</div>

Thanks, @carlos; I was aware of this.

I assume there is no way to grant access to User Management while restricting access to ‘Build Mode’.

P.

---

<div class="post-metadata">

**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\
**Post date:** [November 13, 2024, 9:25am UTC](https://community.noloco.io/t/user-administration/1431/4 "2024-11-13T09:25:01Z")

</div>

@Pablo10 - if you make their role a “Data Admin” (access all data) but not a “Builder” (Modify app) you should be able to do exactly that

 ![image](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/1X/bceb958a116c699e9313b0189e575e5171f92ff7.png)

---

<div class="post-metadata">

**Author:** ![Pablo10](https://avatars.discourse-cdn.com/v4/letter/p/779978/32.png) [@Pablo10](https://community.noloco.io/u/Pablo10)\
**Post date:** [November 13, 2024, 9:39am UTC](https://community.noloco.io/t/user-administration/1431/5 "2024-11-13T09:39:04Z")

</div>

Excellent Darragh, thanks.

---

<div class="post-metadata">

**Author:** ![Pablo10](https://avatars.discourse-cdn.com/v4/letter/p/779978/32.png) [@Pablo10](https://community.noloco.io/u/Pablo10)\
**Post date:** [November 13, 2024, 9:57am UTC](https://community.noloco.io/t/user-administration/1431/6 "2024-11-13T09:57:35Z")

</div>

Hi @darragh

I have tested this, and it is not exactly what I need.

In simple terms, I need a client role type that allows them to manage their users but will restrict access to any other Noloco menus, such as data, workflows, billing, help, etc.

Any way to do this?

P.

---

<div class="post-metadata">

**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\
**Post date:** [November 13, 2024, 10:12am UTC](https://community.noloco.io/t/user-administration/1431/7 "2024-11-13T10:12:15Z")

</div>

Gotcha - you should still be able to do this, the only thing they won’t be able to do is modify the **role**

So long as the user has access to create user records (with permissions)

The workaround is the have another field that will represent the role the user should have, and then using a workflow to assign the correct role.

If each user should be created with the same role, then you won’t need that workaround