Webflow does not natively allow individual clients to view their specific form data within the Webflow Dashboard, especially if submissions are routed to external platforms like Trello or stored in the CMS. However, you can achieve this functionality using a combination of CMS collections, Memberstack, and custom form workflows.
- Instead of just sending data to Trello, also route form submissions to a Webflow CMS collection using tools like Make (Integromat) or Zapier.
- Each form submission should include a reference to the client, stored in a unique CMS field (e.g., Client ID or email).
- This will create a log of submissions tied to a specific client in Webflow.
2. Restrict CMS Content with Membership Tools
- Use Memberstack, Webflow Memberships, or Outseta to create secure client login portals.
- Set up dynamic CMS pages where each logged-in client can only view their own submissions.
- Using Memberstack, you can define “User-specific content” by linking a CMS item to a user profile (usually via an email or unique identifier).
- Add a hidden field in the form, dynamically populated with the logged-in user’s unique ID or email using custom attributes (like
data-ms-member
) from Memberstack. - When the form is submitted, this identifies which client is submitting and is used in the Make/Zapier automation to ensure the CMS entry is correctly tied to that client.
4. Display Submissions in a Dashboard Page
- Create a client dashboard page using a CMS Collection List filtered by the authenticated user's ID.
- Each client sees only their own form submissions, formatted however you prefer (cards, tables, etc.).
5. Optional: Keep Trello Integration
- Trello can still be part of the workflow. Use a branching automation in Make/Zapier to send the same form submission data to both Trello and the Webflow CMS.
Summary
You can’t showcase form submissions per client within the Webflow Dashboard, but by storing submissions in the CMS and securing them with Memberstack or Webflow Memberships, you can create a personalized client dashboard inside your site. Use automation tools to bridge form data between Trello, CMS, and user identity.