KYC Gathering

[dependabot]

User KYC

Purpose

Major flows

• Get user, get fully dehydrated user
  • A user may expose sensitive data like SSNs based on hydration state
• Create/Edit base document
• Create/edit subdocuments
• Due diligence/enhanced due diligence interfaces like EDD and ID Scores
• Upload Reg GG
• Create node
• Create user

User Collections

CTAs

• Create user
• Search by user ID, name, or email
• Filter user permissions
• Filter CIP tag
• Filter creation date range
• Download
• Clear

User collection data

• Name, ID, CIP, Permission, Date Join

Subgroups:

• Nodes, tables, logins, 2fas, transcripts, documents

User

CTAs

• Sign in as user
• Change Flag Status
• Change Permission
• Add Note (the note vs. public_note UI can be improved for admin-client dash communications)
• Change CIP tag (review if this is supposed to be a feature)
• Can not be searchable by name or email checkbox option
• Create document
• Update document
• Delete documents
• Create subdocuments
• Update subdocuments
• Delete subdocuments
• Preview subdocuments (review if needed)
• Create Node
• Add new 2fas
• Add new login emails
• Generate UBO
• Manage UserDuplicates (new)

Considerations

• add physical doc upload to create document flow
• scoping/permission scoping
• ID and EDD related information is core information for a document in terms of product design. https://docs.synapsefi.com/product-guides/id-score
• Client user profile vs. end user profile
• Sign in as user
• Client controls/CIP tag management
• Logins/Transcripts tables
• documents with meta fields
• organizing node creation information
• Generate UBO
• Manage User Duplicates (new)
• Possibly add a read UI that makes a user's controls/permissions clear
• Possibly add a read sanctions UI

Common Components

• Document Uploader (Create document, change sub document, create subdocument, etc)

Classes (TBD)

class User{
 // controls
 // profile
 // collection[] of documents

}
 

class Collection{
 // controls
 // document sheet that describes a user or business
}

class Documents{
 // subdocument: physical, social, virtual
}