Proper Naming of User Groups in a System

Question

Proper Naming of User Groups in a System

Navigation

#1 by (2 votes)

3

I'm designing a system that will have multiple modules. It is possible until these modules are separated into different applications. Then I had a question that I had previously but could not get the answer:

What names should I give to different types of users of the modules of a system? Is there a default?

Existing example: Uber

Uber, with its users users drivers and passengers, has an application for each of these types of users. Uber states that drivers are their partners and not employees (and not customers). But what about the passengers? Are they customers of Uber or the drivers users? Do you understand where I want to go?

My case:

In the case of my project , my client would be a series of different professionals who would be the source of income for the system, and they would be users of a module of their own. These clients have their own clients, who would use another separate module to use the services of the professionals already mentioned. These users (clients of my clients) would not pay to use the system. In addition, there are the users who manage the (professional) clients of the system, using a CRM module that will be made for this.

At the end, there are at least 4 types of users:

My clients
Customers of my clients
Clients of my clients, with more restricted access profile
My client managers (my collaborators)

So how should you name each module and its users? knowing that there is still the open module, which can be accessed without authentication ...

terminologia design-pattern modelagem

asked by anonymous 27.06.2018 / 17:38

1 answer

How to extract web content (Web scraping) with C #? Connection in separate databases PDO - (multi-tenancy)

score 2 · Answer 1

Summary: Profile.

You can have in the same table the two types of users, with almost equal records, being differentiated only by a profile.

Already in your application (or applications) you can have a single type of login, which requires only user and password or login by facebook / google, and when identifying the user, you also search the associated profile and direct to pages or layouts.

This would be very similar to the different profiles within an application, for example a trainee user can see only the query menu, already an analyst user can see the query and request menus, and a user manager can see query, request, approval and reports. The control of which menus, features, or pages, whether displayed or not, depends on the type of the logged in profile and not the user itself.

EDIT: I ended up forgetting to say that the way you're doing is not much used, at least not the way I've seen being made by the companies and projects I've been through, unless it's a totally different application, another context, another thread, the users are treated as "equal" and differentiated by profiles.