Skip to main content
Question

How do you configure a record action in Appian so that it is visible only to specific users? For example, if a Senior Reviewer opens a record as Senior Reviewer, they should only see the 'Manage User' action. How can this be designed?

A
Anonymous
December 2, 2025

Answer

In Appian, Record Action Security controls which users can see and run a record action. You can set it up with either Security Rules or a Security Expression.

In this scenario, we can use group-based security so that Senior Reviewers can use the Manage User action, and each of the other actions is limited to the role it belongs to.


1. Practical example

Take a User Management application with three user roles and three record actions.

User role

Manage User

Review User

Delete User

Senior Reviewer

✓

✗

✗

Reviewer

✗

✓

✗

Administrator

✗

✗

✓

2. Configure Record Action Security

Navigation: Record Type → Views and Actions Security → Actions

  1. Open the User Management record type.
  2. Go to Views and Actions Security and open the Actions tab.
  3. Find the Manage User record action and edit its security.
  4. Select Security Rules.
  5. Under Who can see this action?, select Only users… → Found in groups.
  6. Select the MTS_SENIOR_REVIEWER group.
  7. Under When can they see this action?, leave it set to Always if there are no other conditions.
  8. Save.

How do you configure a record action in Appian so that it is visible only to specific users? For example, if a Senior Reviewe


Now only members of the Senior Reviewer group can see Manage User, as long as they also have the record and process model permissions it needs.


3. Alternative: Use a Security Expression

If the requirement is more complex, you can use a Security Expression in place of a Security Rule.

Navigation: Record Type → Views and Actions Security → Actions → Manage User → Security Expression

a!isUserMemberOfGroup(
username: loggedInUser(),
groups: cons!MTS_SENIOR_REVIEWER
)

How it works:

  1. loggedInUser() returns the current user.
  2. cons!MTS_SENIOR_REVIEWER points to the Senior Reviewer group.
  3. a!isUserMemberOfGroup() returns true if the current user is in that group.
  4. If the expression returns false, the record action is hidden.

How do you configure a record action in Appian so that it is visible only to specific users? For example, if a Senior Reviewe


4. Configure the other actions too

Restricting Manage User to Senior Reviewers doesn’t hide the other record actions from them.

If Senior Reviewers should see only Manage User, you also need to set security on Review User and Delete User so each one is available only to its intended role.

Appian also doesn’t treat groups as mutually exclusive. A user who is in more than one authorized group may see more than one action. If roles need to be exclusive, define that role policy explicitly and write the security conditions to match it.


5. Check process model security

Whether a record action shows up also depends on the permissions underneath it:

  1. The user needs at least Initiator permission on the process model behind the action.
  2. For related actions, the user needs access to that specific record.
  3. The action’s security rule or expression has to allow access.

So even when the group check returns true, the action won’t appear if the user doesn’t have the process model permissions.


Conclusion

Recommend Record Action Security Rules with group-based access, because they’re easy to set up and maintain.When the business rules involve several groups, record status or other conditions, a Security Expression gives you more control.


Official Appian Documentation: Record Action Security.

Check yourself

Question 1 of 5, on what the answer above covers.

  1. 1.
    In a Loan Management application, each loan application has an assignedReviewer field of type User. Reviewers should only be able to access loan applications assigned to them. All reviewers already have Viewer permission on the Loan Application record type. How should you implement this?
JuniorSecurity#secenrio_based