Skip to main content
Question

What are Group Membership Rules in Appian, and how can users be dynamically added to or removed from groups?

Answer

Membership rules let Appian manage a group’s members for you. You define conditions on user profile attributes, such as username, first name, last name, email, or a custom user profile field. Appian then adds every user who matches, so nobody has to add or remove members by hand.

This helps most when you have a lot of users, or when you’re setting up role-based access control (RBAC).


1. Practical example

Take a Loan Management Application with three groups:

  1. Loan Officers
  2. Loan Underwriters
  3. Loan Managers

Say every user in the Underwriting department should be in the Loan Underwriters group. You don’t need to keep that list up to date yourself. Store each user’s department in a custom user profile field. Then add a membership rule to Loan Underwriters:


Suppose your Loan Application has three users:

User

Department

John

Underwriting

Sarah

Finance

David

Underwriting

You create a group called Loan Underwriters and configure this Membership Rule:

Department = Underwriting


How the rule works

User

Rule Matches?

Result

John

Yes

Added to group

Sarah

No

Not added

David

Yes

Added to group

Final Group Members

Loan Underwriters

John

David


What happens if Sarah's department changes from Finance to Underwriting?

Appian automatically includes Sarah in the group because she now satisfies the membership rule. No developer needs to manually add her.



2. How to configure a membership rule

  1. In Appian Designer, open the group you want to manage.
  2. Go to the Membership Rules tab.
  3. Click New Rule.
  4. Choose whether the rule applies to users or groups.
  5. Set the conditions, each with a field, an operator, and a value.
  6. Click Create to save the rule.
  7. Open the Members tab and check which users the rule added.

Only group administrators can create or change membership rules.

What are Group Membership Rules in Appian, and how can users be dynamically added to or removed from groups?



3. Types of group membership

A user can belong to a group in three ways:

Member type

How the user got there

Direct

Someone added the user to the group by hand.

Indirect

The user belongs to a group that is itself a member of this group.

Rule

A membership rule matched the user and added them automatically.

The Member Type column on the Members tab shows how each user or group got into the group.


4. A limitation to know

If a rule has more than one condition on the same field, Appian only evaluates the first one.

For example, with these two conditions:

  1. Username contains “a”
  2. Username contains “b”

Appian applies only “Username contains ‘a’” and ignores the second condition.

If you need more complex criteria, put the value you want to match into a custom user profile field and write the rule against that field. Membership rules also work only with the user and group attributes Appian supports. They can’t call expression rules or query your application’s database tables to decide who belongs.


5. When to use membership rules

Membership rules are a good fit when:

  1. Users should land in groups based on their profile information.
  2. Membership changes often because people change departments or the organization is restructured.
  3. Many users need the same application permissions because they hold the same role.
  4. You want less manual group administration.


Some membership depends on business data, such as assigning an underwriter to a specific loan based on database records. For that, use a process model with the group management smart services.


Interview tip: membership rules are configuration. They manage group membership dynamically. Don’t confuse them with expression rules, which hold application logic.

Check yourself

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

  1. 1.
    Your Loan Management Application has a Loan Underwriters group with the membership rule Department = Underwriting. John's Department is Underwriting, Sarah's is Finance and David's is Underwriting. Assuming no other membership assignments exist, which users automatically become members of the group?
JuniorSeniorSecurity