Good news, the new OAuth2.0 authorisation we’re working on will include an OpenID Connect identity layer that will enable single sign on.
It’s a big project and probably still a few months away from general release but it is coming.
Thanks for your patience.
45 votesMatthew Schinckel commented
This is actually turning into a pretty big deal.
It's compounded by the fact that an employee may only have one timesheet for a given period, even if the existing timesheet is already processed. This breaks the ability for using timesheets to do corrections (or advances, but I suggest that's not really the best way to do that anyway).
We are not prepared to send through timesheets as DRAFT, as they have already been approved in our system, and approving 300 timesheets again is a fairly big ask.
A workaround might be to send through the data as an EarningsRateLine in a Payslip, but in that case the cost cannot by associated with a Tracking Category.