Almost without exception, no. Methods represent behaviors. Behaviors generally aren't supposed to change depending on who the consumer is. For example, when you walk into a restaurant, do you expect to get treated differently because of your gender or your skin color? Of course not. The implicit contract that every restaurant makes with the world is: "You come into my restaurant, I hand you a menu from which to pick things, and you eat the thing you selected." The fact that I might not know what one of the foods is is irrelevant. That's MY problem, not the restaurant's problem. The restaurant can't become a hair salon, simply because that's what I, as a client, want or expect. That's one of the ways we end up with the God Object antipattern. Clearly defining client and producer responsibilities is super important in OOAD.
So, that's the rule. There are some corner-case exceptions to it, but at the moment they aren't coming to mind.