I have a form (reference view) for adding new projects in a task management app.
In the form, when selecting the responsible person for the new project, there is a dropdown list with the names and pictures of the team. But there is also the possibility (action button) to add a new member of the team from here.
How can I make that button go away?
(or bonus - How can I make that button go away if the user is not admin?)
I want to remove it because I have a different form for adding new team members and I don’t want users to accidentally add new users when filling up the form for new projects.
( the app is not in english, but I hope that’s not an issue for helping me find the settings to remove the button )
Hi @sorin_mihai, welcome! This article about the USERROLE() expression may be a helpful place to start - the first example it gives highlights how you specific user levels can be defined for allowing updates to a table (look for the ‘Are Updates Allowed’ field in each table): https://help.appsheet.com/en/articles/2357273-userrole
Another option could be to create your own user class system: you can find more on this thread.
[User Permissions with actions](https://community.appsheet.com/t/user-permissions-with-actions/13214) Questions
Hi all, I have two actions that are used to send notifications to buyers i.e. an action that triggers a workflow rule. I had it in mind that one specific type of user would be clicking the action button (the site admin), however the process has changed and it is now necessary for site admin AND buyers to send this notification. However, site admin cannot do so after 2pm everyday. Looking to find the right expression to block site admin from sending the notification after 2pm but keeping the ac…
The Responsibil column appears to be of type Ref. The presence of the New button in the drop-down menu is determined by the app user’s access to the table or slice the Ref values reference. Therefore, you can remove the New button by removing the user’s permission to add rows to the referenced table or slice.
Table permissions take effect wherever the table is used, including within slices. Slices, however, can be given their own stricter permissions (see Slices: The Essentials). A slice can’t have its own conditional permissions like a table can, though.
Hy, yes that is close. But this makes the rule for this table apply everywhere the table is referenced.
But I want it just for this view to not have the possibility to add a new team member. In this view, the dropdown should only be used to select one of the members as a Responsabil, not to create new ones. However, in a different view, the option to add new members must be open. Any way to control that Add New button, locally inside a view?
I guess I could make a second table as a reference to the “Responsabil” table and use it only for this view and make it read only for everybody, and then use the initial “Respnsabil” table on the other view where I want the admin to be able to make changes and there use the expression you mentioned…Is this the cleanest way?
I would do the method of creating a slice to handle this, by creating a slice and setting the update permissions there… All of the mechanisms throughout app sheet are affected all at once and no need to go through an individually configure everything.
Fabian:
In the UX → Localize go to “New” and enter an expression like:
@Fabian the problem you might find here is that the Localize text is only calculated at certain times in the app - it’s not 100% dynamic. Another option would be to control the New button’s visibility by changing the action that control’s it.
sorin_mihai:
Any way to control that Add New button, locally inside a view?
Fabian’s idea of using the CONTEXT() formula is a good one, just not used in the Localize space.
If you put Fabian’s formula in the condition for the add action of the table, that should give you contextual control over the add action and by specifying the view you wish the action to be available in it should give you the ability to show it where you want.
Here’s a link to another article where we discussed how to affect the NEW button in length.
[We need the ability to easily hide the "New" button for inline views](https://community.appsheet.com/t/we-need-the-ability-to-easily-hide-the-new-button-for-inline-views/10604) Questions
I continue to come across instances where we have a parent-child relationship, and we want to show data split via that relationship, but we don’t want users to be able to create a record through the inline view. We want to use the inline view as a read-only space, many clients now opting to use a dedication action (since we can both pass information along but also do more than just one action). The slow down here is that in order to enable this hybrid behavior, you have to create a slice that’…
