The org owner gets a 403 when attempting to publicize the membership for another user. That's one scenario, but there are other scenarios that have other results. If we describe one invalid scenario, it's tempting to try to describe them all. :wink:

Instead of enumerating each invalid scenario and the corresponding response code, I recommend just explaining the rules. Perhaps something like this will do the trick?

> The user can publicize their own membership. (A user cannot publicize the membership for another user.)