Skip to main content



Coupa Success Portal

How to Use Release Notes


Release notes help you quickly learn what's changed in each Coupa version and what the impact is on your existing Coupa implementation. The release notes aren't intended to be the definitive source of information about how features work, but instead as a tool to help you successfully upgrade to the latest version and take advantage of new features after your implementation is complete. 


The content in both the release notes and the product documentation is organized based on application and license details.

Release Notes

To make it easier to plan and execute your upgrade, the release notes include the following:

Deliverable Description Use
Planned features list List of all planned new features across the entire release schedule (initial release and updates) with impacts and planned release. Think of the planned features list as the schedule in an airport showing the status and details of each new feature. Updates to the list are available every two weeks with the scheduled maintenance updates.
Release notes List of actual changes to the product with each release.  A scheduled product update is available every two weeks and as necessary to resolve time-sensitive updates.
Roles and permissions diffs List of changes to roles and permissions since the last major release organized by role and by permission. Check to see the new permissions that have been added to the system roles. If you have custom roles, you need to manually update them with the permissions for any new features that you want to implement.
Integrations diffs List of changes to API and CSV formats since the last major release. Look for any of the objects which you have integrations for and consider if you want to take advantage of any of the new available fields. 

Documentation Formats

Different sections of the release notes are formatted differently. Use the following list of formats to understand the documentation.

Planned Features List

When trying to understand the scope of the new release, start by learning what features are planned for which release, and how they impact your instance. Think of it as the flight board in an airport. But instead of flight information, you can see when to expect new features to become available.

Column Description
Planned Feature The title or name of the new feature or enhancement. 
Description A brief description of the new feature, or details of what has changed since the previous release.
On by Default

Indicates if the change is visible somewhere your users can see it without the admin changing anything.

Early Access Program (EAP) features are off by default. For more information, see EAP Apps.

Roles and Permissions

Indicates if there are changes to roles or permissions.

  • If No, then there are no new or modified permissions.
  • If Yes, then check the Roles and Permissions section to understand the changes made to system roles, and if there are any migrations for your custom roles.

Indicates if there are changes to either the API or flat file (CSV) integrations.

  • If No, then there are no changes to the API or CSV. However, this doesn't mean that there aren't changes to an object's table.
  • If Yes, then check the Integration Updates section to see the changes and if they affect your integrations.
Status The first version where you can expect the feature to become available.

Permission Updates

A permission is a unique combination of a controller and action. The new permissions are organized by the controller name, and then each of the new actions is shown along with the details below. For more information, see Understanding Roles and Permissions.

Column Description Customer Thinking
Action The specific action added. For example, index, create, or show history. Tell me what new actions are added.
Description The description of what the action does or where it's applied. I need to know what the action does.
Associated permissions Some actions only work in association with other actions. You can find suggested combinations that can achieve business outcomes. Unless otherwise stated, the action listed is part of the same controller. What's the difference between index, show, create, and new? Help me understand how to build my custom role.
Migration The existing permission that, if in a custom role, causes the role to automatically receive the new action. I need to know when you change what a permission does, and what new permissions received some of the functionality of the old permission.