Help

Re: Expected behaviour of interface button that runs an automation

Solved
Jump to Solution
589 0
cancel
Showing results for 
Search instead for 
Did you mean: 
Sean_Murphy1
7 - App Architect
7 - App Architect

I have a user that can't click an interface button which runs an automation. The automation primarily updates a field that is not visible through the interface. My user, who has access to the interface but not the underlying base, is unable to click this button. It is greyed out. Unfortunately I didn't get to see the error message you get when you hover over the button because another user 'helped' them and moved the workflow along.

Is it the current expected behaviour that a user with interface only access can't run an automation that changes the base? Or is there something else going on here?

1 Solution

Accepted Solutions

Hello Sean,

It is not required to have access to the database to do such actions.

It may be that this user has read only access.

Regards

Pascal

See Solution in Thread

1 Reply 1

Hello Sean,

It is not required to have access to the database to do such actions.

It may be that this user has read only access.

Regards

Pascal