Open Sammieboy00 opened 3 weeks ago
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:
Blocked due to backend needing an update first, after which the frontend will proceed.
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:![image](https://github.com/zesty-io/website/assets/141294382/0c98cf30-ca20-4b51-9382-449cbe3c487a)
Interface:![image](https://github.com/zesty-io/website/assets/141294382/ab958b92-7c32-4710-910b-54e36650268c)
To Reproduce
Current vs. Expected behavior
Which area(s) are affected? (Select all that apply)
Website
Additional context
No response