Coder Social home page Coder Social logo

Invite and Login flow about lms HOT 6 CLOSED

pateljannat avatar pateljannat commented on May 27, 2024
Invite and Login flow

from lms.

Comments (6)

pateljannat avatar pateljannat commented on May 27, 2024

@anandology Please review the flow and let me know if I missed something. Also, are the names of forms and doctypes okay?

from lms.

anandology avatar anandology commented on May 27, 2024
  1. When they click on it, they will be redirected to a form Request for Invitation.

I don't think I want to redirect to a different page. The Reqest invite should happen right on the page. There are two options.

Option 1: Add a textbox for email before the "request invite"

    [Enter your email     ] [Request Invite]

Option 2: Open a popup window and complete the invite process.

My preference is to go with option-1.

If the email is invalid or already used, it should show an error right there. Once the request is registered, the form will be replaced with a message "Thanks for your interest in Mon School. You'll recorded your interest and we will get back to you shortly."

from lms.

anandology avatar anandology commented on May 27, 2024
  1. When Admins change the status of the Request to Approved, these users will get another email. This email will have a link to another form called Your Request has been Approved.
  2. This form will ask for the basic information required to create a user in the app. [Full Name]

The email have a link to new signup form.

The NewSignup form will have the following fields.

  • Full Name
  • email
  • username
  • password
  • invite code

The invite code will be a query parameter and that will be autofilled.

  1. After this form is submitted, the information will be stored back in the doctype Request for Invitation and a User will be created using this information.

After the signup, the status of the "Request to Invitation" is changed to Complete Registered and the username/email is added to that document for cross referene. Please note that the signup email could be different from the invite email.

  1. When the User is created, the default welcome email will be sent to the user with a link to set the password.
  2. The users can then set a password and log into the app.

No need of these to steps.

from lms.

anandology avatar anandology commented on May 27, 2024

This doctype will have a status field. [Pending, Approved, Rejected].
[Pending, Approved, Registered, Rejected]

The status is changed to Registred when the the user signs up using the invite link.

Can we call this doctype InviteRequest instead of Request for Invite?

from lms.

pateljannat avatar pateljannat commented on May 27, 2024

My preference is to go with option-1.

Yes option 1 seems fine.

The invite code will be a query parameter and that will be autofilled.

Will the invite code be the same for all the users or will it be unique. Also, we will need to have some sort of validations for the code as well. Maybe a doctype with all invite codes and the field that indicates if the code has been used or not?

Please note that the signup email could be different from the invite email.

If the user uses a different email for signup do we override this in the doctype or save this in a new field?

The status is changed to Registred when the the user signs up using the invite link.

You mentioned in the previous comment that the status changes to Complete.

Can we call this doctype InviteRequest instead of Request for Invite?

Sure Invite Request is fine.

from lms.

anandology avatar anandology commented on May 27, 2024

My preference is to go with option-1.

Yes option 1 seems fine.

The invite code will be a query parameter and that will be autofilled.

Will the invite code be the same for all the users or will it be unique. Also, we will need to have some sort of validations for the code as well. Maybe a doctype with all invite codes and the field that indicates if the code has been used or not?

It will be different.

I think we can use the name of the document as the invite code.

Please note that the signup email could be different from the invite email.

If the user uses a different email for signup do we override this in the doctype or save this in a new field?

I think saving as a new field would be better.

The status is changed to Registred when the the user signs up using the invite link.

You mentioned in the previous comment that the status changes to Complete.

Registered. Updated that comment.

Can we call this doctype InviteRequest instead of Request for Invite?

Sure Invite Request is fine.
👍🏽

from lms.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.