This is available.
On a Details screen, open Behaviour. Who can see Edit sits under Allow Editing, and Who can see Delete sits under Allow Delete. Each rule uses the logged-in user, the same way Screen Visibility Logic does. With no rule, the buttons stay as they are today.
How to set it up: Who can see Edit and Delete
What shipped: 18 Oct 2026 Release
Problem
To let only some people edit or delete a row, a maker copies the row page and sets Screen Visibility Logic on each copy. One copy, shown when Role is Admin, has Edit and Delete turned on. The other copy, shown to everyone else, has them turned off. The two pages have to be kept in sync.
Who it is for
A maker of a private app who wants one row page for every logged-in user, and wants Edit, Delete, or both to appear only for some of those users, such as when Role is Admin.
What happens today
On a row page, Allow Editing and Allow Delete are on or off for everyone who can open that page.
Screen Visibility Logic decides who can open the page. It does not decide who sees Edit or Delete.
The way to vary those buttons is a second page with the same layout, different Screen Visibility Logic, and the buttons turned on or off.
Requirement
On the same row page, under Behaviour, the maker can choose who sees Edit and who sees Delete.
The rule uses the same kind of logic as Screen Visibility Logic: a property of the logged-in user, such as Role is Admin. Edit and Delete each have their own rule.
When the rule matches, that button is shown and works as it does today. Edit opens the update screen. Delete uses the button text, confirmation, and success message already set on the page.
When the rule does not match, that button is not shown.
If the maker does not add a rule, the button stays as it is today. Allow Editing and Allow Delete still turn the button on or off for everyone who can open the page, so existing apps do not change on their own.
Screen Visibility Logic still decides who can open the page.
Out of scope
This does not change who can open the page. It does not change which rows a person can see. It does not let someone edit or delete a row when the button is hidden. It does not remove Allow Editing or Allow Delete.
Acceptance
- With no rule on the button, Allow Editing and Allow Delete behave as they do today.
- With a rule that Role is Admin on Delete, an admin sees Delete on the row page and another logged-in user on that same page does not.
- Edit can use a different rule from Delete, or the same rule.
- A person who cannot open the page still cannot open it.
- A row page that has never had a button rule looks the same as it does today.