Integration with User Accounts about apis HOT 7 CLOSED

Discussed, This is in the pipeline

from apis.

OMGBBQYES!

The current pages use registrationToken + email to allow access (ex - for upgrading levels). Could we use that same paradigm for connecting people with their account for the first time?

Some other annoying things people ask for all the time that we can offload to a 'profile' page:

• Marketplace status
• Link to the Add Assistant form for accepted dealers
• Changing some info - we'll have to talk about what's allowed here, name and address for now?
• Adjust badge name until the end of pre-reg (from event object attached to the badge)
• Link to the upgrade form until the end of pre-reg ^
• View previous year's badge info?
• Staff info?
• Printing receipts for things? (dealers especially)

A larger policy conversation should happen around minor accounts.

from apis.

@alsaihn My first thought actually was to steal the data from the registration page and underneath the form offer a place for them to enter a Username and Password, if they desired.

If they wanted to link later, we could always link them by registration code and give them the opportunity to create an account separately as well.

All those ideas are crucial to getting it to work, and on the events/panels side it will make it easier for Programming to see if a panelist has registered, paid, gotten their badge, etc.

I'm thinking we could offload a lot of dates onto a front-end, publically viewable page where folks can do self-service stuff.

Here's a mockup: https://yuu.cloud/sc/w1i-4d55688.png

from apis.

The link later feature is also how we get last year's attendees to be able to get at their existing data. I'll have to write some de-duplicating/merging procedures for if someone's in the attendee table twice...

from apis.

Add some kind of "download tax receipt" to the portal also. Needs boilerplate and determination of what payments/donations qualify from the treasurer/board/someone.

from apis.

Something I've been playing with is a "register on Telegram" workflow. Telegram Passport already handles all of the personal information for an attendee, and payments can be accepted in-app as well with the Bot Payments API. Unfortunately, Square isn't supported at the moment, but I'll drop them a line and see if that'd be something they'd want to integrate with.

Register via Telegram would get APIS an SSO backend "for free" at the same time.

from apis.

Too many things to fix, will revisit in potential future iterations of project

from apis.