Add CURRENT_USER() Function to formulas
A
Adam Johnston
Problem:
Buttons can currently be clicked by anyone that has view access to the record. If a button click leads to records being edited, then anyone who has view access to the record can cause edits. This is obviously not great.
Solution:
Allowing access to the current logged in user in formulas will allow us to customise button URLs depending on who is logged in. This could mean deactivating a button when the logged in user is not one of a select few. Undoubtably there are other use cases too.
Allowing access to teams in formulas (either as a property of the user or as standalone lists of users) too would work great with this. We could allow an important button to be clicked only if someone is a member of the Management team.
A
Adam Johnston
Hello everyone,
I'm bumping this because I think the new Sections Visibility settings would be a lot more powerful with this implemented. Having a CURRENT_USER() would let us change section visibility based on who is logged in: e.g. an admin could see all the fields, and a user could just see what is necessary for their role.
That's great for multiple team members using the same table for differing purposes.
It's also great for system admins because we can hide system fields from ordinary users but still view and modify them easily
Jon Darbyshire Brian Dollen Jeff Gonzalez Emma Montgomery Rick Palaia Peter Novosel Artem Kunytsia
Jon Darbyshire
Hello Adam Johnston! I have a few more questions for you:
- Can you provide examples of the 'select few' users who should have access to the button?
- What specific actions should be restricted to the Management team?
- Are there any other user roles or teams that should have specific access or restrictions?
A
Adam Johnston
Hi Jon Darbyshire,
- In our case it would be those who have been trained in how to use the tool that the button would access. For example if a button sends a quote to one of our clients then only people who have been trained in creating and sending quotes should have access to the button.
Generally, if a button click triggers a script that interacts with SmartSuite using a certain API key then the user that triggers the script might have less privileges than the API key allows them. It would be good to have the option to disable the button in these cases.
- This was a specific example using one of our custom teams. In out use case it is drafting and sending a quote to a client using our accounting software.
- Undoubtably yes. It would be good to have general access to Teams in a formula and have the ability to check if the current user is a member of a certain Team.