USAID color palette for visualizations

DevResults lets folks choose from a number of color palettes when designing visualizations. Today we added USAID's official branding and marketing color palette, which looks like this:

USAID Palette.png

Now, if you'd like to create and download visualizations that use USAID's preferred color scheme for reports and presentations, you can do so by selecting this palette from the design dropdown for any graph or pie chart.


Heads up: common passwords will no longer be accepted starting Saturday, June 27

In the ongoing effort to improve security and protect privacy on your site, all passwords will now be checked against an internet database of common and/or leaked passwords.

Starting June 27, any new or existing password that is deemed compromised or too common will need to be reset the next time you login.


If you see this warning, try using a stronger password, or better yet, use a password manager that generates and remembers super-secure passwords for you!

Note: Single sign-on users will not be affected.

Rename 'awarding organization'

So far we've enabled pseudonyms (to rename certain data concepts in DevResults) for activities (e.g. 'projects') and locations (e.g. 'facilities').

Now we're adding 'awarding organization' to that list as well (e.g. 'donor'). Just send us a note at and we'll make that update.

Bear in mind, this will only change the text of your DevResults site; the DevResults Knowledge Base and all help articles will still refer to the generic terms 'activity', 'location', and 'awarding organization.' We do our best to use your preferred terminology in responses to Helpdesk tickets, but we may not be 100% consistent.

Search by user & organization in change history

Today we released a small update to the change history page.

Previously, the change history page let you filter changes by user and by organization, but there was no search option.

Now you can search for both users and organizations when you filter the change history list.


Rename 'Locations'

Back in November, we introduced the ability to rename 'activity' throughout your site with your preferred term (for example, 'project' is the most common pseudonym, but you might also choose 'program' or 'award'). Several clients have taken advantage of this already!

Now, you can do the same with 'locations'. Just send us a note at and we'll make that update.

Bear in mind, this will only change the text of your DevResults site; the DevResults Knowledge Base and all help articles will still refer to the generic terms 'activity' and 'location'. We do our best to use your preferred terminology in responses to helpdesk tickets, but we may not be 100% consistent.

Improved graph labels

Today we released a small improvement to the layout of graph dashboard tiles. To increase the clarity of these visualizations, we moved the unit to the y-axis label and placed the disaggregation choice at the top of the graph. It frees up a little more room for the legend as well.

Image of a DevResults graph visualization showing the unit labeling the y-axis and the disaggregation choice at the top

IATI Hub: support added for participating organizations' IATI activity IDs

Another small update to our IATI activity file exports — in the Partner Organization table, where you identify which organizations should appear as "participating organizations" in your IATI export, you can now add each organization's internal activity identifier or code. DevResults will concatenate each partners' organizational identifier with their provided internal activity identifier to create a unique activity identifier. This will help link your activity record to their's for enhanced traceability.


Updates to data entry grid

We've updated the grids where users enter data for direct entry indicators. These new grids look a little different, but more importantly, this allowed us to fix in place the column headings and row labels. Now, if you need to scroll through a big table, you'll always know what cell you're editing.

GIF shows column headings and row labels fixed in place as someone uses horizontal and vertical scroll.

Along with this update, we've separated the indicator Targets & Data tab into two tabs… Targets and Data. The targets are in the targets tab, and you can probably guess the rest.

Image shows the old version of indicator page options with "Targets & Data" as one tab, plus the new version with separate "Targets" and "Data" tabs.

Other changes you might notice: The comments field in data entry grids is a little different and you can now use the tab key to quickly move between cells.

Image shows editable grid with a blue-bordered comments box when user has clicked on a comments cell to edit.

Templates for importing program info

For those responsible for adding new program info to your DevResults site: Today we have a huge update that will make your life easier. All the major index pages in DevResults now have a Download Blank Template option. This will give you an Excel template for adding activities, indicators, organizations, users, or locations. You can find this option in the gear menu on any of these index pages.


The templates only include fields that can be edited via import, so you can fill out whatever columns you'd like and then upload it to DevResults.


In the future we will add built-in drop-downs for fields with a defined set of options, like an indicator's data source, but all templates are currently validated upon import.

Simplified Mechanisms

Today we've released an update to simplify the Mechanisms page. Mechanisms let you identify what kind of funding is received by your activities (or whatever you call them).

Previously, we offered a system with mechanism sub-types (like "Fixed Price") that each belonged to a type (like "Contract"). Activities were then identified with the Type (Sub-Type) pattern, such as "Contract (Fixed Price)".


These options were more complex than useful, so we got rid of them in favor of a simple list of mechanisms. This brings mechanisms inline with how we manage other category options like sectors and tags.


Your mechanisms table now shows the Type (Sub-Type) pattern. If the type matched the sub-type (like "Purchase Order" in this example), it's listed as-is. This matches the way mechanisms were already displayed for activities, so no changes have been made to how your mechanisms look and no action is required on your part.