Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Commented Aug 29 at 7:27
  • Frame challenge: How would an end-user like to have the messages presented to them? Would they like to have all messages in a single list, or in separate lists, or maybe even a choice between those two options? Could the answer change if the number of accounts/roles that a user has grows in the future? Commented Aug 29 at 7:51
  • @BartvanIngenSchenau End users will receive a list of messages. In the future, if a user has multiple account types, they will have a separate list of messages for each account type. This question is not limited to messages — generally, how should API endpoints be designed for resource-based access when users have different account types? Commented Aug 29 at 8:10
  • @MizanRifat, usually the question doesn't come up because either the resource access is tied to a particular role, or you get the same response regardless of the role. Commented Aug 29 at 8:29