You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
You are viewing the article in preview mode. It is not live at the moment.
Our offices will be closed from Tuesday, December 24th through Wednesday, January 1st. We will reopen on Thursday, January 2nd. During this time, we will continue to monitor and handle critical support items, but responses to most tickets and inquiries will likely be delayed.
2. Managing Branch Users
print icon

Branch Membership

A user can be a member of one branch at a time. While branch members will not notice a difference in their BenchPrep experience compared to non-members, Console admins and branch managers, depending on their permissions, can view, create, edit, and move branch members around. 

 

You can see if a user is a member of a branch, and which branch they’re a member of, on their details page in the Overview tab. 

 

 

Scope and Access Context 

Scope 

A scope is the range of data that a user can view, determined by their role. For example, the scope of a user with the admin role is the tenant itself, since the admin role grants access to everything in the Console application. 

 

When assigning a role to a user, you’ll also select the scope of that role. All roles can have the tenant scope (like the admin role), but some roles can also have a scope specific to a branch. If you give a user a role, and scope the role to Branch A, then the user will have all of the permissions associated with the role–but only within Branch A. For example, if this role allows the user to create other users, they can do so, but they can only create users for Branch A. 

The permissions added to a custom role determine whether or not you can scope that role to a branch. During the role creation process, you’ll select which permissions the custom role will have. Each permission has its own scope listed in the “Scope” column. If you only add permissions to this role that have “Branch” listed as a potential scope, you’ll be able to scope this role to a branch. If a role has any permissions that can only be scoped to the tenant, you will only be able to scope this role to the tenant. 

 

Access Context

An access context is the data and applications available to a user based on their role and the scope of that role. The Console header will display the role your account holds. If your account holds multiple roles, the Console header will display the role you’re currently using so that you know which access context you’re working in. You’ll also be able to use a drop-down menu to toggle between roles. 

 

To understand how role switching and access contexts work in practice, let’s say you have an account with two roles: the Admin role and a custom role scoped to Branch A. After logging in, the platform will prompt you to select which role you’d like to use. The role you choose determines the access context you’ll work with. 

If you select the admin role, you will see all of Console and be able to work with any user. If you select the custom role, you will only see the areas of Console this role has access to, and only be able to work with Branch A and its members. You can then use the drop-down menu in the Console header to switch between these two roles and access contexts. 

 

Importing Users in Bulk

If you’d like to create multiple users at once, you can bulk import them on the Users page. Bulk importing users does not allow you to edit/update user names, emails, or passwords for accounts that already exist. These will be skipped during the import process.

  1. Select Users under the Manage Users section in the left-hand navigation bar
  2. Click on Import Users at the top right-hand corner
  3. Click on See upload instructions to download a template and create the CSV file.
  4. Select your CSV file for user import.
  5. Assign a branch (optional) for your users, and click Save.
  6. Assign a group (optional field if branch is selected) for your users, and click on Save. If there are no groups listed, the branch you selected does not have any groups yet.
  7. Assign a branch plan (optional if branch is selected) for your users, and click on Save. If there are no branch plans listed, the branch you selected does not have any plans yet. If a branch plan is expired, it will not be selectable as indicated by the ⮾ icon.

    NOTE: Ensure enough seats are available in the branch plan for the users you are importing. For example, if a branch plan has a seat count of 10 and 7 have been used already, then you’ll only be able to assign 3 more users to the plan.
     
  8. Assign a role (optional) for your users, select the role’s scope (i.e. tenant, branch), and click on Save.

    If you’d like to create a new role, click on Create New Role. However, this will exit you from the importing page and will not save your changes. We recommend creating any custom roles that you need first before importing users.
     
  9. Click on Import to import your users.
  10. A pop-up message will appear indicating your import is in progress. You won’t be able to upload an additional file until this import has been completed.
  11. Once the import is finished, you’ll receive a confirmation email that will provide more details on what was imported and if any errors occurred during the process.

 

Editing User Roles in Bulk

Admins, or users with a custom role with create:user_roles and delete:user_roles permissions, can bulk assign or remove user roles.

Assigning User Roles in Bulk

To add roles to users in bulk, follow these steps:

  1. Select Users under the Manage Users section in the left-hand navigation bar.
  2. Select the users that you’d like to add roles to.
  3. Click on Edit User Roles, and select Assign User Roles.
  4. Select a role to assign, select the role’s scope (i.e. tenant, branch), and click on Save.

    Note: An admin user can only assign roles to a scope within their active role scope (i.e. A branch manager cannot assign a role at the Tenant scope or to a branch outside of their scope).

Removing User Roles in Bulk

To remove roles from users in bulk, follow these steps:

  1. Select Users under the Manage Users section in the left-hand navigation bar.
  2. Select the users that you’d like to remove roles from.
  3. Click on Edit User Roles. Select Remove User Roles to remove specific user roles, or select Remove All User Roles to remove all of them.
  4. If you selected Remove User Roles, select the roles you’d like to remove, and click on Save. Only roles and their respective scopes that are contained within the admin user’s active role scope will appear as available options to remove (i.e. If a branch manager is removing a role from a user which has the role at tenant scope and branch scope, only branch scope will appear in the modal and only the branch scoped role will be removed).


    If you selected Remove All User Roles, click on Continue to confirm. Choosing to remove all user roles will only remove those user roles that are contained within the admin user’s scope.

 

Note: Legacy roles like District Admin., District Supervisor, Institution Admin., Institution Supervisor, and Instructor roles cannot be removed via Console.  Please contact BenchPrep support for assistance in removing these roles.

 

Assigning Members to Branches 

One-by-One 

  1. In Console, go to the Users section. 
  2. Select the user you’d like to work with. 
  3. In the Overview tab, select  Edit next to Branch Membership
  4. Use the pop-up window to select the branch this user should be a member of.
  5. Select the Save button to finalize the branch assignment.  


Bulk 

Console offers an in-app wizard to add members to a branch or branch plan in bulk. 

  1. In Console, go to the Branches section. 
  2. Select a branch
  3. Toggle to the Branch Members tab. 
  4. Select the Assign Branch Members button. 
  5. Move any users you want to be members of this branch from the Available Users table to the Selected Users table.  Available Users only displays users who are not associated with any branch. 

  6. Select the Assign Users button at the bottom of the page to finalize the branch assignment. 

 

Bulk Editing Branch Membership

Edit Branch Membership allows you to seamlessly move multiple users to a different branch. A user can only be a member of one branch at a time. Admins, or users with a custom role with update users permission, can edit branch membership in bulk.

 

To edit the branch membership of users in bulk, follow these steps:

  1. Select Users under the Manage Users section in the left-hand navigation bar.
  2. Select the users that you’d like to edit.
  3. Click on Edit Branch Membership.
  4. Select the branch you’d like to assign the users to, and click on Save. Selecting None in this modal will set the branch membership to None for all of the selected users.

    Note: Users belonging to a group will fail to have their branch membership updated until they are removed from their group.

 

Importing Branch Members

Using the Import Branch Members option allows you to import NEW users and assign them as Branch Members to a specific branch.  Bulk importing users does not allow you to edit/update user names, emails, or passwords for accounts that already exist. These will be skipped during the import process.

  1. In Console, go to the Branches section.
  2. Select a branch
  3. Click the Import Branch Members button.
  4. Click on See upload instructions to download a template and create the CSV file. 
  5. Select your CSV file for user import.
    .
  6. Note that Branch Membership will be pre-selected. 
  7. Assign a group (optional) for your users, and click Save. If there are no groups listed, the branch you selected does not have any groups yet.
  8. Assign a branch plan (optional) for your users, and click Save. If there are no branch plans listed, the branch you selected does not have any plans yet. If a branch plan is expired, it will not be selectable as indicated by the ⮾ icon.
  9. Assign a role (optional) for your users, select the role’s scope (i.e. tenant, branch), and click  Save.
  10. If you’d like to create a new role, click on Create New Role. However, this will exit you from the importing page and will not save your changes. We recommend creating any custom roles that you need first before importing users.
  11. Click on Import to import your users.
  12. A pop-up message will appear indicating your import is in progress. You won’t be able to upload an additional file until this import has been completed.
  13. Once the import is finished, you’ll receive a confirmation email that will provide more details on what was imported and if any errors occurred during the process.

 

Removing Branch Membership

Console admins can remove users from a branch. To do so, follow these steps: 

  1. In Console, go to the Branches section.
  2. Select a branch
  3. In the Branch Members tab, select Edit next to any branch member you want to remove. 
  4. In the pop-up window, un-check the box next to the name of the branch the user is currently in, then select the Save button. 
     

You can also remove a user’s branch membership via their user details page by following these steps:

  1. In the Overview tab, select Edit next to Branch Membership

    Note that you must remove the user from any groups they’re in before removing them from their branch. If the user you attempt to remove from a branch is part of one or more groups, you will receive a message prompting you to remove them from the groups first. 

  2. In the pop-up window, un-check the box next to the name of the branch the user is currently in.
  3. Select Save to remove the user from the branch. 

 

NOTE:  Branch managers cannot remove members from the branch they manage–they can only change the user’s membership from their current branch to a child of that branch (if the current branch has children). 

Branch managers who manage unrelated branches will not be able to move users between those branches. Each time a user accesses Console, they select a role to operate within, and Console will not factor in other roles they may have. Because of this, branch managers will not be able to view all branches they manage at the same time, unless the branches they manage have an ancestor/descendant relationship.

Feedback
0 out of 0 found this helpful

scroll to top icon