Settings and activity
3 results found
-
7 votes
Barry Johnson
supported this idea
·
-
397 votes
Hi community, we appreciate many businesses have adopted single sign on with providers like Google, Microsoft Azure/Entra, and Okta to easily streamline logins to many applications and manage operational risk. Our team are staying close to votes and feedback of the idea here, and though we can't commit to development at this time, we will be sure to let you know of any progress toward enabling single sign on
Barry Johnson
supported this idea
·
-
514 votes
Hi everyone, we thoroughly appreciate your engagement and sharing how custom fields would be advantageous to you here.
With lots of work for 'building on beautiful' underway atm, we want to be honest that custom fields is not planned in the near term.
Some in the idea here, may find the recent addition of Notes that can be added within the Contact Details section of a contacts record useful in being able to record and view specific detail relative to a contact at present - More on this shared here
We'll continue to evaluate the viability of largely voted ideas such as this when there is resource, however this unlikely in the next 12 months.
An error occurred while saving the comment An error occurred while saving the comment Barry Johnson
commented
This is absolutely necessary as this may be required to give visibility to reseller customers who are selling products or services on to an end user. This has been open for a long time; please can this get some attention?
Barry Johnson
supported this idea
·
The response from Kelly is extremely disappointing. This is undoubtedly a thing which is important to hundreds of customers but perhaps something which is more important than "building on beautiful". I cannot understand why this is so difficult to be honest as in many cases; people would be looking to reference other fields which are there, or just want to add some additional information into fields which, I would hope, you would have as configurable placeholder fields in the tables of the database. If not, a schema extension should be trivial as it wouldn't require adjusting the existing fields; only adding user configurable placeholders which could then be referenced elsewhere. I'm really disappointed with this response as I thought Xero were more customer focused than this. With little functional differences introduced over the last 18 months, I don't know what else your devs could be working on which is of significantly greater importance than real world customer need.