Skip to content
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

Open
2 tasks
cielf opened this issue Jul 7, 2024 · 6 comments
Open
2 tasks

Super admin should be able to add different kinds of users #4503

cielf opened this issue Jul 7, 2024 · 6 comments

Comments

@cielf
Copy link
Collaborator

cielf commented Jul 7, 2024

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

  • Superadmin can directly add users with the different roles described above
  • tests to demonstrate this functionality
@AweysAhmed
Copy link
Contributor

@cielf may I have this issue?

@cielf
Copy link
Collaborator Author

cielf commented Jul 9, 2024

Go for it!

@cielf
Copy link
Collaborator Author

cielf commented Jul 21, 2024

When testing this out, check the case mentioned in issue #4532.

@AweysAhmed
Copy link
Contributor

When testing this out, check the case mentioned in issue #4532.

Thanks. I'll look into that.

Copy link
Contributor

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.

Copy link
Contributor

Automatically unassigned after 7 days of inactivity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants