This can happen if someone changes the users profile in production during the sandbox refresh. For example, the sandbox refresh has already copied over the profile and user info, but hasn't completed everything else, and someone changes the users profile in production at that right time, then yes the user would have a different profile in production than the new refreshed sandbox. I've seen this with data on records as well.
Please remember to check this as the best answer if you feel it helped.
Profiles are updated whenever anything related is updated. For instance if a field is updated, a custom object is added, FLS or CRUD are updated or other permissions are set or updated, then the Profile will be different. It's feasible that any of these changes took place within that 1 day window. Furthermore, it's feasible that depending on your Sandbox template, you're not copying down all the Profile information from Production, in which case the Sandbox profile would differ from production as well.
Have you confirmed that the Profile "changed" or only the last updated stamp changes? As James pointed out, the timestamp may get updated for many reasons, but in reality the profile really has not "changed".
This can happen if someone changes the users profile in production during the sandbox refresh. For example, the sandbox refresh has already copied over the profile and user info, but hasn't completed everything else, and someone changes the users profile in production at that right time, then yes the user would have a different profile in production than the new refreshed sandbox. I've seen this with data on records as well.
Please remember to check this as the best answer if you feel it helped.
Please remember to check this as the best answer if you feel it helped.
All Answers
Thx
Please remember to check this as the best answer if you feel it helped.