Leap Login Setting: Set Default Branch to Workstation's Assigned Branch
Requested Change:
We would like to be able to configure Leap to match the Polaris Desktop Client's login behavior with regard to session branch selection. We would like it to default to the workstation's branch.
Desktop Client:
When logging into the Polaris Desktop Client, the "Please select a branch for this session" dialog dropdown menu defaults to the Workstation's branch.
Leap:
When logging into Leap, the "Select your Branch and Workstation" branch dropdown defaults to the User's assigned branch.
Why:
At our organization, most staff are transacting in Leap on a desktop computer that is installed at a particular location. Nearly 100% of the time, these computers will be signing into Leap using the branch where the computer is installed, independent of the staff user's default assigned branch.
We have staff who work at multiple branches and have noticed they accidentally sign into their staff user's default branch, even when they are working at a different location.
Solution idea:
Add a LEAP setting that will allow organizations to select which default branch is presented at login (workstation vs. user). In our case, we would want a global setting for LEAP workstations that always defaults to the workstation's branch. But some organizations might want a user-specific or workstation-specific setting that would override the global setting. There could be unique use cases where a user travels with a laptop and you might want to force a manual selection each time for that particular user or workstation (no default).
-
Brian Horrocks
commented
Requested Change:
We would like to be able to configure Leap to match the Polaris Desktop Client's login behavior with regard to session branch selection.Desktop Client:
When logging into the Polaris Desktop Client, the "Please select a branch for this session" dialog dropdown menu defaults to the Workstation's branch.Leap:
When logging into Leap, the "Select your Branch and Workstation" branch dropdown defaults to the User's assigned branch.Why:
At our organization, most staff are transacting in Leap on a desktop computer that is installed at a particular location and will only be used at that location. With very few exceptions, these computers will be signing into Leap using the branch where the computer is installed, independent of the staff user's default assigned branch.We have staff who work at multiple branches and have noticed they accidentally sign into their staff user's default branch, even when they are working at a different location.
Solution idea:
Add a LEAP setting that will allow organizations to select which default branch is presented at login (workstation vs. user). In our case, we would want a global setting for LEAP workstations that always defaults to the workstation's branch. But some organizations might want a user-specific or workstation-specific setting that would override the global setting. There could be unique use cases where a user travels with a laptop and you might want to force a manual selection each time for that particular user or workstation (no default).