Skip to main content

Optional Workspace path

Feature Request

I would like to see the ability to enable an optional workspace path so that any forms in that workspace would have a URL like https://example.com/forms/<workspace-path>/<form-path>

This would allow us to then create access rules in NGINX/Cloudflare/etc.

For example, I could create a workspace called “staff” all forms in that workspace then have a URL starting https://example.com/forms/staff

I can then create rules that only allow visitors with the office IP to be able to view those forms, or setup Cloudflare access for that path

Posted by bigheadsmith ·
1 comment

Log in to comment and vote

Comments1

  • Archie

    Team•

    May 21

    Hi There,

    Thank you for taking the time to share this idea and for explaining the use case so clearly.

    The concept of having an optional workspace path in the URL structure—such as /forms/<workspace-path>/<form-path>—is very interesting, especially for scenarios where teams want to group forms logically and then apply external access rules (for example through NGINX or Cloudflare) based on those paths.

    Your example using a “staff” workspace and restricting access by IP or authentication rules helps make the use case very concrete and easy to understand. This kind of setup is often important for organizations that need an extra layer of control outside of the application itself while still keeping form organization clean and predictable.

    Appreciate you sharing this perspective.