>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3330979. --> Reported by: [jurgenhaas](https://www.drupal.org/user/168924) Related to !288 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>As discussed on <a href="https://drupal.slack.com/archives/C0287U62CSG/p1672774635456189">Slack</a> we need new actions to access key value stores.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>There are multiple key value stores:</p> <ul> <li>Key value store</li> <li>Expirable key value store</li> <li>Private temporary key value store</li> <li>Shared temporary key value store</li> </ul> <p>Each of them supports any number of collections. ECA should have access to all of them, not just to its own collection.</p> <p>What needs to be decided, if ECA should have write access to all collections or only to its own and only limited read access to others.</p>