this for example, i want to know how to lock the " editor" button for people who will use this function, but leave on the main page as it is!
You would need to store that permission in a table (could be users table or any table such that it is associated with the user), then connect your app to that table, load the corresponding record by the current logged in user, check the record field corresponding to your permission, and if satisfied, either enable that button via Enabled State (e.g. if you checked permissions on App Start or Step Enter trigger), or make the trigger(s) of the button conditional on that permission.
oh thanks jmlowden! i didn’t quite understand after creating a table… without wanting to be lazy, but do you explain me in a more detailed way?
i’ve created this table and already added it to my app with my user already, now just put into practice that the button only serves users that are added in it.
Hello Emili, do you have access to the User Groups feature? This is the most common way to accomplish this on more recent Tulip releases: Create and manage user groups
I would create a query to get all records with users in that column, then create an aggregation to get the list of unique users from those query results.
In your button trigger, you would check if the current logged in user IS IN that aggregation result.
I did not have user groups available until recently, still exploring, but I imagine this would be more efficient! button condition would be something like current logged in user IS IN user group…