When gathering requirements, which Appian design object should be used to account for user access control?

• A. Groups
• B. Process models
• C. Portals
• D. Record Types

Answer: (A)

Defining who can access what is the core idea here. In Appian, access control is driven by groups—the collections of users that share a role or function. By identifying the groups in your requirements, you can map permissions to those groups and attach security settings to various design objects accordingly. This makes it possible to control who can view, edit, or execute across interfaces, processes, and data consistently as users change.

While other objects involve security considerations (process models govern workflow, portals/sites handle UI access, and record types manage data-level security), the mechanism you use to model and enforce who can access the system is groups. They serve as the primary unit to define and manage access across the application.