Multiple "Save to" locations in Request forms

Anna Giacobbe

Hi!

I haven't found a similar post suggesting this (apologies if there is one), but I'd love it if we could add more than one location to the Save to settings in Request Forms.

At the moment, we can only add one and typically rely on the "Create to…" functionality of blueprints, but not all of our request forms populate blueprints. As a result, we end up configuring a random mandatory single-select question in said form to add the other parent folders to each option to ensure proper cross-tagging.

Alexandra Torres

+1 supporting this. Already upvoted and we’d absolutely benefit from this in an enterprise setup.

While we often rely on blueprints and conditional logic to determine save locations, both introduce governance risk. If a blueprint is modified or deleted, requests may stop landing where they should, often without clear visibility. Similarly, when conditional routing is tied to a custom field, edits to that field can silently break the logic altogether.

In our environment, client and product custom fields are critical for routing, ownership, and reporting. Being able to define multiple Save to locations directly on the request form would provide a more durable, form‑level control that’s less dependent on downstream blueprint or logic integrity.

From a governance perspective, this helps ensure:

• Requests consistently land in the correct client and operational spaces
• Intake behavior remains stable as blueprints and fields evolve
• Reduced reliance on workaround questions purely for tagging or placement

For large, multi‑client teams like ours, this isn’t just convenience, it’s about reducing risk and maintaining long‑term intake reliability.