Skip to main content
Question

User Role Permission not behaving correctly

  • March 14, 2019
  • 0 replies
  • 115 views
Hi,

Does anyone know why a specific user can still edit certain fields that should be only in View Mode?

So, I created a role that limits it to Edit specific fields only. I, an Admin of the application, used the Test As Functionality of Quick Base to see if the configured role was setup correctly. Upon checking, the created role is behaving correctly. However, when I test as a user who has the said role, the user can still edit fields that should be in View mode only. The said user has only the said role assigned to him. He also reported the issue to me indicating that he should not be able to edit certain fields. 
This topic has been closed for replies.

How sure are you that the user is only in one Role. Have you searched their name in the Users list for that app?
  • KingslySamuel
  • Quickbase Alumni
  • March 14, 2019
I suspect this would make any difference if you had set it all up correctly. But, still just out of curiosity, what does the permission (under 'Advanced)' say when you right click on the field and look at its properties? For the role you mention, does it say "view" or "modify"?
  • ArchiveUser
  • Author
  • Quickbase Alumni
  • April 2, 2019
Hi Kingsly,

I can confirm that the permission set for that field is "View" for that specific role. I am not sure why it is not behaving correctly when I test as a user who has the said role.

Thanks!
  • AustinK
  • Quickbase Alumni
  • April 2, 2019
Have you tried doing this with form rules instead? If you have a ton of forms it can get annoying but if doing it via the field properties isn't working you could try that.

If you have multiple roles that do not need the ability to edit a field do a multiple condition rule. When a user is in the role <their role(s) here>(multiple roles can be added), make read-only <your fields here>. That way when that role is using that form the fields will be read-only, for other roles they can edit them. You can also flip that rule around and do it as "if the user is NOT in the role <role>, make editable <field>" if everyone except a few roles need the ability to edit.

Try that and see if it works. I'm not sure why it is not working for you with field properties.
  • ChayceDuncan2
  • Quickbase Alumni
  • April 3, 2019
Is your app open to 'Everyone on the Internet' by chance? If you've opened up your app to let non-QB users interact with a portion of your system - that role assigned to EOTI will blanket onto all users because they are people on the internet also

Chayce Duncan | Technical Lead
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
Terms & ConditionsAccessibility statement