Settings and activity
4 results found
-
722 votes
Thanks for your feedback on Single Sign-On(SSO). We last updated this idea in October 2025, and we’re sorry it’s taken some time for us to provide another. We will do our best to keep you more informed of progress as it continues.
Where SSO is today
We’ve built an SSO capability for accountant and bookkeeper partner practices using OpenID Connect (OIDC). We ran a closed beta with a small group of partners, which is now complete, and those partners are connected. We’re still confirming how and when other accounting and bookkeeping partners can access it. SSO isn’t currently available to businesses or IT providers. We’ll share access details in a future update once they’re confirmed.
What we’re looking at next
We’re exploring what it would take to offer SSO to small businesses. Business needs differ from accountant and bookkeeper partners’, so we’re looking at:
- how a business and its users…
An error occurred while saving the comment An error occurred while saving the comment 
Matthew Flanagan
commented
Integration with identity providers is essential these days to let business control how they want their users to authenticate and ensure strong phishing resistant MFA can be enforced.
I run a cyber security business and it is embarrassing for Xero that this feature is yet to be implemented.
With the new financial year about to start I will be looking at other products for my accounting needs.
Matthew Flanagan
supported this idea
·
-
102 votes
Hi team, we've just launched passkeys to our first group of users. From this week, Xero Me app users who haven't set up MFA yet will be able to use passkeys to log into Xero. Next, we'll be progressively rolling this out to more users over the coming months. We look forward to and welcome your feedback here. As we have more news on the rollout I'll share with you on this idea.
Matthew Flanagan
supported this idea
·
-
37 votes
Thanks for sharing your idea, and letting us know the changes that matter most for you.
Now it's up to the community to get behind and support this idea. Make sure you share it with any colleagues that this could benefit, so they can add their vote too!
In the meantime, you might like to use Xero's own authenticator app, Xero Verify, which does support push notifications when you log in.
Matthew Flanagan
supported this idea
·
-
227 votes
Hi everyone, thanks for your feedback and for sharing your experiences with leave requests for employees who work non-standard hours.
Later this year, we plan to release the first stage of Working Patterns in AU Payroll.
This will allow users to set a one-week work pattern for each employee, which will automatically be used for leave and public holiday calculations in the pay run.
This initial release will establish the foundation for supporting a broader range of working patterns in the future, including more complex or changing schedules.
We’re moving this idea to Accepted while we explore how leave requests could work for these employees. Please continue sharing your specific scenarios, as they’ll help inform how we develop this functionality.
An error occurred while saving the comment Matthew Flanagan
commented
My business is doing the 4 day work week (8 hrs per day mon-thu) and this is crucial for us to be able to manage our employee leave. It currently thinks a day of leave is 6.4 hrs (32/5) and cannot account for the fact that we don't work on fridays and so leave should not be applied on those days. I thought of a hack of creating my own holiday calendar to handle the friday thing but the 6.4 hours per day problem still remains.
An error occurred while saving the comment Matthew Flanagan
commented
My business is doing the 4 day work week (8 hrs per day mon-thu) and this is crucial for us to be able to manage our employee leave. It currently thinks a day of leave is 6.4 hrs (32/5) and cannot account for the fact that we don't work on fridays and so leave should not be applied on those days. I thought of a hack of creating my own holiday calendar to handle the friday thing but the 6.4 hours per day problem still remains.
Matthew Flanagan
supported this idea
·
Stop putting prices up each year without implementing SSO. We need this to be secure. We don't need or want features like JAX.