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?
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
- Open the User Management record type.
- Go to Views and Actions Security and open the Actions tab.
- Find the Manage User record action and edit its security.
- Select Security Rules.
- Under Who can see this action?, select Only users… → Found in groups.
- Select the MTS_SENIOR_REVIEWER group.
- Under When can they see this action?, leave it set to Always if there are no other conditions.
- Save.
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
How it works:
- loggedInUser() returns the current user.
- cons!MTS_SENIOR_REVIEWER points to the Senior Reviewer group.
- a!isUserMemberOfGroup() returns true if the current user is in that group.
- If the expression returns false, the record action is hidden.
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:
- The user needs at least Initiator permission on the process model behind the action.
- For related actions, the user needs access to that specific record.
- 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.In a Loan Management application, each loan application has an
assignedReviewerfield 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? - 2.A Loan Application record type has these fields:
- Applicant Name
- Loan Amount
- Credit Score
- Application Status
Reviewers and Senior Reviewers can access the same loan applications, but Credit Score should only be accessible to Senior Reviewers. What is the most appropriate solution? - 3.A Loan Application record type has two views, Summary and Audit Details. All authorized reviewers should see Summary, but only Senior Reviewers should see Audit Details, and only when the loan's status is
COMPLETED. How should this be implemented? - 4.A User Management record type has three related actions: Manage User, Review User and Delete User. Senior Reviewers should only see Manage User, Reviewers only Review User, and Administrators only Delete User. Each user belongs to exactly one role group and has the required process model permissions. Which configuration satisfies this?
- 5.A Senior Reviewer belongs to the
MTS_SENIOR_REVIEWERgroup and can view a User record. The Manage User related action has a security rule allowing the Senior Reviewer group, yet the action is not visible. You find the group has Viewer but not Initiator permission on the process model behind Manage User. What is the most likely reason?