Updating User Account Settings
In general, updating user settings requires “manage” permission over the user’s primary group.
If you are an Organization Admin, then you have manage permission over all groups in your organization and therefore have the ability to manage all users in your organization.
How to Update User Settings
- Navigate to the user's standard action menu (available on the users index page or on the user's detail page)
- Select Edit User.
- Apply desired changes.
Attribute Editing Restrictions
To maintain account security, some attributes may only be updated by the user themselves, or by an Organization Admin. This chart will tell you which attributes are editable by which users.
Attribute |
Self |
Manager |
Org Admin |
Full Name: User's full display name (e.g. Standard User A) |
Yes |
Yes |
Yes |
User Name: Unique Platform username (e.g. standardusera). |
No |
No |
No |
User ID: Unique Platform ID. |
No |
No |
No |
Initials: User’s display initials (e.g. SUA) |
Yes |
Yes |
Yes |
Email Address: Email address associated with the account. |
Yes |
No |
Yes |
Phone Number: Used for sending 2FA codes to the user via SMS. |
Yes |
No |
No |
Timezone: (e.g. Eastern, Central) If specified, timezone will override primary group default timezone for automating Platform scripts and workflows. |
Yes |
Yes |
Yes |
Robot User: Whether or not this account is a robot account. |
No |
Yes |
Yes |
Active: Whether or not this user account is active. Deselecting this checkbox will deactivate the user's Platform account. |
No |
Yes |
Yes |
Disable SSO: Whether or not this user has SSO disabled. If SSO is disabled, the user will need to log in using a password + 2FA code. Only applicable if SSO is enabled for your organization. |
No |
Yes |
Yes |
Automatically Send Two-Factor Codes via SMS: Checking this box will cause SMS two-factor codes to be automatically sent to the user during the login process. If unselected, the user will need to use an Authentication App or manually request SMS two-factor codes, if SMS two-factor is allowed by their organization. |
Yes |
Yes |
Yes |
Require two factor auth for login: Whether or not two-factor authentication is required for this user. Recommended to have enabled for all users. |
No |
No |
Yes |
Organization: This field is not editable since it is based on a user's primary group. For instance, if the user's primary group is within Organization A, then the user will belong to Organization A. |
No |
No |
No |
Primary Group: The user's main group. This group will automatically be given edit access to all Platform objects (e.g. jobs, notebooks, services) created by this user. |
No |
Yes |
Yes |
Additional Groups: The user will be able to share work with users in these groups. Also known as Sharing Groups. |
No |
Yes |
Yes |
Comments
0 comments
Please sign in to leave a comment.