Appearance
Remaining Figma Design v1.1 Features
Reviewed: 19 August 2026
This file contains only the features that are still missing or incomplete. Completed features have been removed.
Backend handoff: Backend APIs needed
Admin panel
| Remaining feature | What is missing | Dependency |
|---|---|---|
| Detailed audit log | Field changes, source, user, filters, and export | Backend API needed |
| Old CRM archive | Legacy member data tab and search | Scope decision + backend data |
| Extended member-list data | Main contact, city, country, registration date, payment status, and last update | Backend response fields needed |
| Generic advanced filters | Figma-style filtering by arbitrary member fields | Backend filter contract needed |
| Complaint procedure dates | Procedure start/end fields from the Figma count-entry design | Scope decision + backend fields |
| Richer internal notes | Note title and complete author/date metadata | Backend fields + frontend |
Public registration
| Remaining feature | What is missing | Dependency |
|---|---|---|
| Umbrella membership details | Umbrella organisation, membership number/code, and membership-in-progress | Scope decision + backend fields |
Member portal
| Remaining feature | What is missing | Dependency |
|---|---|---|
| Extended organisation editing | Organisation name, KVK, phone, WZD, employee count, and umbrella | Permission decision + backend mutations |
| Payment-method choice | Bank transfer or iDEAL selection before payment | Scope decision + payment API |
| Payment Settings | Payment method, next payment, membership cycle, and status | Backend API needed |
| Change payment method | Member-facing update workflow | Backend API needed |
| Membership cancellation request | Member confirmation and admin follow-up workflow | Backend API needed |
| Partially blocked account | Portal-wide warning and permission-based download restrictions | Backend permission state + frontend |
| Document library | Templates, information documents, yearly files, search, filters, and downloads | Backend document API needed |
Email workflows
Backend verification is still required for the 14 Figma email templates and their event triggers. Pay particular attention to:
- More-information-required email.
- First and second payment reminders.
- Credit and additional invoices.
- Certificate-available email.
- Account-activation email.
Decisions needed before development
- Does post-login umbrella linking replace umbrella selection during registration?
- Are complaints full complaint cases or annual complaint-count entries?
- Which organisation fields may members edit directly?
- Should admins manage price tiers, or are prices backend-managed?
- Does this portal create invoices, or does SnelStart/backend automation own that workflow?
Recommended order
- Member Payment Settings and cancellation.
- Document library and blocked-account handling.
- Detailed audit log and legacy archive.
- Remaining registration and complaint scope decisions.