search

homedepot / infinite-wish-board

A platform for kids to make wishes at Make-A-Wish, GA.
Apache License 2.0
27 stars 43 forks source link

API: Account Types #22

Open crstamps2 opened 5 years ago

crstamps2 commented 5 years ago

Right now, we envision 4 tiers of users: Admin, Sponsor, Parent/Guardian, and a Kid.

The Admin is essentially the make-a-wish (MaW) foundation high level users. They can essentially modify anything they see fit. They can also change other users permissions (probably?).

A sponsor is a person or company who agrees to fulfill a wish made by a kid. They probably should be able to see the kids wish and contact information of both the kid and the parent or guardian.

~A Parent or Guardian is just as it sounds. They are the parent or guardian of the kid. While the kid is ultimately the one making the wish, sponsors and MaW have to ultimately work with a parent. The parent should be able to manage the kids profile and information for the wish.~

~A kid is the kid making the wish. The point of the app is to let a kid, essentially, create a profile and make a wish. They are the initial user of the app, but beyond that, most logistics are handled with the parent/guardian.~

We decided to combine the kid and parent/guardian profile. Perhaps this is just a "wisher" profile. This should be in charge of all the aspects of the wisher (those details to be laid out later).

alex-hall commented 5 years ago

Does #24 satisfy the ability to figure this out?

The repo already gives you back the user profile object I believe (unless this was changed).

crstamps2 commented 5 years ago

It gives you back a user profile, but there wasn't any kind of type of user. In this case we were going for an admin style user. It is an assumption that we need one. I think we need to get a PM to volunteer some time to figure out what actually needs to go into this effort.

crstamps2 commented 5 years ago

I can also see a type being "parent" or "guardian". Something that signifies that the account in question is the legal guardian of the kid.

alex-hall commented 5 years ago

I'm guessing you're tackling this in #45 ?

If not, can I add this to that branch?

crstamps2 commented 5 years ago

45 we can definitely leverage the context feature of graphql, and easily make the frontend experience change based on who you are logged in as. But no, I was not directly tackling that in #45

aclaire-thd commented 5 years ago

Q: What can an admin user access/do that another user type couldn't? Maybe /wish-summary ?

If non-admin could see /wish-summary, then that user could be a parent/guardian. If so, then they should probably only see their wish listed... or maybe they can only get to the /wish-summary/THEIR_WISH and not the curation list?