Permissions overview

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

Self-hosted

What do you need help with?

Hello everyone !

I’m trying to understand role-based permission and read this docs : Permissions overview ( Roles on Free and Premium plans and Role-based permission on Advanced and Enterprise plans)
Let’s say I have a project with a database that contains a table with a form view. I just need to allow my users to answer the form and nothing else.
I know there are 2 ways to protect forms right ? Share the public link and / or adding a global password on top of.

But in my case, I want to use multiple passwords (one for each user) and only give access to form for these users. Ideally, by answering it fills in a column in table like “Collaborators” does.

For now to do that, I need to invite users to join the project giving them a role listed (in doc link). By reading each role, I understand that way the user will have access to more than just answering the form. Am I wrong ? If not, which role is the best fit for my case please ? I don’t want the users to be able to access other views than form (neither form answers).
I’m not sure the issue could be resolved by using entreprise plan on self-hosted. is it ?

At the moment, there wouldn’t be a way to do exactly what you want. Permissions cannot be set at a view level but at a table level. Meaning all views inside that table can be accessed (that are set to collaborative). Setting individual passwords for a shared view is also not possible.

If you need the collaborator field to be set, this means that to populate that field, it would require that user to be a member of your workspace to be a visible option to select as a collaborator. However, if a link field to a different table called “users” where you add each user to that table and then select them as a record inside that linked field would suffice, you could potentially solve this use case through building it out in the app builder.

Hi, thanks for your answer. I will consider the solution you mentioned.