In users and groups, we need to define the users who will interact with the solution and how they are to be grouped.
Note
This should be from the business perspective, as apposed to how we might see users within a standard eZ publish installation.
It's also important to use the same language or terminology as the client. Although a standard user in eZ publish is an editor, the client may use the term author or publisher, in which case, we should use that name to avoid confusion. This allows us to design the system to meet these goals.
The following is an example of users and roles for an e-commerce portal. Firstly, we list and define the specific roles, then for each role we define any further details required.
This role includes visitors to the site that do not log in.