Getting Started with Personalization Utilities

Hey Patrick -

The saying "measure twice, cut once" is apropos here.
User names are case sensitive, and while it's easy for an admin to deactivate a user, you'll have to engage support if you want to remove users from your system.
That said, does your organization have an agreed upon user naming convention?

Familiarize yourself with the docs on the OOTB add user smart service to ensure you understand how the user object works:
docs.appian.com/.../Add_User_Smart_Service.html

Finally - given that we do have this OOTB functionality to systematically add users, verify for yourself that you actually need to use this plugin in lieu of the OOTB smart service. Typically, designers reserve the use of this plugin for creating users when there's a requirement to not send the default new user/password email.

Hey Patrick -

The saying "measure twice, cut once" is apropos here.
User names are case sensitive, and while it's easy for an admin to deactivate a user, you'll have to engage support if you want to remove users from your system.
That said, does your organization have an agreed upon user naming convention?

Familiarize yourself with the docs on the OOTB add user smart service to ensure you understand how the user object works:
docs.appian.com/.../Add_User_Smart_Service.html

Finally - given that we do have this OOTB functionality to systematically add users, verify for yourself that you actually need to use this plugin in lieu of the OOTB smart service. Typically, designers reserve the use of this plugin for creating users when there's a requirement to not send the default new user/password email.

Thanks, Rob, this is helpful. We are using SAML authentication and don't want users to receive the standard password email.