Hi,
We are looking into using self-registration for one of our extended enterprise domains. We are trying to determine if we should use “Branch” for our user “Site Location” data value. Our thought behind this is that it would make future rules around data management and reporting for Power User permissions easier to manage as the program grows.
The concerns we have are:
- We don’t see a way to require a user to select a branch using the branch drop-down option upon self-registration. (Note: We cannot use the “require branch code option” as it’s unfortunately not manageable or scalable to communicate the code to all the different client site learners. Even if we could it doesn’t help with the next bullet point?)
- We don’t see a way for a user to change their “Branch” under their account profile once it’s created. (Note: Learners often change “site locations” so they need the ability to update it as needed.)
Based on these concerns, we’re thinking using an Additional Field is a better option for our scenario to capture user “site location” data. The main down side to using an Addl Field is it requires us to have to manage “Groups” with rules including the “site location” additional field in the future when it comes to Power User permissions instead of simply utilizing “Branches”.
We are curious if anyone has any insights, or if perhaps we’re missing something within the functionality or configuration settings that would allow us to use “Branches”.
Here’s our understanding and questions:
If we use self-registration, users do have the ability to select their “Branch” from a drop-down during registration, BUT it is NOT a required field. The Branch drop-down field pre-populates with the first available branch (by alphabet). If a user does not change/select their branch they’ll be put in that “default” pre-populated branch.
- Is there a way to make the Branch drop-down a required field upon registration?
- Do users have the ability to change their branch from their account profile page once they’ve registered?
Are we understanding this correctly? Are we missing anything here?
Thanks for any ideas or insights you may have. Even if it’s just validating that for our case and needs, using an Additional Field instead of Branch for our site location field is our best bet.
