@smallcircles @unattributed

Hmm... Well.... I thought at least a good year about these questions and did not yet come up with better words.

I mean, yes, our journalists are creators, which clarifies that. But then our users would be consumers and thats not better. And I cant call them journalists as not every user is one. So client maybe? But that would be a better fit for the Organizations as they are the ones talking with sales and paying the money.

All in all: I really am at a loss for better words here.

Nonetheless, thank you for your time

@smallcircles @unattributed

I do know about bounded contexts and DDD. Our code is structured to make clear in which context we move. I guess its more of a "Ubiquitious Language" Problem when talking with people about what we need to do and what not.

Did I mention that not *all* our "users" are journalists? Some are just "consumers". So I still need a word to mean both at the same time as they are the ones to get authorized to different parts/services of our Software.

@smallcircles @unattributed

My problem with using person vor journalist is as follows:

- The Organizations are the actual, paying customers (Sales domain, but also grouping element for authorization checks)
- We have journalists on both ends of our software. *our* journalists produce news which the customers journalists use to write their news
- people are everywhere in our system. So we need words to differentiate between them

@smallcircles @unattributed

What would be an alternative to the word User?

In my dayjob we have Organizations aka "Customers" with groups of "Users" who use our service for their journalistic work.