Bartek Dybowski

Not overdue, I'll be reviewing this issue soon.

I've reviewed proposals and I like [the one](https://github.com/Expensify/App/issues/31002#issuecomment-1798886822) from @dukenv0307 - I think it identifies the root cause correctly and and the proposed solution is promising. The proposal from @NisargDeveloper...

I think we should give a try the **Solution 1** from [the proposal](https://github.com/Expensify/App/issues/31764#issuecomment-1823770551) of @tienifr - doing this the same way as for WS is a good idea as this...

@sophiepintoraetz We closed the PR from @dukenv0307 as turned out this solution won't work. So now, we are still waiting for proposals here.

Hey @sophiepintoraetz! I'll be OOO till January 6th, and right after that I'm leaving the C+ role and joining Waves. Could you assign another C+ engineer to handle this issue...

Ahh, right @tienifr... Thanks for pointing this out. @bfitzexpensify so I think we should switch to `Internal` here to get an opinion from BE engineer. What do you think?

@deetergp I don't know to be honest, but maybe @tienifr could help here? Could you point out the places where we do the same with `policyMembers`?

Hey @bfitzexpensify! I'll be OOO till January 6th, and right after that I'm leaving the C+ role and joining Waves. Could you please assign another C+ engineer to handle this...

yeah, there is such plan but I had no time for that recently... I will try to take a look at this in August

Ach... Ok, now I understand ;) You want users to extend `AuthorizedForFirst` and `AuthorizedFor` in their code. Maybe it would be better if users won't have to do it? They...