Admin - Select organization on registration

[palisadoes]

Is your feature request related to a problem? Please describe.

We are working on migrating the approval of requests to join organizations to a new Admin screen as outlined in this issue:

• Add membership request feature for ADMIN  #1416

Prior to this the process was:

1. New registrants joined the Community
2. Super Admins would approve the request
3. Approved registrants would login and select an organization

There were disadvantages to this approach:

1. This gave too much responsibility to the Super Admin who may not necessarily know people requesting to join in the way an Admin would.
2. The two step process where the organization was selected post approval, could have been reduced to a simpler single step.

Describe the solution you'd like

TALAWA API

• This new requirement means that:
  1. New USERs and NON_USERs will need to select an organization when registering so that the request can be directed to the correct organization's Admin screens.
  2. The setup script needs to create a single organization with a generic name on installation to facilitate registration to choice of at least one organization
  3. There can never be less than one organization in the DB
  4. The registration mutation must include organization ID information that issue Add membership request feature for ADMIN  #1416 will be able to detect.
  5. The current GitHub action pull request workflow needs to be updated so that the default organization is created successfully. This is in addition to the already existing test data importation test.
  6. The default organization creation mode mutation needs set the registration approval required flag to True to err on the side of caution.

TALAWA MOBILE

• This new requirement means that:
  1. The user registration screen(s) will need to prompt for the organization and use the updated Talawa API registration mutation.
  2. The screen(s) design must follow the guidelines of our Design System found here:
     • https://docs.talawa.io/docs/design/ux/ux-design-system

TALAWA ADMIN

• This new requirement means that:
  1. The user registration screen(s) will need to prompt for the organization and use the updated Talawa API registration mutation.
  2. The screen(s) design must follow the guidelines of our Design System found here:
     • https://docs.talawa.io/docs/design/ux/ux-design-system

OTHER

1. You will need to write tests for the updated code
2. All other functionality must be maintained
3. We will need to add your Figma page designs to our official Figma document

Describe alternatives you've considered

• N/A

Approach to be followed (optional)

• See above

Additional context

1. Related issues:
   1. API - Select organization on registration talawa-api#1703
   2. Mobile - Select organization on registration talawa#2330
   3. Admin - Select organization on registration #1440
2. User definitions in the DB schema
   

Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship

• Student Internship Programs talawa#359

[Sejal1411]

Would like to contribute! Pls assign.

[karthxk07]

@palisadoes Can i work on the Talawa-admin part for this, please?

[manishjha-04]

@palisadoes can i work on this?

[Cioppolo14]

@Sejal1411 Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. We sometimes give exceptions for more urgent cases and sometimes we lose track, but the policy stands. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too.

[Dcode2100]

I would like to work on the talawa-admin part of this issue please assign it to me

[Sejal1411]

@Cioppolo14 I have unassigned myself from one of the issues. Can i get assigned to this issue?

[karthxk07]

@Sejal1411 i got this issue assigned already , maybe you can work on the api part for the same 👀

[Cioppolo14]

@Sejal1411 If this issue wasn't already assigned, at this point I could assign you. In the future, if you are first to comment requesting an issue and you really want that issue, make sure you have less than 2 total issues for when I go to do assignments. Thank you for understanding.

[palisadoes]

@karthxk07

1. We will need to add your Figma page designs to our official Figma document
2. Please plan for this

[palisadoes]

@karthxk07

1. The blocking API PR for this issue has been merged.
   1. Signup route changed talawa-api#1741
2. Please proceed with your work on this with urgency

[karthxk07]

@palisadoes I had been working on another issue and have been ignorant about this one. I will be immediately on this sir 👍

[karthxk07]

@palisadoes Sir , in the select organization page, should the user have options to join multiple organizations or only one to start with. Can it be something like this where instead of topics we have organizations ?

[palisadoes]

One

[karthxk07]

@palisadoes Sir, Is something like this fine?

https://www.figma.com/file/CCUKLqu8AYb3uBGQrXLJwE/Untitled?type=design&node-id=0%3A1&mode=design&t=5FkVhuIFeHKU7avH-1

[palisadoes]

How can you make the selection a part of the existing registration screen?

[karthxk07]

@palisadoes Sir, maybe we can add a dropdown field to select from all available organisations?

Something like this? https://www.figma.com/file/6xACotBTh0GU3POVqZbMX0/Untitled?type=design&node-id=0%3A1&mode=design&t=4tJRjxZscGMivMpw-1

[palisadoes]

OK

[palisadoes]

When do you think you'll be able to raise a PR for this?

[karthxk07]

@palisadoes Sir , I have completed the frontend part , I am working on implementing the logic. I will make the PR ASAP or latest by this weekend.

[karthxk07]

@palisadoes Sir, Is this signUp mutation behavior expected, because in the above merged blocking PR , the expected output was somewhat different. How should I proceed about this?

Screencast.from.2024-02-08.22-29-31.webm

[palisadoes]

If that case comment on the PR's issue with what you'd expect and let's reopen it to have the expected behavior

[palisadoes]

However, this PR was created to rectify a previously identified bug.

• Sign up route changed with bug fix and proper data importation talawa-api#1770

[palisadoes]

@karthxk07

The API PR is now complete. You can proceed. This is could be showstopper issue for new registrations. Do you have time to complete this by the weekend?

• API - Select organization on registration talawa-api#1703

[karthxk07]

@palisadoes That is good news sir. Unfortunately I have exams till the end of the week. But , most of the other work is done so, I can work modestly this week, get done with most work on weekend plus one two more days and make the PR ASAP.

[palisadoes]

Good luck with your exams. That comes first. Thanks for the update.

[palisadoes]

@karthxk07

Be aware of this:

• Cannot register as LAST_RESORT_SUPERADMIN_EMAIL talawa-api#2165

[karthxk07]

@palisadoes Yes sir. I have already fixed it locally . This issue will rise for not only the super admin but also for every user trying to register. I will push it up with all the changes.

[karthxk07]

@palisadoes Sir , there have been a lot of changes to the api repo which has rendered a large part of the admin side inconsistent.

Major problem, The usertype is removed from the login mutation so now we cannot directly see if the user is a ADMIN, SUPERADMIN, or a USER.

How do i proceed further with this?

[palisadoes]

The userType methodology was removed. The description of the new way can be found here:

• API: Fix the usage of userType talawa-api#1711

[karthxk07]

Screencast.from.14-04-24.12.55.33.PM.IST.webm

@palisadoes Sir , this is ready. Does this look fine?

[palisadoes]

Yes. Finally!

How does it work with a fresh installation where the LAST_RESORT_SUPERADMIN_EMAIL is set? Where the email address isn't one of the sample data users, for example

[karthxk07]

@palisadoes Sir , here is how it works for LAST_RESORT_SUPERADMIN_EMAIL.

Screencast.from.15-04-24.07.16.02.PM.IST.webm

[palisadoes]

Thanks. Please submit a PR

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.