-
-
Notifications
You must be signed in to change notification settings - Fork 527
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Super admin should be able to add different kinds of users #4503
Comments
@cielf may I have this issue? |
Go for it! |
When testing this out, check the case mentioned in issue #4532. |
Thanks. I'll look into that. |
This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned. |
Automatically unassigned after 7 days of inactivity. |
- just a single form containing all accordion sections - on validation error, detect which sections contain errors and open just those sections
May I work on this one? |
It makes sense to pair it with #4819 which you're already working on, so ok. |
Summary
Superadmins should be able to add any type of user. Right now, they have to add a organization user, and then can add roles.
Why change
We don't really ever want to add partners directly, but new user types (e.g. the proposed NDBN type) will not have an organization to belong to. Super admins should be able to add super admins as well -- right now we have to add them through the back end.
Details
So what do we want to do
Remove the "organization" on add user.
Add "Role" and "Resource" fields that are completed to determine the role the new user has.
The available selection for the "Resource" field should be determined by the Role
-- if org_user or org_admin, the resources available would be the Organizations
-- if partner, the resources available would be the Partners
-- no resource available for SuperAdmin role.
Name, email, Role fields are mandatory. Resource is mandatory iff role has a resource (i.e. org_admin, org_user or partner)
Criteria for completion
The text was updated successfully, but these errors were encountered: