<?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: vSphere Access Control - Self-Service capability in VMware vSphere™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Access-Control-Self-Service-capability/m-p/2927905#M43344</link>
    <description>&lt;P&gt;Yes it is.&amp;nbsp; But, that question was posted by me with our company account that does not have my email address.&amp;nbsp; &amp;nbsp;Can you answer the question?&lt;/P&gt;</description>
    <pubDate>Thu, 08 Sep 2022 15:01:44 GMT</pubDate>
    <dc:creator>timstspry1</dc:creator>
    <dc:date>2022-09-08T15:01:44Z</dc:date>
    <item>
      <title>vSphere Access Control - Self-Service capability</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Access-Control-Self-Service-capability/m-p/2927890#M43342</link>
      <description>&lt;P&gt;All, I have used the Access Control feature of the Administration page in vSphere to add a custom role that allows our developers to manage snapshots.&amp;nbsp; My question is what is needed on the VM's that I grant that role to in order for the developer to take/delete/restore snapshots?&amp;nbsp; Does the VMware Player need to be installed on those VM's in order for this to work?&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;Tim&lt;/P&gt;</description>
      <pubDate>Thu, 08 Sep 2022 13:09:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Access-Control-Self-Service-capability/m-p/2927890#M43342</guid>
      <dc:creator>timstspry1</dc:creator>
      <dc:date>2022-09-08T13:09:11Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere Access Control - Self-Service capability</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Access-Control-Self-Service-capability/m-p/2927902#M43343</link>
      <description>&lt;P&gt;Is this other post also yours?&amp;nbsp;&lt;A href="https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Access-Control/m-p/2927886#M43341" target="_blank"&gt;https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Access-Control/m-p/2927886#M43341&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 08 Sep 2022 14:51:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Access-Control-Self-Service-capability/m-p/2927902#M43343</guid>
      <dc:creator>scott28tt</dc:creator>
      <dc:date>2022-09-08T14:51:26Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere Access Control - Self-Service capability</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Access-Control-Self-Service-capability/m-p/2927905#M43344</link>
      <description>&lt;P&gt;Yes it is.&amp;nbsp; But, that question was posted by me with our company account that does not have my email address.&amp;nbsp; &amp;nbsp;Can you answer the question?&lt;/P&gt;</description>
      <pubDate>Thu, 08 Sep 2022 15:01:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Access-Control-Self-Service-capability/m-p/2927905#M43344</guid>
      <dc:creator>timstspry1</dc:creator>
      <dc:date>2022-09-08T15:01:44Z</dc:date>
    </item>
  </channel>
</rss>

