Philipp Schrenk<p><span class="h-card" translate="no"><a href="https://indieweb.social/@dries" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>dries</span></a></span> Thank you Dries for the exciting insights into Drupal's future.</p><p>If I have a <a href="https://mastodon.social/tags/Drupal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Drupal</span></a> 11 site already, will I be able to implement the <a href="https://mastodon.social/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AI</span></a> features and <a href="https://mastodon.social/tags/DrupalExperienceBuilder" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DrupalExperienceBuilder</span></a> and some other features as well easily with modules via composer or do I have to switch to <a href="https://mastodon.social/tags/DrupalCMS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DrupalCMS</span></a>?</p><p>Can I restrict the use of ExperienceBuilder completely or per component, based on user role/permissions?</p>