You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried creating a test custom role in an instance and tried assigning a user to that custom role but the newly added custom role was not in the options.
Created Role:
Interface:
To Reproduce
1. Create a "Test Role" using Create Role API on an instance
2. Go to the instance's accounts UI3. Click on Users4. Click on Invite User5. Input name, email, choose role.
Current vs. Expected behavior
Expected: Test Role can be chosen
Actual: Test Role is not part of the list. Only seeing default roles.
Which area(s) are affected? (Select all that apply)
Website
Additional context
No response
The text was updated successfully, but these errors were encountered:
The invite endpoint uses accessLevel (1-5) to identify what role they are invited with. That is why currently it is limited to the default (static) roles. Its database as well is limited to an int datatype. I'll be exploring extending accessLevel beyond 5 for custom role and check for any possible implications.
This has been the behavior even with the old accounts-ui. Even though, in the old accounts-ui, you can select a custom role before sending the invite, it will still default to the base (system) role the custom role is created upon invite accept. For example:
Invited user as Test Admin Role (with accessLevel = 1 which is an Admin system role where the custom role is based)
User accepted invite. API will then check the accessLevel value which is 1. So the user will still have the static system role Admin instead of the custom role Test Admin Role.
Description
I tried creating a test custom role in an instance and tried assigning a user to that custom role but the newly added custom role was not in the options.
Created Role:
Interface:
To Reproduce
Current vs. Expected behavior
Which area(s) are affected? (Select all that apply)
Website
Additional context
No response
The text was updated successfully, but these errors were encountered: