How to organize and store the config for each user in order to do something one or more times?

Question

PHP

When authorizing a user, it is necessary to show the functionality that he has not yet seen, one or more times.
For example: we made a new modal window with new functionality, and you need to show it to everyone, then when you close the window or refresh the page, do not show it anymore.
Or something else has been added: some block, which, when a person has read it, should no longer be shown.

How to store states for each item. There was an option to make fields like: user_id, par1, par2. There was an option to store an object for each player in the form of json {par1: false, par2: true}. But how to update these objects for each user when adding functionality? You can add an object with the par3 property through a request to everyone and the new functionality will be added, but then everything will be re-viewed.

Answer 1

Are you talking about a browser? So store in the cookie what new items have already been shown to the user from those that have appeared in the last, say, three months. Just a list of IDs on one line. Why is it in the database?

Answer 2

It will be easier in cookies.

Answer 3

I did through the option {par1: false, par2: true}

Of course, I can add another object with the par3 property through a request to everyone and the new functionality will be added

- it is not necessary to update if, when receiving, there is no property, for example, view_modal, the object simply means that it is considered not viewed, when viewing and confirming, enter the view_modal=true property

Answer 4

Already did something similar. If you always show in order, then it is not at all necessary to store everything with everyone.
If all new features have IDs and are shown in order, then it is enough to store with each user the ID of the last viewed one. And no growth.
There is also a limitation, of course, you can only show as the ID increases, but you need to store much less.

Answer 5

How to properly store such data and remain scalable?

fields of the form: user_id, par, value
check if something was shown to the user - 1 request
mark what was shown - 1 request

Answer 6

json field. And you need to fill in not those that he did NOT see, but those that he saw. I saw - added the key. You can even json array.
No separate tables are needed, this is complete nonsense.