Sheet could be called anything, it's just a field to indicate a certain level of authorisation, as defined below. It's not necessarily per sheet, the name I've used clouds the solution. SHEET is just a field, it could be sales area, department, xxx, anything, whatever makes sense for you...call it button?
I use the two steps for two reasons;
1) This allows for more complex and sophisticated scenarios, the example is a simple one.
2) I'm not sure just doing this in one step works. The section access is all hidden once a user accesses the report which means the field you need disappears. But try this and let me know if one step works.
Let me know how you get on and let me know if you have any questions.
Your example was really helpful and in fact, I tried something similar for my logic and it worked.
But my only issue here is, it is forcing me to create a separate table (to map section access users and their roles).
As I said before, there should be a way with the section access table alone. But I am yet to figure out appropriate solution for that. I will let you know once I derive that.
I'm not at my machine at the moment but, as memory serves, you will find this setting under Document Properties > Security.
However, I'd really recommend that you move this script to a hidden tab that is password protected to ensure your security model cannot be compromised. (In your script go to file > create hidden script and enter a password twice).
