You will now be able to use the same login and password to log into:
- My Phone Portal
- UC-One Clients – UC-One Desktop, Mobile, Tablet and Connect
- Business Apps – Receptionist, Call Center Express Supervisor and Agent
Currently, you have a single password and two different logins:
- One for My Phone dashboard login (defined by your Site Admin when your station was first assigned to you) and
- One for UC- One Clients and Business Apps login that was system defined as your TelephoneNumber@ServiceProviderDomain
With this update, you will be able to use the same username/password across all supported clients, apps and portals.
For Administrators –
As an administrator, you can define up to 4 additional user IDs per user such as the End User’s email address (assuming it is unique). Users existing password is not changed unless requested by the user or if you reset it. Once you change a password for an End User, the End User must access the temporary password within 24 hours. If not accessed within 24 hours, you must resend a temporary password.
- The system defined login (TelephoneNumber@ServiceProviderDomain) the End User already has will continue to work and does not count as one of the four additional user IDs.
- All logins must have a format of “alpha-numeric-string@domain”. If your current User ID is in this format and it is unique across BroadCloud, it will be recognized and kept by the system.
Please Note: The previous login (typically FirstInitial, LastName ) will not work after your next successful My Phone login. Otherwise, if you have not defined a new compliant login, the End User will be prompted by the system to login with their existing credentials and retrieve a new system generated login. After the End User acknowledges the Pop-up message regarding their new long User ID, they will receive an email with the same information for historical purposes.
- After a period of time, support for old non-compliant logins will be stopped and the end user will need to use one of the following logins to access the My Phone portal:
- System generated login
- One of their additional User IDs
Features added to Site Services
Until now, if an Administrator wanted to use Site Services like Selective Call Forwarding or Alternate numbers with an Auto Attendant, Call Queue, or Hunt Group, they would have to buy a station with these features. BroadCloud is now enhancing these services so that additional feature functionality is supported directly by the service; eliminating the requirement for an additional station and simplifying administration.
Features added in R22:
- Call Forward Always to Auto Attendant, Hunt Group, Call Queue
- Call Forward Selective with schedule added to Auto Attendant, Hunt Group, Call Queue
- Alternate Numbers for Auto Attendant, Hunt Group and Call Queue
- Distinctive ring to Hunt Group and Call Queue
Enterprise Directory access from your phone
Currently, you can access your enterprise directory from:
- UC Clients
- Receptionist Client
- My Phone Portal
- CRM Connect Client
- Dialer for Chrome
Soon, you will be able to access your Enterprise Directory directly from your desk phone if you are using Polycom VVX or Yealink phones.
What changes can we expect to see in the My Site Portal?
Site → User Assignments → Station, Device, and User Assignment → User Info
As an Administrator, you will now have the ability to add up to four (4) unique user IDs for each user. The new user IDs need to be in the above specified email format and unique.
End user email notifications will now include all user IDs configured for the user by the account admin.
What changes can we expect to see in the REP Portal?
Site → Assignments → List by User → Edit User Assignment → User Info
As an Administrator, you will now have the ability to add up to four (4) unique user IDs for each user. The new User IDs need to be in the above specified email format and unique.
End user email notifications will now include all User IDs configured for the user by the account admin.
What changes can we expect to see in the My Phone Portal?
When you first login, after the R22 Upgrade:
- Using your existing short User ID, you will receive a pop-up message providing your new User ID.
- An automated email will be sent to you with your new User ID for future reference.
- On the next My Phone login, your previous short User ID will no longer be available for use.
Moving forward, you will use any of your new User IDs to login to the My Phone Portal and UC-One Clients.
Does this change effect how I log into UC-One / CRM Connect / Receptionist / Call Center Clients?
After you have successfully received your new User ID by logging into the My Phone portal or through your administrator, all new User IDs will be available for login to these Clients.
- New UserID@SPDomain
- Existing TN@SPDomain
Which BroadCloud Services Use Unified User ID?
- BroadCloud My Phone End User Portal
- BroadCloud UC-One Clients
- Communicator (Desktop, Mobile, Tablet – iOS / Android)
- Connect / Meet (Mobile – iOS / Android)
- BroadCloud Receptionist Client
- BroadCloud Call Center Clients (This is not CC-One)
How does the new unified user ID functionality work?
With the alignment of BroadCloud R22 and BroadWorks R22, the BroadWorks alternate user ID feature is now supported. The BroadCloud unified user ID feature leverages the BroadWorks Alternate ID feature allowing up to four (4) unique user IDs per user. This new functionality lays the foundation for other exciting new near-future feature functionality in BroadCloud, including external authentication, bMobile, and more.
When will the new unified User ID get created?
On the first (1st) attempt after the BroadCloud R22 upgrade, any of the following events will cause BroadCloud to automatically generate unique User IDs for each end user.
- If a site administrator logs into the My Site or REP portal and edits an end user’s information.
- If an End User logs into their My Phone Portal.
- If an API request is submitted with user information changes.
- If a user creation bulk upload is initiated from the My Site or REP portal.
The automatically generated user IDs are created by taking the existing short user ID and then adding an “@” symbol and the service provider domain. BroadCloud will then validate the user ID for uniqueness. If unique, the user ID is saved, otherwise, the system will add a numeric string after the short user ID portion of the user ID and attempt another validation.
- Existing User ID → johnsmith (Not unified user ID compliant)
- Auto Created User ID → firstname.lastname@example.org (Unified user ID compliant – Not Unique)
- 2nd Auto Attempt → email@example.com (Unified user ID compliant – Unique)
By default, the following unified user IDs will be auto-created for end users:
- If the short ID was not unique, the existing short user ID may be postpended with a numeric value.
What are the formatting requirements for the new user IDs?
The new user ID format requires that user IDs be unique across BroadCloud, and, must now be in “alpha-numeric@domain” format and not exceeding 161 total characters (does not have to be a real email address).
Special Note – It is highly recommended that end users use their email address as at least one of their user IDs. If end users are not happy with their system generated user ID, they are encouraged to contact their account admins to coordinate having it changed.
How long will the existing “Short” user IDs work?
BroadCloud will continue to support existing user IDs for a 90-day period after BroadCloud R22 releases so that end user or site administrators can follow the steps below to update the end user IDs. After the 90- day period, if an end user has not logged into their My Phone Portal or if a customer admin has not verified the end user’s account, the system will generate a new, unique user ID in email format and the end user will receive an email with the updated information.
Does this affect other BroadCloud account logins?
This change does not affect any other user IDs, only end user IDs. The SP portal or customer admin user IDS will remain unaffected.
How does this affect the FED platform and PIV users?
User ID Box Returning – For existing PIV Users who have an email address specified in the email field, the email address will automatically be moved to the new user ID field after the end user’s first My Phone login after the R22 Upgrade.
Up to 4 unique user IDs in email format can be configured for FED users. This allows up to 4 PIV user credentials to be used by each user.
How is the user creation bulk upload process affected?
When user creation bulk uploads are submitted after the R22 Upgrade, user IDs will need to be in the new email format.