🚀 Produce Release Notes - September 20, 2025

We’re excited to share the latest updates to CultureBot! This release introduces improvements to permissions visibility, fixes for Employee Experiences setup, and more reliable reporting.

Highlights at a Glance

  • Permissions UX → Logged-in user info (name, company, avatar) now displayed.
  • Employee Experiences → Table matches Users Table, error validation, save button fixes.
  • Shoutouts Report → Creator/receiver data now populates correctly.

1. Logged-in User Info in Permissions

We’ve started adopting our new Permissions system, which comes with an updated UX:

  • The logged-in user’s name, company, and avatar are now displayed clearly in the UI.
  • This is prep work for upcoming improvements to how permissions and subscription checks are managed.

👉 This ensures more clarity and transparency when navigating the platform and lays the foundation for streamlined access management.

2. Employee Experiences Table Enhancements

We’ve updated the Employee Experiences table to match the look and feel of the Users Table. Alongside this refresh, we resolved several issues reported by customers:

  • Improved UX consistency: Employee Experiences table now aligns with Users Table styling.
  • Better error handling: Added proper validation for both frontend and backend.
  • Save button reliability: Fixed a bug where the button could get stuck during errors.

👉 These fixes also addressed the reported problem where Experiences were not posting in private channels and setup dropdowns were throwing errors.


3. Shoutouts Report Fixes

Customer Success reported missing data in the Shoutouts Report (Creator, Creator Email, Receivers, Receivers Emails columns). We’ve fixed this issue:

  • Reports now correctly display all Creator and Receiver details.
  • Reliability improvements to ensure customer-facing reports are accurate and complete.

💡 What’s Next?

We’re continuing to expand permissions management and improve reporting reliability. If you encounter issues or have feature requests, let us know — we love hearing from you!

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.