The updated user management features, New Domain Admin UI and User Object Admin Page, introduce several behavior changes for Admins managing Vault users and domain users.
Known Issues
The following known issues impact user management. We plan to address these issues in a future release.
Impacts | Issue |
---|---|
|
|
|
|
|
|
Vault Users |
When Dynamic Access Control is enabled and an Admin assigns a delegate for a user, the user can see the full name of the assigned delegate in the Delegate Access section. |
Vault Users |
If a user does not have the User: View User Information permission, the user can see the Delegate Access section with a list of masked users. Users can delete a masked user. |
|
|
|
|
|
|
|
|
|
|
|
|
Vault Users |
Newly-created users don't see left and right arrows to navigate to other records in the list when viewing or editing a User record. |
Vault Users |
There is no Favorites view on the Vault Users page, but users can still mark a User record as a favorite on the record detail page. |
Vault Users |
On the Vault Users page, Admins see an unclear error message when they attempt to assign a new cross-domain user a higher security profile than they themselves have. |
|
|
|
|
|
|
Vault Users |
Cross-domain users can update Domain-level fields on Person records using Vault Loader. |
Vault Users |
A Cross-domain Security Policy no longer displays the home domain for cross-domain users. |
Vault Users |
When an Admin searches for users on the Vault Users page and exports the list of users, the export only includes users where the search term matches a value in the Name column. If the search returns results that match on other columns, those results doesn't appear in the export. |
Domain Users |
The Domain column no longer appears for a list of domain users. |
Behavior Changes for Managing Vault Users
The following behavior changes impact Admins managing Vault users:
- Admins who only had the Admin: Users: Create permission previously now also have the Admin: Users: Edit permission.
- Admins who only have the Admin: Users: Read permission and the Object: User: Read permission can no longer see all fields on the User object.
- On the User record detail page for a cross-domain user, non-editable fields are no longer greyed out. However, Vault prevents users from saving changes to these fields.
- Users in the Pending state appear with an Active status instead of Inactive. Note that Admins can perform configuration for these users, but the pending users are not able to log into Vault.
- The columns that appear by default for a list of users have changed to:
- Name
- Company
- Title
- Mobile
- Office Phone
- The following columns are no longer available for a list of users:
- Domain
- Vaults
- The following columns have updated names for a list of users:
- Business Email becomes Product Announcement Emails
- Technical Email becomes Service Availability Notifications
- If no login history is available for a user, the Last Login field will now be blank.
- The Add Users to this Vault action is no longer available to non-Domain Admins. This option now exists on the Domain Users page, which is only available to Domain Admins. Note that non-Domain Admins can add a user to a Vault by creating a new user and selecting an existing domain user in the Domain User field.
- The Vault Users list page includes a User object record for System User.
- Only Active users see the Reset Password and the Force Update to Security Question user actions.
- When Admins create cross-domain users in Vaults with multiple applications, Vault automatically populates only one Application License Type with the cross-domain user’s License Type, in the application which has the highest number of license types available. If multiple applications “tie” for the highest number of licenses remaining, the Application License Type is set in all of these “tied” applications.
Behavior Changes for Managing Domain Users
The following behavior changes impact Admins managing domain users:
- Domain Admins can no longer see the list of Vaults to which a user is assigned from the Domain Users page list view. Instead, they can see Vault membership from a User record detail page.
- Domain-only users are not editable on the Domain Users page. Instead, Admins can assign a domain user to the current Vault in a Pending state by setting an Activation Date. Once the user is added to the Vault, the Admin can edit user details.
- Domain Admins can’t edit users that do not have membership to the current Vault.
- The option to Export study site assignments for Portal users no longer appears in the Actions menu on the Domain Users page.