Allow user(s) to manage dropdown options - Best Practice

[Community Alums]

Looking for some opinions on how others have handled the following requirement.

My facilities team wants a new catalog item to handle Facilities Requests.  Within the item, they want a category dropdown but they want to be able to manage the options (add/edit, etc...).  

In the past, I'd just make it a choice list and have them submit a request to my team to add the choice but it would be nice to get out of the business of managing other departments processes.

I was thinking of extending a table (TBD) that would store the categories and then adding a module in the Navigator that allows them to add/edit the records (since they have access to the Platform UI). 

Any other ideas?  What table should I extend?

[jonsan09]

I've run into some similar in the past. I went down the record producer route, allowing to create or remove records for choice list.  This also insured they only need to fill in their relevant information and the record producer took care of all the other needed record fields, in my case it was for sys_choice table. Then I locked down the record producer to the specific users.