> Just to let you know, wherever the UI has assumed it is a full profile and has not opened a ticket to make it so, there is a bug or a bug waiting to happen.

I believe we've had tickets for all of the different cases where the UI expects a full profile after an update (we're not bothered about create). We originally weren't expecting this, and picked items off the updated object onto the full profile. This was cumbersome and error prone, and therefore the strategy was changed everywhere.

> Based on this assumption made by the UI, I'm assuming the requirement is that a basic profile is never returned by the back-end API?

The UI expects the basic profile in all lists, searches, etc.

> For example if you update the user and are expecting the me object, what if it was the tenant admin that updated a user, I don't think it makes sense for the me to be returned to a different user

This is currently a non-issue. The me object is only expected when a user updates his own profile. When an admin updates the user's profile, it would never replace the me object.