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

Documentation - draw the account creation flow including the back-end and data #15221

Closed
JohnamLane opened this issue Feb 2, 2023 · 4 comments
Assignees
Labels
BA Pay Work for Pay Team

Comments

@JohnamLane
Copy link
Collaborator

JohnamLane commented Feb 2, 2023

In working on a change to the affidavit flow, we realized that we needed more info on what information is saved during account creation and review.

Using this online diagramming tool, https://app.diagrams.net/, please create the following flow:
BCeID new account creation

  1. Create BCeID
  2. Pair 2FA app
  3. Enter account details (payment method, account type, admin name, affidavit and notary info)
  4. Submit draft account for review
  5. BCOL Admin approves
    or
  6. BCOL Admin places on hold
    or
  7. BCOL Admin rejects

In all of the above steps, describe what data our system is storing and/or checking.
example: when a person has logged in, but hasn't submitted their account, what is saved in AUTH or KC?
things that are tracked may include:

  • orgs
  • users
  • tasks
  • affidavits
@JohnamLane JohnamLane added the Pay Work for Pay Team label Feb 2, 2023
@JohnamLane
Copy link
Collaborator Author

@jennyschan Here are some other details to get started:
Account creation (BCeID)
1. Client creates BCeID
2. Client logs in
3. Client pairs 2FA
4. Account creation flow starts
5. System checks if BCeID is the owner of an org already
a. If yes, then no affidavit upload is shown
b. If no, then prompt for affidavit upload
6. Client submits draft account application
a. Affidavit
b. Proposed account name (must be unique)
c. First admin's name (must match affidavit)
d. Payment method (if BCOL, account can't already be in use)
e. Other account info (address, email, …)
7. BCOL Admin sees the draft submission in the Pending Review column of Account Management
8. BCOL Admin review the draft submission:
a. Is the notary valid?
b. Does admin legal name match affidavit exactly?
c. Blank affidavit
d. Submission incomplete
e. Affidavit missing seal
9. BCOL Admin places draft submission on Hold
a. Describe DB changes to affidavit and task list
10. BCOL Admin reject submission
a. Describe DB changes to affidavit and task list
11. BCOL Admin approve submission
Describe DB changes to affidavit and task list

@JohnamLane
Copy link
Collaborator Author

Reason's a draft account can be put on hold:
image.png

@jennyschan
Copy link

@JohnamLane Thanks for the info... I will also add the email that client will receive as I just tested one.

@seeker25 seeker25 added the BA label Sep 28, 2023
@JohnamLane
Copy link
Collaborator Author

Older ticket - closing.

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

No branches or pull requests

3 participants