This conversation has been merged. Please reference the main conversation: Separating Messages & Notifications within Roles
We allow our employees the ability to receive voicemail notifications to their corporate email address. However, we do not want them changing this email address to a 3rd party email provider as it posses a security risk, allowing employees to forward voicemails that may contain personal or company information such as social security numbers, account numbers, etc. Disabling end user access by deselecting the "Messages & Notifications" option in the role that they belong will also prevent them from changing their voicemail greeting from their desk phone as well as the My Extension Portal. I would like to request that "Messages" and "Notifications" are separated as two different settings within an end user role.
- Number of Digital Lines on the account: 637
- Account type (U.S., Canada, UK, AT&T, Telus, British Telecom): U.S.
- A brief description of the business you perform: Employee Staffing
- A high level description of the product or feature being requested: Granularity in Roles that separates Messages from the Notification Settings page into two separate security settings so that you can disable end user access to the notifications settings page but still allowing them to change your voicemail greeting.
- A typical use case scenario explaining how your business would use the feature: Disabling end user access to the Notifications settings page of their account would allow administrators (Super Admins) the ability to set the end user's email address for voicemail notifications but not allow the end user to change this address to 3rd party email provider (gmail.com, outlook.com, etc.).
- Benefit of such feature: This allows the Super Admin (and company) to maintain company and personal data loss by controlling where voicemails are being sent. Since voicemails may contain any number of personal, corporate or other sensitive information in audio form, my organization needs to be able to control where that information is being sent. In our case, voicemail notifications being sent to our own, corporate email addresses. Disabling end user access to change this feature allows us to continue to maintain the data loss prevention within our organization, but still allowing those users to change their voicemail greeting and allow them to receive their notifications within their corporate email accounts.
- Include any related support case number if applicable: N/A
There are no replies.