Save As
A Save As is a Salesforce action that creates a separate copy of the current report, dashboard, or list view under a new name, while leaving the original untouched.
Definition
A Save As is a Salesforce action that creates a separate copy of the current report, dashboard, or list view under a new name, while leaving the original untouched. You open an existing item, make changes if you want, then choose Save As to store those changes as a brand new item instead of overwriting what you started from.
The point of Save As is reuse. Rather than building a report or dashboard from a blank slate, you start from one that already has the right columns, filters, groupings, or components, then branch off your own version. The original keeps working exactly as it did, so other people who depend on it are not affected.
How Save As behaves across reports, dashboards, and list views
Save versus Save As, the difference that matters
The cleanest way to understand Save As is to put it next to plain Save. Save updates the item you currently have open. Any edits you made overwrite the stored version, and everyone who uses that report or dashboard sees the change. Save As does the opposite. It takes the current state, including your unsaved edits, and writes it out as a new item with a new name, leaving the original exactly as it was. Salesforce Help describes this directly for reports: Save As lets you clone the original report without modifying it, so the original stays intact. That single behavior is why Save As shows up so often in real admin and analyst work. It lets you experiment freely. You can open a report someone else owns, restructure it, add filters, change groupings, and keep the result as your own copy without any risk to the source. If you only had Save, every edit would be a commitment, and shared reports would be far more fragile than they are. Save As turns a finished asset into a safe starting point.
What the Save As dialog asks you for
When you trigger Save As on a report, Salesforce prompts you for a few details before the copy exists. You give the new report a name, you can add an optional description, and you pick the folder where it will live. The folder choice is not cosmetic. It controls who can find and run the report, because folder sharing decides access. A report saved to your private folder is yours alone. A report saved to a shared folder becomes available to everyone with access to that folder. Dashboards follow the same shape. The Lightning dashboard Save As, also labeled Clone, creates a dashboard with the same properties and widgets as the one you are viewing, then lets you adjust the settings and save it somewhere new. In both cases you are not just renaming. You are deciding where the copy lands and, by extension, who will use it. Treating the name and folder as deliberate choices, rather than defaults you click past, keeps your org tidy and your reports findable later.
Save As as a report development workflow
In mature orgs, Save As is not an occasional convenience. It is how report building usually happens. Someone needs a pipeline report split by region. Instead of choosing a report type and rebuilding every column and filter, they open the existing pipeline report, switch the grouping, and Save As under a new name. The new report inherits all the careful work already baked into the source. This compounds over time. A well built base report becomes a template that spawns a dozen variations, each one a few edits away from the last. The pattern also reduces mistakes. A report built from scratch can quietly miss a filter, like excluding closed records or scoping to the right record types. A report cloned from a trusted source starts with those decisions already correct. The tradeoff is sprawl. Because Save As is so easy, orgs accumulate near duplicate reports that drift apart over months. The discipline is naming and foldering, so a future you can tell the regional copy from the original at a glance.
Folder access and what you are allowed to save
Save As is not a free pass to put a copy anywhere. Your ability to save into a given folder depends on your access to that folder. To save a report or dashboard into a shared folder, you generally need at least edit access on it, not just view access. If you can only view a folder, you can run what is inside but cannot drop new items there. This catches people out. You clone a colleague's dashboard, expecting to save it next to theirs, and Salesforce only offers folders you can write to, often just your private folder. That is working as designed. Folder permissions are the access control layer for analytics, and Save As respects them. The practical move is to plan the destination before you start. If the copy needs to be shared with a team, confirm you have edit rights on the target folder first, or ask the folder owner to grant them. Saving to a private folder and moving the item later is also possible, but choosing the right home up front avoids an extra step and keeps the copy visible to the people who need it.
Where else Save As shows up
Beyond reports and dashboards, the same copy idea appears across Salesforce in different clothing. List views let you save a filtered view of records, and you can build a new view from an existing one rather than starting clean. Dashboard filtered views let a viewer keep their own filtered version of a shared dashboard without altering the source for everyone else. In builder tools, the equivalent is often labeled Clone or Save a Copy rather than Save As, but the behavior matches: take the current configuration and branch a new one. Flow Builder, for example, lets you save a flow as a new flow, which is the same preserve the original, edit the copy idea applied to automation. Recognizing this as one consistent pattern helps once you move between tools. The button might read Save As, Clone, or Save a Copy, yet the question it answers is identical. Do you want to change this thing, or do you want a new thing based on it. Save As, in every form, is how you choose the second option.
Common pitfalls and how to avoid them
The most frequent Save As mistake is accidental overwrite, which is really the opposite mistake: clicking Save when you meant Save As. You open a shared report, tweak it for a one off question, hit Save out of habit, and now everyone sees your tweak. The habit to build is to pause on shared items and ask whether your change should stick for everyone or just for you. If just for you, Save As. A second pitfall is folder confusion, where a copy lands in your private folder and the teammate who asked for it cannot see it. Always confirm the folder in the dialog rather than accepting the default. A third is name collision and drift. Generic names like Pipeline Report copy make the org unsearchable within weeks. Give the copy a name that explains how it differs from the source, such as Pipeline by Region, so its purpose is obvious. Finally, remember that Save As copies the definition, not a live link. The new report does not stay in sync with the original. Edit the source later and your copy will not change, which is usually what you want, but worth knowing when numbers diverge.
Trust & references
Cross-checked against the following references.
- Save Your Report in Salesforce ClassicSalesforce
- Build a Lightning Experience DashboardSalesforce
Straight from the source - Salesforce's reference material on Save As.
- Build a Report in Lightning ExperienceSalesforce
- Save Your Report in Salesforce ClassicSalesforce
Hands-on resources to go deeper on Save As.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does Save As do?
Q2. Where is Save As available?
Q3. Why use Save As?
Discussion
Loading discussion…