Settings and activity
3 results found
-
644 votes
Hi community, we appreciate your continued feedback on having different default email addresses for various transaction types in Xero contacts, and the manual steps involved to ensure you're communicating with the right person for different purposes.
Currently, one way of managing this in Xero would be to include every additional person on a contact record in emails, and then removing those that aren't required when sending each transaction. However we totally get this isn't the ideal solution.
While being able to set different email addresses for differing transaction types is something we want to address longer term, like the idea for multiple addresses work for this feature requires cross-collaboration between teams in order to achieve.
Once the multiple addresses feature is live this is something we'll be able to consider more closely and provide further updates on.
We do regularly review all ideas here, and your input is vital. We'll…
Brian Walmsley
supported this idea
·
-
823 votes
Hi everyone, we appreciate wanting to hear from us on this idea and apologies for not commenting sooner. I can assure you this has not gone unnoticed and internally there have been reviews and discussions for how batch payments can be improved. We have the appetite, but as with all developments this must be weighed up and considered against many other important changes needed in product.
We want to be upfront that developing the ability to include Credit notes in Batch payments has not been planned at this stage.
As some may have seen, we do have work going on around being able to include Credit Notes as part of the reconciliation process. We understand for many on this idea the timing of including credit notes when you’re creating the batch payments is crucial, however we hope that when delivered at least being able to reconcile these more efficiently…
An error occurred while saving the comment Brian Walmsley
supported this idea
·
-
1,060 votes
Hi everyone, we appreciate the interest surrounding this idea, however we want to be open that we're unable to extend our log-out time past 60 minutes. Xero hold a lot of sensitive information including bank data and we're required to be as secure as online banking.
Any session information running on a web browser can potentially be stolen. If the session does not time out. You then have an infinitely long vulnerability window to session hijacking. Our best option is to keep a tight expiration window on the session cookie, and regenerate them frequently. Even setting a long timeout doesn't help with this - too long a timeout will greatly increase the risk of invasion or potentially jeopardise your personal data and the safety and integrity of the Xero application itself. This is why we maintain control of this.
If we detect there's been no activity on a page (e.g…Brian Walmsley
supported this idea
·
I've read several comments on this from other users - I concur