Use a custom content entity type to store the request
>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3545943. --> Reported by: [alorenc](https://www.drupal.org/user/3603980) Related to !3 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>There are some advantages of using a dedicated entity:</p> <p>We don't create the consumer entity from the beginning but only when the request is accepted<br> We have a storage for user who requested the client (which may be different from the user that owns the client)<br> We can store the request &amp; rejection reasons<br> We can keep a history of requests and even of rejections.<br> It's possible to store de desired label from the very beginning</p>
issue