RingOS - Feature Request

Scenario

User 160 functions as both an office manager and call center supervisor and requires the ability to manage user access at the customer level.

A recurring operational requirement is the reassignment of an existing user account when an employee departs. For example:

- User 102 leaves the company
- A new employee assumes User 102’s extension and role
- The email address and login credentials must be updated accordingly

Current Understanding / Limitations

Based on our experience and prior guidance:

- Customer-level administrators cannot change an end user’s web portal password
- Password changes are limited to the Forgot Password process
- Changing the voicemail password has no impact on web portal access
- Changing the voicemail email address has no impact on web portal login credentials
- The email tied to web portal access appears to be controlled at the backend / billing module level

Regarding user deletion and recreation:

- We have been advised that deleting and recreating the user may be a workaround
- However, in practice this introduces additional constraints:
- A newly created user must be assigned a subscription
- Customer-level administrators do not have the ability to assign subscriptions
- This makes the delete-and-rebuild approach not self-sufficient at the customer level

Additionally, we have observed that even after deletion and recreation, email associations for portal access may persist or not update as expected, indicating backend dependency.

Request for Clarification

We would appreciate confirmation on the following:

1. What is the correct and fully supported method to reassign an existing user (e.g., User 102) to a new employee, including:
- Updating the web portal login email
- Resetting or reassigning login credentials

2. Is there any supported way for a customer-level administrator (without billing module access) to:
- Update the email address tied to web portal login
- Manage or initiate credential resets beyond the standard user-driven process

3. If backend/provider intervention is required:
- What is the recommended operational workflow to ensure a clean transition without residual credential or subscription conflicts?

4. How should customers handle this scenario efficiently and repeatedly without:
- Requiring user deletion
- Requiring subscription reassignment
- Creating dependency on backend corrections

Objective

Our objective is to establish a clear, repeatable, and customer-manageable process for handling employee turnover scenarios.

At present, there is a gap where:
- Customers cannot fully manage user credential transitions
- Deletion/rebuild is not viable due to subscription control limitations
- Backend dependency introduces delays and inefficiencies

We are looking for a defined and supported workaround or best practice that allows customers to operate more independently in these scenarios.

We appreciate your guidance and any supporting documentation you can provide.