Prompting the User to Save or Discard

Oct 13, 2025 by orovajewels.com 70 views

Feature Request: Enhancing Dashboard Experience with Automatic Layout Saving

Problem Statement

As a user of PostHog, a leading product analytics platform, you may have encountered a frustrating issue while working with dashboards. When editing a dashboard layout, rearranging insight panels, and then navigating away without saving the changes, the new layout is lost. This can be a significant problem, especially when working on complex dashboards with multiple insights and custom layouts.

Solution Overview

To address this issue, we propose a feature that automatically saves the dashboard layout or prompts the user to save or discard the new layout prior to navigating away. This feature will enhance the overall user experience, ensuring that users can work efficiently and effectively with their dashboards.

Automatic Layout Saving

One possible solution is to implement automatic layout saving. This feature would save the new layout as soon as the user makes changes to the dashboard. This way, users can work on their dashboards without worrying about losing their changes. However, this approach may not be ideal, as it could lead to unintended changes being saved.

Prompting the User to Save or Discard

A more user-friendly approach is to prompt the user to save or discard the new layout prior to navigating away. This feature would provide users with a clear indication that their changes have not been saved and give them the option to save or discard the new layout. This approach would ensure that users are aware of their changes and can make informed decisions about saving or discarding them.

Alternatives Considered

We have considered the following alternatives:

No automatic saving: This approach would require users to manually save their changes, which could lead to lost work if they navigate away without saving.
Warning message: Displaying a warning message when the user navigates away without saving their changes could be a simple solution, but it may not be effective in preventing lost work.
Save button: Adding a save button to the dashboard layout edit view could provide users with a clear option to save their changes, but it may not be intuitive for users who are not expecting to save their changes.

Additional Context

This feature request is related to a problem that has been reported by users in the PostHog community. The issue is not specific to a particular version or commit of PostHog, but rather a general problem that affects users across different versions.

Debug Info

- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]

Benefits of the Feature

The proposed feature will bring several benefits to users, including:

Improved user experience: The feature will ensure that users can work efficiently and effectively with their dashboards, without worrying about losing their changes.
Reduced frustration: The feature will reduce frustration and anxiety caused by lost work due to navigation away without saving changes.
Increased productivity: The feature will enable users to work more productively, as they will be able to save their changes and navigate away without worrying about losing their work.

Conclusion

In conclusion, the proposed feature will enhance the overall user experience of PostHog by providing users with a seamless and efficient way to work with their dashboards. The feature will save the new layout automatically or prompt the user to save or discard the new layout prior to navigating away, ensuring that users can work effectively and efficiently with their dashboards.
Q&A: Feature Request - Dashboard Layout Saving

Frequently Asked Questions

We've compiled a list of frequently asked questions related to the feature request for dashboard layout saving. Below, you'll find answers to some of the most common questions.

Q: Why is this feature important?

A: This feature is important because it will improve the overall user experience of PostHog. Users will be able to work efficiently and effectively with their dashboards, without worrying about losing their changes.

Q: How will the feature work?

A: The feature will save the new layout automatically or prompt the user to save or discard the new layout prior to navigating away. This will ensure that users are aware of their changes and can make informed decisions about saving or discarding them.

Q: Will the feature be available for all users?

A: Yes, the feature will be available for all users, regardless of their PostHog plan or version.

Q: Can I customize the feature to fit my needs?

A: Yes, users will be able to customize the feature to fit their needs. For example, users can choose to save their changes automatically or be prompted to save or discard their changes.

Q: Will the feature affect the performance of PostHog?

A: No, the feature will not affect the performance of PostHog. It will be designed to work seamlessly with the existing PostHog infrastructure.

Q: Can I request additional features or customizations?

A: Yes, users can request additional features or customizations by submitting a new feature request. Our team will review and consider each request on a case-by-case basis.

Q: When can I expect the feature to be available?

A: We're working hard to make the feature available as soon as possible. We'll provide regular updates on the status of the feature and let users know when it's available.

Q: How will the feature be rolled out?

A: The feature will be rolled out in a phased manner, starting with a small group of users. We'll monitor the feature's performance and make adjustments as needed before rolling it out to the broader user base.

Q: Can I provide feedback on the feature?

A: Yes, users can provide feedback on the feature by submitting a support ticket or reaching out to our team directly. We value user feedback and will use it to improve the feature.

Additional Resources

For more information on the feature request, please refer to the following resources:

PostHog Community Forum: Join the conversation on the PostHog Community Forum to discuss the feature request and provide feedback.
PostHog Support: Reach out to our support team for assistance with the feature request or to provide feedback.
PostHog Documentation: Refer to the PostHog documentation for more information on the feature request and how to use it.

Conclusion

We hope this Q&A article has provided you with a better understanding of the feature request for dashboard layout saving. If you have any further questions or would like to provide feedback, please don't hesitate to reach out. We're always here to help.