Admin & Settings Ideas

Admin, Settings and API Ideas

New Idea
Nigel Master


(See for context)


Currently releases are given to happen over a range of datas. There's no easy way to tell which release an instance is on please.


Please could a field be added to the Tenant Profile in Admin setup that gives the currently running version - that way we'll know when the release has happened, and can tell the difference from sandbox and production environments.

Kenta Zuora Staff

Zuora Staff

In the Notification Framework, an Event Trigger can compare old and new values on a given field (e.g. Invoice.Status and Invoice.Status_old). We would like for the subsequent callout built on the trigger to be able to reference this information

This would allow an external system to hold the business logic of determining actions based on the combination of the old/new values

yuliya_papl Senior Tutor

Senior Tutor

Currently on the User account level we see the creation date only.


For tracking and audit purposses would be great to have user account modification and deactivation dates. 

Status: Under Consideration

Agreed that this is a good idea. As we re-design user login, we will look to add this in.

Zuora-Support Community Manager

Community Manager

Require Audit Trail

Status: Under Consideration
by Community Manager on ‎01-13-2016 11:24 AM

Feature Request: Require Audit Trail

Status: under evaluation

Reference Number: DE5826/PMT-876

Business Need:

There are business requirements that are looking for the ability to have an audit trail for all fields and records. The requirement is to have an audit trail on all

- Account fields (including all custom fields)
- Subscription Fields (including all custom fields)
- Contact Address Fields (including all custom fields)
- Settings changes
- Users' actions


Status: Under Consideration

This continues to be high on our backlog, but we don't yet have a delivery date. We'll provide an update as soon as we have a more concrete idea on when we'll start on this feature.

gelaimr Z-Support SME

Z-Support SME

Use Case: When creating Notification Definition, we can only set one CommunicationProfileID at a time. it is a bit of task to create definition individually when a tenant has several Communication Profiles to manage and can this also result in a profile being accidentally missed. 


rdeloach Scholar


Export / Import configuration

Status: Coming Soon
by Scholar rdeloach on ‎01-21-2016 04:13 AM

It would be most helpful to be able to export a tenant configuration to a file, like meta-data or similar, and have the ability to import it into a tenant.  There are 2 use cases for this: first, to back up and archive configurations to satisfy auditor requests to validate no unapproved configurations have changed.  Second, in ensuring environment integrity in API Sandboxes or Services tenants to your source/production tenant.

Status: Coming Soon
zachmeyer Student


We would like the ability to pass parameters into the Callout Notification BaseURL. The URL is currently static.


For example, instead of a hard coded URL like this:


We would like something like this:{AccountId}


This is useful for REST APIs that expect specific information in the URL. We would like the parameter options to include custom fields as well.

KerryMcD Scholar


We have hundreds of Zuora users and it can be a real pain finding a user on the user list, especially if their first and last names are in the middle of the alphabet.  Would love the ability to: 


  • Search for a user by name
  • Sort the list by other columns like role
  • Filter the list (build list views like in Salesforce) so I could easily pull up a list of all Active users or all FinOps users for example.
  • Be able to export any of the results of the above (so export only active users for example).

This is a huge pain point for me as an admin. Thanks in advance!

bolaurent Master


Too many credentials!

Status: Under Consideration
by Master bolaurent on ‎05-25-2017 08:59 AM

I have credentials associated with Zuora:


  • Community
  • Connect
  • Support
  • Subscribed
  • University


This is kind of a pain; how about a unified auth system?

Status: Under Consideration

Hi @bolaurent, you're absolutely right, and we're working internally to provide a unified login capability across all Zuora properties. We just need a bit more time to get that done. Please bear with us for the time being!

jasong Tutor


Support confirmed with me that when a tenant is configured to use SSO and a user clicks the "logout" button, then it redirects users to the organization's SSO login page.

However, session timeouts go to the ZUORA login page. This, in my opinion, is the wrong behavior.

When a tenant is configured to use SSO, session timeouts should ALSO redirect users to the SSO page - that way if the SSO configuration still has an active token, the user can be redirected seamlessly back to zuora.

Please upvote this. The lack of this feature is causing pains within my organization. Smiley Happy


bolaurent Master


Give UI tabs useful names

Status: Under Consideration
by Master bolaurent on ‎09-23-2016 09:48 AM

I typically have multiple tabs open to the UI. All the tabs have the same, not helpful, name. 

I really want these tabs to be named with the record that is displayed (a product, an account, an invoice, etc).



Status: Under Consideration

@bolaurent, you're right, this is not that helpful. Let's see what we can do.

bolaurent Master


unified search in Zuora UI

Status: New Idea
by Master bolaurent on ‎03-03-2017 08:09 AM

It's a significant source of friction that I can't search for an object until I click on that object name in the sidebar, then the search window on the right.


Please give us a unified search field, displayed on all UI pages in the same location, that searches all objects. So, for instance, if I enter "INV0000123" it gets me to an invoice, and if I enter "Foobar" it displays accounts and subscriptions named foobar*.


Also, if there is only a single hit (as for instance, "INV000123" would produce), then take me directly to the record.



S_Mizu Scholar


Display Order of Custom Fields

Status: Under Consideration
by Scholar S_Mizu on ‎02-03-2016 12:32 AM

The custom fields are currently displayed in the order in which the custom field was created. If I want to add a new custom field that is related to existing custom field, I would like to position it around the related custom field, but the new custom field is displayed at the bottom of the custom fields. I would like to control the display order of each custom field.

Status: Under Consideration

Great idea, please continue to vote to give us a sense of priority on this.

brianh Newly Enrolled

Newly Enrolled

Setup API to allow user management

Status: New Idea
by Newly Enrolled brianh on ‎12-22-2017 07:52 AM

There are API interfaces to manage most of Zuora except the users (not customers) of the organization. We would love to have our management systems and scripts to be able to update or change the status/role/etc of our users via an API.  Part of this stems from the fact that user searching/sorting/editing in the web gui is painful when finding and editing users (no filtering/searching, limited results on one page forces multiple Next, Next, Next, when the users name is in the middle of the alphabet, etc).

alexboster Senior Tutor

Senior Tutor

We have a critical custom field (that represents the customer's unique database id in our systems) that should be unique. It would be very helpful if we could set the custom field in Zuora to be unique, such that Zuora would not allow us to create multple objects (in this case, Accounts) with the same custom field value.


Our use case: When the customer converts (enters payment information), we send that to Zuora directly from their browser via the REST API. Our system then receives a New Subscription callout notification if the conversion succeeds. This is probably very standard.


Then potential issue is that browsers cannot be considered 100% reliable. So it's possible we could send the Create Account REST call multiple times, even with various mitigations in our Javascript code. We can detect that this has already happened (indeed, every callout notification after the first would generate an error in our system that could be escalated). But it would be better if Zuora would just reject the redundant records.

Renaldo Zuora Staff

Zuora Staff

Allow a custom field lengths of 2k or 4k chars.


Customers are finding they require custom fields that can hold more text. 

Un-indexed custom fields, or additional notes or description fields of 2 to 4k characters are being requested.

Status: Under Consideration

I'd love to hear what the use cases are for 2k or 4k fields. At some point, these are starting to be used as a data store, could the new Attachment feature be used for this instead? Please note that we're also looking into adding a concept of Notes that, similar to Attachemnts, could be entered on select Zuora objects (likely Account, Subscription, and Invoice).

dmdaniel Savvy Scholar

Savvy Scholar

Recycling Bin

Status: Under Consideration
by Savvy Scholar dmdaniel on ‎05-11-2016 06:53 AM

There are a couple of issues with the delete permissions, so this idea is a combination of a number of different ideas.


- By default delete permission are enabled in the "Standard Profiles", they should not be - giving delete permission should be a more active task by an administrator.


- Customising the default profiles is not possible, so you need to add a new profile to remove delete privledges. 


- In an active system you then need to identify the users to change to this profile, unfortunately there is no report.  So its a matter of clicking on each user and changing (easy to make a mistake)


- There is no way to remove the standard profile, so new users may get assigned to the wrong profile quite easily. (As this would be the detault option).


Ultimately it is very difficult to robustly control and remove delete permissions -  to address this a couple of things need to be done:-


- make the default profile editable.

- remove delete capabilities from the out of the box profile.


Even with all of this, mistakes can happen, and ultimately there needs to be a capacility to un-delete mistakes (or even malicious actions) which could otherwise risk the survival of a business.


There really needs to be an un-delete capability or a recycling bin (simiar to salesforce) that would allow object that have been deleted to be restored.




Kyle Zuora Staff

Zuora Staff


Status: Under Consideration
by Zuora Staff on ‎06-03-2016 04:41 PM

I think it would be a great idea to allow the ability to create/read/update users in Zuora via the REST apis. Is this something that is being prioritzed at this point?


Status: Under Consideration

Hey @Kyle, great idea and we're looking to do this along with a REST API for the rest of Zuora Settings as well. The likely timing is sometime in 2017, given other items we're working on, but would love to see this voted up to give me more feedback on the priority.

vkannan Tutor


Allow AqUA to return JSON response

Status: Unlikely
by Tutor vkannan on ‎08-11-2017 02:32 PM


Today when we execute AqUA, the only option is to get back a file with the data.

Can we look at returning JSON for the same response.

We can look at creating page sizes to restrict the size.



Status: Unlikely

@vkannan, why do you prefer JSON over CSV, for extracts that are meant to be quite large?

conklinb Partner


we currently have 1 catalog that contains 1200 rate plans alone, we are expecting to leverage the translation profile capabilities to handle branding of names which are currently not only at the product catalog level, but also within the rate plan names.  This limit will significantly affect how much we can leverage this tool, especially if we can not also delete translations that we no longer need going forward (which is already submitted as an idea)