Q: Security for individual endpoint
Since you don't have yet a published roadmap yet, I'd like to ask your plans about this security feature:
Right now, when authorize a secret key it gets access to all endpoints, for example with "books" provides access to endpoint POST to create a new book, or GET to read all books inventory.
However, it is important for each secret key to select permissions only specific endpoints. Here are some examples with "users" table (instead of books):
- one secret key is allowed to list all users, but not create or edit users (like read permissions).
- one secret key is allowed to search for a specific user match, but not list all users (to verify password)
- one secret key is allowed to edit users, but not create new ones (like password reset)
- one secret key can create users (administrator).
I'm aware it's a big request that takes long...

Riya_NoCodeBackend
Sep 25, 2025A: Hi koenigworks9,
We are OPEN to ANY feedback or feature suggestions you have. You can email our support and they check and analyze those further. And we have implemented a TON of new features in last 1 year based on the community feedback (see our 'Updates from NoCodeBackend' section above).
Regarding your ask on Security for individual endpoint, I totally get it and it actually makes sense when you want to restrict users to execute certain endpoints. I have already passed this feedback to our team. I will definitely update you once we have some decisions on it.
Thanks
Riya

Verified purchaser
Thank you for your response, YES, I have seen your good updates based on feedback, since I had purchased your product T3 :-) Notice my comment regarding roadmap was just a fact (never a critic): many applications don't publish an open roadmap to "keep under business control" and not open "internet's free will". I do that myself as well, so I understand the reasons behind. Best regards an keep up!
Awesome 😃🙌🏼