UNIDA Gateway Platform Limitations
This page explains the current limitations of the UNIDA Gateway demo and the technical, operational and compliance areas that should be completed before full production use.
The current demo is designed to show product flow, dashboards, roles, verification direction and user experience. It is not yet a full production platform. Production requires database integration, secure file storage, admin review workflows, email notifications, audit logs, security controls and legal review.
1. Demo Scope
The current UNIDA Gateway demo is intended for product presentation, stakeholder understanding, investor discussion, developer handoff and early user flow testing.
It demonstrates the expected journey for businesses, investors, stakeholders and administrators, but some actions are simulated rather than fully connected to a live backend system.
2. Current Demo Limitations
Some demo data may be stored temporarily in sessions or static arrays instead of permanent database tables.
Document upload flow may show status visually, but production requires secure file validation, storage, virus scanning and admin review.
Verification stages can be previewed, but production should store every status change in database logs with reviewer notes and timestamps.
Registration, verification, approval, rejection and support notifications should be connected to a reliable email or SMS service in production.
Admin dashboards show the intended structure, but production should include real approval, rejection, update request and escalation actions.
Unny and Rieta may use common predefined answers in the demo. Production can connect them to a knowledge base, support tickets and approved platform content.
3. Upload and Document Review Limitations
The upload module should not be considered complete until the system supports secure upload handling, file type validation, file size limits, document expiry tracking, reviewer notes, document replacement and automatic status updates.
Production should also separate sensitive verification documents from publicly accessible folders where possible.
4. Verification Limitations
The verification process should eventually support:
- Profile completeness checks.
- Required document checks by user role.
- Submission locking after review begins.
- Admin review notes.
- Approval, rejection and needs-update status.
- Verification expiry for incomplete submissions.
- Audit trail for every verification change.
- Notifications to users after every important status change.
5. Dashboard Limitations
Dashboards should continue to be improved so each role receives only the information and actions relevant to them.
- Business dashboard: profile completeness, required documents, support needs, funding needs, verification status and opportunity submission.
- Investor dashboard: investment preferences, ticket range, preferred sectors, shortlist, meeting requests and verified opportunities.
- Stakeholder dashboard: support services, coverage regions, reviewed businesses, recommendations, follow-ups and reports.
- Admin dashboard: users, roles, permissions, uploads, verifications, support requests, policies, reports and platform settings.
6. Security Limitations
Before production, the platform should include stronger security controls:
- CSRF protection for all forms.
- Rate limiting for login and sensitive actions.
- Password reset and email verification.
- Role-based permissions connected to database tables.
- Audit logs for admin actions.
- Secure session configuration.
- Server-side validation for all inputs.
- Secure upload validation by MIME type, extension and size.
- Regular backups and recovery procedures.
7. Legal and Compliance Limitations
The Terms of Use, Privacy Policy, Verification Policy and Platform Limitations pages should be reviewed by a qualified legal professional before production launch, especially if the platform handles sensitive documents, investment-related information or stakeholder recommendations.
8. Communication Limitations
In production, user communications should be connected to reliable notification services. Important events such as registration, document upload, verification submission, approval, rejection, needs-update request, meeting request and support handoff should generate clear messages for users.
9. AI Assistant Limitations
Unny and Rieta in the demo may answer common questions only. Production assistants should use approved platform content, avoid unsupported claims and forward complex requests to a human support agent.
10. Contact
For technical, policy or support questions, contact:
- Company: UNIDA TECH LIMITED
- Platform: UNIDA Gateway
- Email: support@unidagateway.co.tz