# Verba: Restrict some of the front end functionality to admin only **URL:** \ **Category:** Support\ **Created:** [June 5, 2024, 2:49pm UTC](https://forum.weaviate.io/t/verba-restrict-some-of-the-front-end-functionality-to-admin-only/2627 "2024-06-05T14:49:09Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![jaydcrowe1989](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/jaydcrowe1989/32/2634_2.png) [@jaydcrowe1989](https://forum.weaviate.io/u/jaydcrowe1989)\ **Post date:** [June 5, 2024, 2:49pm UTC](https://forum.weaviate.io/t/verba-restrict-some-of-the-front-end-functionality-to-admin-only/2627/1 "2024-06-05T14:49:09Z")
### Description Hi, I was wanting to lock down some of the functionality on the front end. For example hiding the Documents tab unless you are logged in as an admin. I understand that out of the box you can restrict access but I was wondering if I could only do it for certain features? ---
**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\ **Post date:** [June 5, 2024, 10:35pm UTC](https://forum.weaviate.io/t/verba-restrict-some-of-the-front-end-functionality-to-admin-only/2627/2 "2024-06-05T22:35:41Z")
Hi! Welcome to our community. 🤗 this in on our console, right? Can you point me exactly where is this? Thanks! ---
**Author:** ![jaydcrowe1989](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/jaydcrowe1989/32/2634_2.png) [@jaydcrowe1989](https://forum.weaviate.io/u/jaydcrowe1989)\ **Post date:** [June 5, 2024, 10:51pm UTC](https://forum.weaviate.io/t/verba-restrict-some-of-the-front-end-functionality-to-admin-only/2627/3 "2024-06-05T22:51:26Z")
Thank you for the reply. I should have been more specific and said this is the example chatbot project Verba. It is awesome and exactly what i am after. What I would like to do now is put this into a production environment, upload my documents but then, restrict the add documents button and page etc. to be behind a logged in user. I know there is a condition that hides the button for production but i want to allow certain people to add documents. I have looked into implementing this as a custom solution on top of the project but I was wondering if there was anything out of the box for this please? ---
**Author:** ![Arturo\_Zambrano](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/arturo_zambrano/32/1735_2.png) [@Arturo\_Zambrano](https://forum.weaviate.io/u/Arturo_Zambrano)\ **Post date:** [June 13, 2024, 4:29am UTC](https://forum.weaviate.io/t/verba-restrict-some-of-the-front-end-functionality-to-admin-only/2627/4 "2024-06-13T04:29:08Z")
I’m really interested in this response, DudaNogueira. ---
**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\ **Post date:** [June 15, 2024, 12:22am UTC](https://forum.weaviate.io/t/verba-restrict-some-of-the-front-end-functionality-to-admin-only/2627/5 "2024-06-15T00:22:22Z")
Hi @jaydcrowe1989 and @Arturo_Zambrano ! Thanks for the interest 🙂 Verba uses FastApi, so implementing robust auth is some code away. I believe the best path here is to state that as a feature request on it’s repo: > **[GitHub - weaviate/Verba: Retrieval Augmented Generation (RAG) chatbot powered...](https://github.com/weaviate/Verba)** > > Retrieval Augmented Generation (RAG) chatbot powered by Weaviate - weaviate/Verba With that we can measure popular features, and also channel all discussions around it. One “hacky” and easier way I see right now to overcome this scenario would be to allow to run a Verba Instance on a READONLY mode. With that you can spin an instance that will be readonly for the general use, and then a second one, with `READONLY` set to false, even temporarily only for the user with access, that could be used to import data. Please, feel free to open the feature request in Verba repo. Thanks!