Should applications and objects be secured using individual user accounts?

Using groups for securing applications and objects in Appian is recommended because it simplifies the management of permissions and enhances security. When you create security settings based on user groups instead of individual user accounts, it allows for more scalable and maintainable security configurations.

Groups can represent roles, departments, or functions within an organization, facilitating the application of permissions. For instance, when a new employee joins a department, you can simply add them to the relevant group rather than reconfiguring permissions for each individual. This approach ensures consistency in access levels and reduces the risk of errors in oversight when managing user permissions.

Additionally, if there are changes in personnel or restructuring within the organization, modifying access rights for a group is more efficient than adjusting rights for numerous individual accounts. It promotes a principle of least privilege while enabling easier updates as organizational needs evolve.

While there might be situations where specific applications could require unique individual permissions, as a general practice, securing applications using groups is seen as a best practice in Appian development and security management.