A problem in website User Design

In website design, are the accounts in the front and back of the system well separated or merged into one? For example, the account registered by the front-end user is the front-end user account, the background management is the account added by the Administrator, the front-end account cannot log on to the background, and the background account cannot log on to the front-end. In website design, are the accounts in the front and back of the system well separated or merged into one?
For example:
The account registered by the front-end user is the front-end user account, the background management is the account added by the Administrator, the front-end account cannot log on to the background, and the background account cannot log on to the front-end.

Reply content:

In website design, are the accounts in the front and back of the system well separated or merged into one?
For example:
The account registered by the front-end user is the front-end user account, the background management is the account added by the Administrator, the front-end account cannot log on to the background, and the background account cannot log on to the front-end.

This must be separated, and the coupling degree should be minimized during design. If the data volume is large in the future, it will be helpful for future sharding/database sharding, Vertical Split/horizontal split.

It is relatively easy to separate the settings. The Administrator account generally has various permissions to add, delete, modify, and query. Users can only view and modify personal information. Permission control is complicated to merge.