What for the list of permissions/permissions in a DB?

Question

Software design

I watched a bunch of admin panels, articles and videos, a table with permissions is created everywhere, but these permissions are empty entries without implementation in the code, there is a big chance of typos or storing outdated data, again, somehow it is necessary to maintain relevance on the production server, test and developers machines.
Now I am raising a new admin panel and decided why not store permissions in a simple array? Either the constants of which permission class, in the admin panel already show this data for role assignments, so it will be exactly the implementation first, the relevance of the code, and only then the entries in the database.
What could be the catch? What for all the same permissions in a DB? Have you had experience with this? Do migrations keep the table with permissions up to date?

Answer 1

In general, a classic solution from the time when memory was expensive - to store rights as a binary mask of the form 0101011101 - in which the role being determined depended stupidly on the bit number.
The problems that arise with this approach are quite obvious.
What exactly do you mean by "why not store permissions in a simple array" and "Why all the same permissions in the database?" It's not very clear from your question.