>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3579404. --> Reported by: [rosk0](https://www.drupal.org/user/325151) Related to !3 !1 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>I believe the module idea is good and now it's time to implement it.</p> <p>When various automated, or system, events happen, there could be a need to change the content in response to the event. These changes are typically done on a revision with a corresponding revision log message about the nature of the change. In revision UI Drupal shows a user account associated with a change. To avoid misleading the user looking at this UI we should use an account that is not Anonymous and not of that any other user.</p> <p>We already have a case where the content will be updated based on the CRM events triggering webhooks on the Drupal. With AI picking up the momentum I can see a case where we would want to integrate this module with <a href="https://www.drupal.org/project/ai">AI ecosystem</a> to make it clearly visible which content was created/updated by the <code>System Account</code> ( or <code>AI Account</code> ).</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Implement a module with the following features:</p> <ul> <li>configurable account display name, default value <code>System Account</code></li> <li>adds the <code>system_account</code> base field to the user entity, default value <code>FALSE</code></li> <li>creates a <code>system_account</code> during the installation and sets system_account field to <code>TRUE</code></li> <li>implements user query alter to filter out system account from the results - avoids output in manage users page and other user focused queries</li> <li>implements a rendering alteration to render a link to a system account as a plain text, if possible</li> </ul> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>community feedback<br> implementation<br> release</p>