Almost every platform that has been created they have the need of users with more than one &quot;type&quot;.
<ol>
<li>One which are actual users with normal privileges. The USERS.
</li>
<li>And the ones who have special privileges. The ADMINS.
</li>
</ol>
Admin users have special privileges that only they should have and not anyone else. Otherwise, if one user can manipulate data of another without there consent then the platform is a mess.
I found it always challenging to design a single database with solves the need of both users.
<ul>
<li>Should I have a <code>type</code> of the user stored in my database?</li>
<li>Should the first user who has registered on the platform would be the &quot;admin user&quot;?</li>
</ul>
I want to come to a collaborative conclusion about what is a better approach and why?

Almost every platform that has been created they have the need of users with more than one "type".

1. One which are actual users with normal privileges. The USERS.

2. And the ones who have special privileges. The ADMINS.

Admin users have special privileges that *only* they should have and not anyone else. Otherwise, if one user can manipulate data of another without there consent then the platform is a mess.

I found it always challenging to design a single database with solves the need of both users.

* Should I have a `type` of the user stored in my database?
*  Should the first user who has registered on the platform would be the "admin user"?

I want to come to a collaborative conclusion about what is a better approach and why?

How to distinguish admin users from normal users?

Product

Explore

Company

Blogs

Support