Administrators can create new users or manage existing users via the Administration section of OBG. Administrators can update information in the user's profile and assign the user's OBG access level and group memberships.
Administrators and Service Area Administrators have the ability to create and manage users. If a user does not have Administrator or Service Area Administrator access, the functions to create and edit users will be grayed out.
A business's OBG account must have at least one individual user account (Username) at all times. Likewise, the business's OBG account must have at least one user designated as an Administrator at all times. Administrators may create as many additional users as necessary. If an administrator no longer needs Administrator access and/or needs to transfer Administrator access to another user, Administrator access must be given to the other user first. The new administrator can then reassign the access of the former administrator.
If a user has forgotten their Username, Administrators can view the user's information to see the Username. The user can then be advised of their Username.
If a user has forgotten their password, Administrators can have the OBG system generate a new password and email it to the user. Note that the user's current email address must already be listed in the user's profile before the password is reset. If the email is not received by the user, check to insure that the user's email address is correct and/or have the user check their spam or junk email folder.
If the user no longer needs an OBG account or has left the business, the Administrator can deactivate the account and block the user from logging on to OBG. User accounts are also automatically deactivated by the OBG system after a number of consecutive and unsuccessful logon attempts by the user.
A user's account can be deactivated by checking (or reactivated by un-checking) the box on the user's profile screen.
If a user is being created for the purpose of only using OBG on behalf of Client companies and not on behalf of the user's own company (as might be the case with Service Provider/Representative Sign-ons), the Administrator should set up the user with "Limited Access" and then not assign any access to individual OBG Service Areas (leave all as "No Selection"). The user only needs to be added to the appropriate Client groups (provided that they have been set up by the Client). This will enable the user to use OBG on behalf of Clients but not on behalf of the Service Provider company.
If, in the future, the user needs access to OBG on behalf of the Service Provider company, that access can be added without affecting the user's membership in Client groups.