There is a project, https://cab.razmorozka.com/, which does not have internal logic that you will need to create.
You will need to create for the site:
- A database for temporary storage of client data.
- Tracking and monitoring success with the ability to track data submissions.
- Maintaining statuses for documents.
- Generating documents based on templates.
- Translating documents (including OCR)
- Working with Google Drive and creating folders, storing and parsing data from there.
The admin panel should allow:
Viewing all users and editing their personal accounts by sections; before accessing the account, the operator can check certain sections of the new account and show more sections than the basic ones.
Seeing their uploaded documents/progress.
Seeing the date of the last upload, having reminders for clients to upload files.
Changing document statuses.
Adding comments and requests for revisions.
Uploading their versions of files if necessary.
Forming collective applications:
application template
power of attorney
list of participants
Administrator logic
If you look at the top right, there is a backoffice button, it can only be with us and there will be a rough vision of the operator interface, where inside will be:
1.1. Clients, our partners, and next to them their progress scale and a ball with a number of tasks required from us within the client (document verification).
Inside the client, their Google Drive folder will be visible, with uploaded and sorted documents by AI responses (assets, powers of attorney, personal documents), including automatically translated ones, as well as pre-template ones that will only require the client's full name and/or signature from us.
For each tab, we will need our own logic that we will describe later!
Client logic
1. The client logs in through various authentication methods (by contract number, by password, by one-time link, it doesn't matter for now) to the personal account located on the site razmorozka.com/login or somewhere there.
2. They see their status at the bottom left, sections that they need to submit (dynamic and editable at all stages)
3. Examples can be made in JavaScript so that they pop up as images right in the same account, without transitions anywhere.
4. The file after uploading automatically does the following in the backend:
4.1. Saves in Google Drive by the client's last name in the folder all documents and dynamically changes the status, progress, etc. + at the bottom in the uploaded documents column displays them (the client cannot delete them)
4.2. Goes through the API to our AI, which will check and perform a primary check of the document.
4.3. After the check, sends the document to the dynamically changing client dossier.
4.4. If possible, also sends it to Google Translate for translation into English (if it is not a scan; if it is a scan, places it in a separate folder and notifies us in the backend with a checkbox for manual scan verification)
Backend (preferred)
Integrations
Email notifications (SMTP)
Telegram webhook for manager notifications
Integration of third-party APIs (openwebUI)
Security requirements
Encryption (bcrypt).
HTTPS.
Access restriction to documents (URL signing, temporary links).
Error logging.
Protection against SQL injections, CSRF, XSS.
As part of the project and since we are dealing with confidential data, an NDA will be signed with all legal entities, and upon completion of the project, we will check the site for backdoors and leak possibilities.
Please send your related projects of personal accounts, or maybe demos, videos that show how and what you have done; we may pick up more options for developing the account from there.
