We cache organization permissions when loading the authorization
service, but when accepting an invitation, the user's permissions are
going to change.
We'd need to either invalidate the cached permissions, or invalidate
everything. This patch does the latter in the interest of un-breaking
accepting invitations, but the former might be a much cleaner approach.
cc @sandersonet @fancyremarker - as explained in Slack, I'm going to roll this out to un-break accepting invitations. I'm totally fine with reverting this or replacing it with a better fix.
We cache organization permissions when loading the authorization service, but when accepting an invitation, the user's permissions are going to change.
We'd need to either invalidate the cached permissions, or invalidate everything. This patch does the latter in the interest of un-breaking accepting invitations, but the former might be a much cleaner approach.
cc @sandersonet @fancyremarker - as explained in Slack, I'm going to roll this out to un-break accepting invitations. I'm totally fine with reverting this or replacing it with a better fix.