Displaying individual client form submissions inside their Webflow dashboard is not natively supported, but it can be achieved using a combination of custom code, CMS structure, user authentication, and external automation (e.g., via Make or Zapier).
1. Structure the Webflow CMS Correctly
- Create a CMS Collection for form submissions with fields like:
- Client (reference field to a Client collection)
- Submission data (custom fields based on your form inputs)
- Timestamp or submission date
- Create a "Clients" CMS Collection with fields like:
- Client name
- Unique login ID or email
- Page slug (e.g., /dashboard/client-name)
2. Use Memberstack or Webflow Memberships for Login
- Enable authentication using Webflow Memberships or a third-party like Memberstack.
- Associate each user with their corresponding CMS Client entry.
3. Automate the Submission Flow to CMS
- When a Webflow form is submitted:
- Continue sending to Trello (if needed).
- Also send the data to Webflow CMS via Make (formerly Integromat) or Zapier:
- Trigger: New Webflow form submission.
- Action: Create a new CMS item in the "Submissions" collection.
- Link the submission to the correct Client CMS item through a Reference field using data like the logged-in user's email or ID (you'll need to capture this).
4. Restrict CMS Pages to Logged-in Clients
- Create a Collection Page like
/dashboard/client-name. - On this page, use a Collection List that filters submissions where Client (Reference) = Logged-in user.
- Restrict access using membership settings so that only the respective user can view their own dashboard.
5. Optional: Use Custom Attributes or User-Specific Tokens
- If you want lighter implementation, you can use custom attributes or URL query strings to filter CMS lists.
- However, this is not secure, as savvy users could change URLs and potentially view other data.
Summary
You can display form submissions to individual clients inside their Webflow dashboard by:
- Sending form data to the CMS via Make or Zapier,
- Using Memberstack or Webflow Memberships for user login,
- Filtering CMS items by client using Reference fields, and
- Ensuring page access is restricted per client.
This allows clients to log in and view only their own submissions in a secure and scalable way.