You are able to invite your colleagues in to your organisation as Team Members, giving them access to the Console.

Team Members are prescribed Roles. Roles give the Team Members access to specific areas and functionality of the console depending on the roll they are assigned.

You are also able add App Users, who will have access to specific apps and associated forms.



Team Members


In the Team Members menu you will see a search filter, number of team members, and your list of team members.

Team Members have restricted access to the console depending on their Role.

To add Team Members, select 'Team Members' from the side menu.

Click the Add Team Member Button at the bottom right of the page.



Then add the users' full name and email address, and select the appropriate Role for the team member.

The team member will then receive a welcome email, generated temporary password, and a link to login to the OneBlink console. You also have the option of checking the 'Team member will login using Google account' this will not generate a password. The user can utilise the 'login with google' option in the login screen.



Roles


Out of the box the LcS Console includes 5 Team Member Roles. These Roles and their corresponding permissions can be found in the Roles menu. From here you can view the number of Team Members in each Roles as well as add, edit and remove Roles. For more information on Roles check out this article.


Environments Restrictions


Team Members can also be restricted by environment. To do this use the "Restrict Environment Access" switch. Once turned on you will be able to select the environments that the Team Member will have access to. Once this has been configured the Team Member will only be able to view, access, and modify the environments that have been configured for their Team Member.


For more information on environments check out this article.


App Users


Users are restricted to the apps they have been assigned to and the forms published within that app. 


To add a new User click My App side menu, click the Manage button on the app you want to add the user to.

Navigate to the User tab of that app, and click the 'Add User' button.




Integrate with Active Directory


We also have the feature that you can use your current Active Directory to authenticate and authorise App users. More information can be found in this article.



Email Sending


You can also configure the email address that new App users will receive their welcome initiation from. By Default, the email address is support@oneblink.io. Do note that you will need access to the email address you set as the sending email, in order to verify it.


Temporary Password


When a new team member or app users is added and is not using SAML or google to login, they are provided a temporary password. This is used in place of a password when first logging in to the platform or app. Once used the team member or app user will be asked to set a new password. Temporary passwords only last 14 days. If the temporary password is not used within those 14 days, then it will expire and a new temporary password will need to be sent.


When a new user is added as a team member or app user the icon next to their user will show as an orange hour glass. This means they the user has not yet logged in to the platform and their temporary password has not yet expired. When the temporary password expires the icon will change to a red padlock. When this happens the user will not be able to login and a new temporary password will need to be sent. To send a new temporary password to the user, click the Resend password button. This will send an email to the team member or app user with a new temporary password lasting another 14 day.





Removing Users


If you would like to remove a Team Member or a User, and you have the user management permission enabled, on the Team Member page or in the User tab click the trash icon to the right of their email address. You will be prompted to confirm before deleting.


Authenticated Forms

Only App Users are able to see authenticated forms. 

If an App User wants to access an authenticated form they must first login via a login button in the forms library.