What's new - release notes
Where to find CultureMonkey product updates, how new features and fixes are communicated through the public changelog, and how to request something you'd like to see.
On this page
CultureMonkey ships improvements continuously - new features, refinements to existing ones, and bug fixes. This article is not the list of those updates itself. Instead, it's a pointer: it tells you where the up-to-date list lives, how we communicate what's changed, and how to ask for something you'd like us to build next.
If you're wondering "did that button always work like this?" or "when did this new report appear?", the changelog is the place to look. Bookmark it once and you'll always have an authoritative record of what shipped and when.
The single source of truth for product updates is the public Changelog (also called release notes) at culturemonkey.io/release-notes. It's organized by month, and every release is tagged with how many things are New, Updated, or Resolved. For help using any of it, or to suggest a feature, go through support.
Where to find product updates
The definitive, always-current list of what's changed in CultureMonkey is the public Changelog.
You can reach it directly at culturemonkey.io/release-notes. It's a public page, so you don't need to be logged in to view it, and you can share a link to any release with a colleague who doesn't have a CultureMonkey account.
The page is laid out as a timeline, grouped by month. The most recent releases sit at the top. Each release appears as a card showing the release title and a set of badges that tell you, at a glance, the shape of that release:
| Badge | What it counts |
|---|---|
| New | Brand-new features or capabilities introduced in that release |
| Updated | Existing features that were changed or improved |
| Resolved | Bugs that were fixed |
Click any card to open the full release. Inside, the details are split into the same three sections so you can skip straight to the part you care about:
- What's New - the new capabilities, with a short description of each.
- What's Changed - improvements and adjustments to features you already use.
- Bug Fix - issues that have been resolved.
How to search and filter releases
Over time the changelog builds up a lot of history, so it comes with a simple search and date filter to help you find a specific change.
- 1Search by keyword - type into the search box to find releases whose title, summary, or individual entries mention your term. This is the fastest way to answer "when did X ship?".
- 2Filter by date range - set a start date, an end date, or both to narrow the list to a specific window, for example everything released last quarter.
- 3Combine them - search and date filters work together, so you can look for a keyword within a specific period.
- 4Clear your filters - use the Clear or Reset control to return to the full timeline.
If a search or filter returns nothing, you'll see a short "no results" message. That means nothing matched your criteria, not that the changelog is broken - try broadening your keyword or widening the date range.
How CultureMonkey communicates releases
We use a small, deliberate set of channels so that updates reach you without becoming noise. Here's what to expect from each.
- The public changelog (confirmed). This is the canonical, complete record. Everything that ships and is meant for customers to know about lands here. If you only follow one channel, follow this one.
- This Help Center. When a release changes how a feature works, or introduces a feature significant enough to need its own guide, the relevant Help Center article is updated or added. So the article you're reading always reflects current behavior, and the changelog tells you when that behavior changed.
- Email and in-app announcements. For larger or especially useful updates, CultureMonkey may also highlight them through email to account admins and/or an announcement inside the product. These are used selectively for the changes most worth your attention, rather than for every release.
Product interfaces evolve. Rather than trying to remember when something changed, treat the changelog as your reference. It's dated, searchable, and authoritative, which makes it far more reliable than recollection when you need to confirm exactly what shipped.
Machine-readable release notes
The changelog is also published in a plain-text, machine-readable format at culturemonkey.io/release-notes.md (and each individual release has an equivalent .md address).
This exists mainly so that AI assistants, crawlers, and automated tools can read the release history cleanly. You almost certainly don't need it for day-to-day use, but it's handy to know it's there if you ever want to pull release information into another system or feed it to a tool programmatically.
How to request a feature
Good product ideas often come from the people using the product every day. If there's something you wish CultureMonkey did, we want to hear it.
The most reliable way to get a request in front of the right people is through support. Reach out using any of the methods in Getting help and contacting support, and frame your request so it's easy to act on:
- 1Describe the outcome you want, not just the mechanism. "I need to see participation by department in a single view" is more useful than "add a dropdown here".
- 2Explain the why. The problem you're trying to solve, and how often it comes up, helps us prioritize. A request tied to a real, recurring pain point carries more weight.
- 3Note who it affects. Is this just for you, for all your admins, for managers, or for employees? Scope helps us understand impact.
- 4Include an example. A screenshot, a sample of the data, or a walk-through of the steps you take today makes the request concrete.
We can't promise every request will be built, and we generally don't commit to timelines for individual ideas. But every request is heard, and requests that solve a common problem for many customers are exactly the kind of thing that ends up in a future release, which you'll then see land in the changelog.
If something is broken rather than missing - an error, a number that looks wrong, an email that didn't send - that's a bug, not a feature request. Report it through support so it can be investigated and, once fixed, it'll show up under Resolved in a future release. See also Frequently asked questions for common issues you can often resolve yourself first.
Staying current: a simple routine
You don't need to check for updates constantly. A light routine keeps you informed without effort:
- Bookmark the changelog so it's one click away when you need it.
- Skim it every few weeks, or whenever you notice something in the product looks different, to catch the New and Updated items relevant to how you work.
- Watch for emails and in-app announcements for the bigger changes, and open the linked release for details.
- Search before you ask. If you think a feature might already exist, a quick keyword search in the changelog (and this Help Center) often answers the question faster than a support ticket.
Frequently asked questions
Where is the "what's new" section inside the app?
The complete, dated list of updates lives on the public changelog at culturemonkey.io/release-notes rather than as a permanent panel inside the product. Larger updates may be highlighted with an in-app announcement or an email when they ship, but the changelog is the place to browse the full history any time.
Do I need to log in to read the release notes?
No. The changelog is a public page, so anyone with the link can read it, and you can freely share a specific release with colleagues who don't use CultureMonkey.
How far back does the changelog go?
It shows the full published history, grouped by month with the newest first. Use the date filter to jump to a specific period, or the search box to find a specific change.
Will I be told when something I use changes?
For significant changes, yes, through email and/or an in-app announcement, and the related Help Center article is updated to match. For smaller refinements, the change is recorded in the changelog even if it isn't announced individually, so the changelog remains the complete record.
How do I know if my feature request was built?
When a request ships, it appears in the changelog under What's New (for a new capability) or What's Changed (for an improvement). If you'd like a status update on a specific request in the meantime, ask support.
I found something that looks like a bug. Is that a feature request?
No - a bug is something that isn't working as intended, and it should be reported to support so it can be fixed. Fixes are published under Resolved in a future release. A feature request is for something the product doesn't do yet.
Where to go next
- Reach the team for help or to request a feature: Getting help and contacting support
- Answers to common questions: Frequently asked questions
- New to the platform? What is CultureMonkey?
Your feedback helps us improve the Help Center.