Back|
Back |
|
User Management
User Management helps you keep your sensitive data secure by controlling access to specific program areas, accounts, and PDF templates in Advisor View. You can create user groups and then set up roles and assignments that tell Advisor View which users or groups are allowed to perform certain tasks in the program. You can assign multiple roles to each user, and if you assign conflicting roles (one role grants access and another restricts access), Advisor View will err towards granting permission as opposed to restricting permission. For example, let's say you create a role to grant access to billing and another role to restrict billing access. When you assign both roles to the user, Advisor View will grant the user access to billing.
After you set up roles and assignments, the next step we recommend is setting up and assigning account sets so Advisor View knows which accounts your users and groups are allowed to access.
On the User Management page, you can set permissions for:
ACCOUNT SETS. An account set is a collection of accounts that don’t have to be related. To build account sets, you can use account set saved searches.
Account Set Saved Searches. Account set saved searches automatically update account sets with accounts that fit the criteria or rules for the group. Account set saved searches are useful when you want to locate an account or multiple accounts to add to an account set.
ROLES. A role defines the set of tasks that a user or user group is allowed to perform—for example, you can use roles to set whether a user can access global setup options like creating benchmarks or creating target allocations.
ROLE Sets. You can group roles in a role set to make permissions easier and more reliable. For instance, you can create a role set for your ops team that includes permissions for PDF templates, and another role set that creates permissions for accounts. This way, you won't have to assign each permission for each user, and you won't risk forgetting permissions that you wanted to include.
PDF Templates. You can set PDF templates as public or private, and assign permissions to protect PDF templates from being inadvertently altered or deleted. You can also choose who can access a template, and whether users have read-only or edit access. Administrators have access to all templates.
PDF Template sets. You can group PDF templates into a PDF template set. Your PDF template set can contain as many PDF templates as you select, or you can select all templates if you want to create a set that includes everything. The set makes it easier for you to manage your PDF template permissions at the group level instead of having to set the permissions separately for each template.
USERS. Each person who has access to Advisor View has a user account. You can assign a logo for each user's view.
USER GROUPS. A user can be a member of more than one user group. By creating a user group, you can avoid repeatedly setting the same permissions for multiple users.
Views. Report views are pre-defined report snapshots that can be based on any dynamic report in Advisor View. They make it easy to create customized reports that show slightly different information. Views are only available to the owner/author and administrators until they are set as publicly accessible. Administrators can then assign user and user group permissions for these shared views to determine exactly who can see them.
Views SEts. A view set is a group of views that allows you to manage permissions at the group level instead of having to set the permissions separately for each view. View sets can be managed by any administrator and they don't have owners.
|
May be assigned access to 0 or 1 account set |
|
May be assigned access to 0 or more PDF templates |
|
May have 0 or more users |
|
May be assigned 0 or more roles |
|
|
May be assigned to 0 or more users |
|
May be assigned to 0 or more user groups |
|
|
May be assigned to 0 or more users |
|
|
May be assigned to 0 or more user groups |
|
|
May contain 0 or more PDF templates |
|
|
Must contain an “All PDF Templates” PDF template se |
|
|
May be assigned to 0 or more users |
|
|
May be assigned to 0 or more user groups |
|
|
May defined by 0 or more roles |
| Note: A role set with 0 roles would act as a placeholder and does not make logical sense for assignment to users |
|
|
|
May be assigned to 0 or more users |
|
|
May be assigned to 0 or more user groups |
|
|
May be assigned to 0 or more users |
|
|
May be assigned to 0 or more user groups |
|
|
May be assigned access to 0 or 1 account set |
|
|
May be assigned access to 0 or more PDF templates |
|
|
May belong to 0 or more user groups |
|
|
May be assigned 0 or more roles |
|
|
May be assigned to 0 or more account sets |
|
|
May be assigned to 0 or more users |
|
|
May be assigned to 0 or more user groups |
|
|
May be assigned to 0 or more users |
|
|
May be assigned to 0 or more user groups |
|
|
May be assigned to 0 or more users |
|
|
May be assigned to 0 or more user groups |
|
|
May be assigned to 0 or more users |
|
|
May be assigned to 0 or more user groups |
|
|
May contain 0 or more PDF templates |
|
|
Must contain an “All PDF Templates” PDF template se |
|
|
May be assigned to 0 or more users |
|
|
May be assigned to 0 or more user groups |
|
|
May be assigned to 0 or more users |
|
|
May be assigned to 0 or more user groups |
|
|
May defined by 0 or more roles |
| Note: A role set with 0 roles would act as a placeholder and does not make logical sense for assignment to users |
|
|
|
May be assigned to 0 or more users |
|
|
May be assigned to 0 or more user groups |
|
|
May be assigned to 0 or more account sets |
|
|
May be assigned to 0 or more users |
|
|
May be assigned to 0 or more user groups |
|
|
May be assigned to 0 or more users |
|
|
May be assigned to 0 or more user groups |
