Settings and activity
6 results found
-
374 votes
Hi community, thanks for sharing your continued interest here. We appreciate the importance of having assurance that mail you send from Xero is being received, and that being able to send from your own company email would increase confidence in this process.
I can confirm this idea has been continually reviewed by our product teams, and being able to send from your own company email is on their radar. Currently there are other priorities, and platform work that requires their attention, before they can consider this more deeply.
When there is opportunity to pick this up, I will share any news with you all here.
An error occurred while saving the comment 
Alistair Riddell
supported this idea
·
-
592 votes
Hi everyone, we appreciate all the feedback and votes on this idea. We know using Microsoft Entra ID SSO is now common practice for some businesses and being able to access Xero via a native integration with Entra ID would streamline how your teams log in and get set up in Xero, as well as help in managing access for larger teams and keeping things secure.
Our product team have been working with a small limited group of Partners to develop SSO capabilities. Though we can't give any definite timelines yet, we’ll keep this thread updated with news. Thanks
Alistair Riddell
supported this idea
·
-
780 votes
Hi everyone, as another step toward improving history of new invoicing you'll find you'll now see an entry when an invoice is sent, and the email address it has been sent to.
We appreciate this is something we've heard a fair amount of feedback on and we hope helps in your journey to using new invoicing.
We still have more enhancements on the way for history and I'll be back again when more updates land.
Alistair Riddell
supported this idea
·
-
389 votes
Hi everyone, we want to share that we've released a change to history for each time an invoice is sent.
Invoice history will now show the primary recipient email whenever an invoice is sent. This includes the initial and any subsequent send of an invoice.
We appreciate this has been a pain point for everyone that's joined in the idea here and hope this visibility improves your experience in invoicing.
We'd like to confirm how this works;
- This record is only applicable from here on in, there are no updates to any historical entries for sending.
- History will show the email of the initial recipient entered in the 'To' field any emails that you include as a CC or BCC option will not be shown.
We do want to highlight, that while the email will be recorded in majority of cases, there are a few scenarios our team have picked…
Alistair Riddell
supported this idea
·
-
606 votes
We appreciate everyone that's contributed here. Needs in more incremental permissions for bank accounts, have been clearly highlighted in your feedback - from protecting the confidentiality of payroll information to securely delegating reconciliation tasks for specific accounts.
Leaning in from our last update, our product teams have conducted lots of research of existing user roles, to highlight the most critical areas work is needed to power up our customers use of Xero.
Reporting and inventory are our first areas of priority, and you may have seen recent updates across ideas for these areas.
Permissions to bank accounts is another area that stood out in our research, but has more dependencies and will take longer to develop.
We'll keep you updated as our journey with roles and permissions evolve and there's more in the space of banking to share with you all.
Alistair Riddell
supported this idea
·
-
449 votes
Hey everyone, thank you for all your feedback. We’re on a long journey to provide more granular access and controls within Xero features that our customers need.
As you may have seen in some of our recent updates across other user roles ideas we’re currently in the process of adding more permissions within Reporting and Inventory. Further to this our research has highlighted Payroll and Banking as areas that more controls are most needed, and are on our agenda as we continue to develop permissions and access to features.
Your feedback here and through direct engagements with our teams have been extremely insightful, and we appreciate all your inputs.
I'll continue to provide updates on the development of roles for features as we progress.
Alistair Riddell
supported this idea
·
Clearly it's more important to spend their developer time on features like this "JAX" icon which has appeared, which nobody asked for and I suspect few people want. That way they can say "we've got AI".