**As** a Begin of the insertiondeveloperEnd of the insertion Begin of the deletion \[enter role of user\]End of the deletion
**I want to** Begin of the insertionpersist users queriesEnd of the insertion Begin of the deletion \[enter objective\]End of the deletion
**so that** Begin of the insertionI can use them as other queriesEnd of the insertion Begin of the deletion \[enter desired result\]End of the deletion

**Acceptance criteria**

* Begin of the insertionUser queries can be persisted in the database

* There should **not** be a UI for this. So no manual management like we do have them for project queries.

* This PR should only set up the database groundwork to store, manage and retrieve them from the DBEnd of the insertion Begin of the deletion <br>End of the deletion


**Technical notes**

* Begin of the insertion`queries` table is only work package queries

* `project_queries` are quasi the same table but only for project queries

* Investigate if we can consolidate all of them into one. But at least project queries and the new user query should be in one database table.&nbsp;End of the insertion Begin of the deletion <br>End of the deletion


**Permissions and visibility considerations**

* Begin of the insertion_AsEnd of the insertion Begin of the deletion _To whom isEnd of the deletion this Begin of the deletion feature visible?_

* _WhenEnd of the deletion is Begin of the insertiononly the backend preparation, no permissions are needed for now._End of the insertion Begin of the deletion it not visible?_End of the deletion


**Translation considerations**

* _Key terms and phrases in the key Begin of the insertionlanguages_ End of the insertion Begin of the deletion languages_&nbsp;End of the deletion


**Out of scope**

* <br>


_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._