Environment

• MultiPortal Version: 1,2.0
• Proxmox VE Version: 9.2
• Deployment Type: HA Cluster]
• Browser (if UI issue): Edge

Description
When creating a new user and assigning a role at creation, the role is not applied. The user is created successfully with no error shown, but the role field is blank in the users list. The failure only surfaces later when the account is used.

Editing the same user afterwards and assigning the role works correctly.

This may share a root cause with the existing thread “Suspected Bug: User Permissions Not Updated After Role Changes” — that one describes create working and later role changes not propagating; this is the inverse on the create path.

Steps to Reproduce (if applicable)

1. Create a new user and select the Service Provider Administrator role.
2. Save. User is created, no error displayed.
3. Users list shows the role field blank.
4. Impersonate the user - Forbidden (#403).
5. Edit the same user, assign Service Provider Administrator, save.
6. Role now applies correctly and impersonation works

Expected Behavior
The role selected at creation is persisted and applied to the user. If it cannot be applied, an error is surfaced at creation rather than the user being created in a broken state.

Actual Behavior
The role is silently dropped. The user is created without permissions and no error is shown. The only signal is a 403 at point of use.

Logs/Screenshots
[ ]

Apologies Woody!- let me correct my scenario
I did not create one user with two roles assigned , it was two separate users one having the reseller role assigned and the other has reseller read only role assigned on creation.
The issue is both these users showed as no role assigned when I checked in the user list afterwards , which is why it gave the 403 error while trying to login as one of these users , I couldn’t reproduce it, so the question is whether a single user created with a single role can ever end up with no role assigned if something in the creation step fails silently.

Quick question on MP user creation — is role assignment applied synchronously at the time of creation or is it via the background worker? And can a user be created if the role assignment step fails (i.e. end up with no role)?
Scenario: I created a reseller user with the “Reseller” and “Reseller Read Only” roles selected at creation. The user was created, but impersonating it returned a 403 Forbidden, and on further inspection the user had no role assigned. It didn’t recur on subsequent tests later, so I can’t reproduce it — mainly trying to understand the flow for my test coverage, and whether it’s possible to end up with a role-less user if the assignment step fails.