Smartstaff, administrator
4,478
edits
Changes
→Authentication Member
!Setting!!Description
|-
|Controller Name||Enter any name you wish.
|-
|Description||Enter desired description.
|Alias||The [[Alias]] of the instance that will act as the '''Primary Authentication Controller'''.
|-
|Member security Security key||This will be populated once the settings are saved. This key must be entered in the configuration of the '''Primary Authentication Controller''' instance.
|-
|Allow all users||Enable this setting if all login-enabled accounts within this '''Authentication Member''' instance should be allowed authenticate and connect via the Primary Authentication Controller.
|-
|Enabled usersUsers||If '''Allow all users''' is not enabled this allows you to select individual user(s) that can use the Primary Authentication Controller to authenticate for this instance.
|-
|Create users - if not foundcreate them automatically||Enable this setting to enable automatic creation of a new account within this instance if someone with an account on the Primary Authentication Controller attempts to connect.<br />''Note:'' this settings attempts to match the e-mail address to uses that are '''already''' login enabled only. If an account with the same e-mail address already exists on the Member instance, but is NOT login enabled a new user will be created when they attempt to connect. This is to avoid accidentally activating an existing contact with inappropriate pre-existing Role(s). The new user will be created with the branch and role defined in the following 2 settings.
|-
|Default branch of new userBranch For New User||If '''Create users if not found''' is enabled you can select which internal branch/company they will be created within.
|-
|Default role of new userRole For New User||If '''Create users if not found''' is enabled you can select which role newly created users will be given.
|}
