You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Create BCeID
Pair 2FA app
Enter account details (payment method, account type, admin name, affidavit and notary info)
Submit draft account for review
BCOL Admin approves
or
BCOL Admin places on hold
or
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
The text was updated successfully, but these errors were encountered:
@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
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
or
or
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:
The text was updated successfully, but these errors were encountered: