<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Day 2 restrictions in VMware Aria Operations  Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Day-2-restrictions/m-p/2963268#M19363</link>
    <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is related to Aria Automation. Please use Arai Automation Discussion to ask the question.&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;</description>
    <pubDate>Tue, 11 Apr 2023 07:16:35 GMT</pubDate>
    <dc:creator>RickVerstegen</dc:creator>
    <dc:date>2023-04-11T07:16:35Z</dc:date>
    <item>
      <title>Day 2 restrictions</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Day-2-restrictions/m-p/2963190#M19362</link>
      <description>&lt;P&gt;Is there a way to restrict the access to deployments to the owner in Service Broker?&amp;nbsp; For example, I would prefer that a member not be able to request an action on a deployment that is not theirs, or at least limit those actions.&amp;nbsp; For example, in the development side it would be fine for them to request a deletion for their own servers, but not someone else's, whether by design or on accident.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is new to us and I am sure I am just missing a check box somewhere.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Apr 2023 15:09:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Day-2-restrictions/m-p/2963190#M19362</guid>
      <dc:creator>Flipper35</dc:creator>
      <dc:date>2023-04-10T15:09:34Z</dc:date>
    </item>
    <item>
      <title>Re: Day 2 restrictions</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Day-2-restrictions/m-p/2963268#M19363</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is related to Aria Automation. Please use Arai Automation Discussion to ask the question.&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2023 07:16:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Day-2-restrictions/m-p/2963268#M19363</guid>
      <dc:creator>RickVerstegen</dc:creator>
      <dc:date>2023-04-11T07:16:35Z</dc:date>
    </item>
    <item>
      <title>Re: Day 2 restrictions</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Day-2-restrictions/m-p/2963309#M19366</link>
      <description>&lt;P&gt;Sorry, thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2023 13:05:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Day-2-restrictions/m-p/2963309#M19366</guid>
      <dc:creator>Flipper35</dc:creator>
      <dc:date>2023-04-11T13:05:38Z</dc:date>
    </item>
  </channel>
</rss>

