<?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>article Alero: Is there a configuration setting that allows internal and Alero users to use the same managed account? in Remote Access Articles</title>
    <link>https://live.paloaltonetworks.com/t5/remote-access-articles/alero-is-there-a-configuration-setting-that-allows-internal-and/ta-p/1429948</link>
    <description>&lt;H3&gt;Question&lt;/H3&gt;
Is there a configuration setting that allows internal and Alero users to use the same managed account?

&lt;H3&gt;Answer&lt;/H3&gt;
&lt;P&gt;There is no configuration to allow Alero users and internal users to use the same account. This would imply that the account needs to reside in multiple safes, which is something we strongly discourage because of password synchronization issues that would result.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What you can do is&lt;/P&gt;
&lt;P&gt;1. Determine which accounts the Alero vendor should have access to&lt;/P&gt;
&lt;P&gt;2. Create a separate safe strictly for Alero users, with the Alero users having only Use and List&lt;/P&gt;
&lt;P&gt;3. In the same safe, the internal users should have whatever permissions they need. This could be just use, retrieve and list&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What you want to avoid is giving Alero users permissions on 'internal' safes - that is, safes that have accounts that the vendor should not access. Obviously, you don't want to give your vendors excessive rights. The separate Alero safe with only those accounts that the vendor can access (Use, List) will provide the necessary permissions and to which you can add internal users with more permissions if necessary.&lt;/P&gt;
&lt;H3&gt;Issue&lt;/H3&gt;
&lt;P&gt;Alero: Is there a configuration that would allow both internal and vendors to use the same account and connect through PSM?&lt;/P&gt;
&lt;H3&gt;Environment&lt;/H3&gt;
&lt;P&gt;Alero / PSM&lt;/P&gt;
&lt;H3&gt;Resolution&lt;/H3&gt;
&lt;P&gt;There is no configuration to allow Alero users and internal users to use the same account. This would imply that the account needs to reside in multiple safes, which is something we strongly discourage because of password synchronization issues that would result.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;What you can do is&lt;/P&gt;&lt;P&gt;1. Determine which accounts the Alero vendor should have access to&lt;/P&gt;&lt;P&gt;2. Create a separate safe strictly for Alero users, with the Alero users having only Use and List&lt;/P&gt;&lt;P&gt;3. In the same safe, the internal users should have whatever permissions they need. This could be just use, retrieve and list&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;What you want to avoid is giving Alero users permissions on 'internal' safes - that is, safes that have accounts that the vendor should not access. Obviously, you don't want to give your vendors excessive rights. The separate Alero safe with only those accounts that the vendor can access (Use, List) will provide the necessary permissions and to which you can add internal users with more permissions if necessary.&lt;/P&gt;</description>
    <pubDate>Wed, 05 Nov 2025 05:01:21 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2025-11-05T05:01:21Z</dc:date>
    <item>
      <title>Alero: Is there a configuration setting that allows internal and Alero users to use the same managed account?</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-articles/alero-is-there-a-configuration-setting-that-allows-internal-and/ta-p/1429948</link>
      <description>&lt;H3&gt;Question&lt;/H3&gt;
Is there a configuration setting that allows internal and Alero users to use the same managed account?

&lt;H3&gt;Answer&lt;/H3&gt;
&lt;P&gt;There is no configuration to allow Alero users and internal users to use the same account. This would imply that the account needs to reside in multiple safes, which is something we strongly discourage because of password synchronization issues that would result.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What you can do is&lt;/P&gt;
&lt;P&gt;1. Determine which accounts the Alero vendor should have access to&lt;/P&gt;
&lt;P&gt;2. Create a separate safe strictly for Alero users, with the Alero users having only Use and List&lt;/P&gt;
&lt;P&gt;3. In the same safe, the internal users should have whatever permissions they need. This could be just use, retrieve and list&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What you want to avoid is giving Alero users permissions on 'internal' safes - that is, safes that have accounts that the vendor should not access. Obviously, you don't want to give your vendors excessive rights. The separate Alero safe with only those accounts that the vendor can access (Use, List) will provide the necessary permissions and to which you can add internal users with more permissions if necessary.&lt;/P&gt;
&lt;H3&gt;Issue&lt;/H3&gt;
&lt;P&gt;Alero: Is there a configuration that would allow both internal and vendors to use the same account and connect through PSM?&lt;/P&gt;
&lt;H3&gt;Environment&lt;/H3&gt;
&lt;P&gt;Alero / PSM&lt;/P&gt;
&lt;H3&gt;Resolution&lt;/H3&gt;
&lt;P&gt;There is no configuration to allow Alero users and internal users to use the same account. This would imply that the account needs to reside in multiple safes, which is something we strongly discourage because of password synchronization issues that would result.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;What you can do is&lt;/P&gt;&lt;P&gt;1. Determine which accounts the Alero vendor should have access to&lt;/P&gt;&lt;P&gt;2. Create a separate safe strictly for Alero users, with the Alero users having only Use and List&lt;/P&gt;&lt;P&gt;3. In the same safe, the internal users should have whatever permissions they need. This could be just use, retrieve and list&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;What you want to avoid is giving Alero users permissions on 'internal' safes - that is, safes that have accounts that the vendor should not access. Obviously, you don't want to give your vendors excessive rights. The separate Alero safe with only those accounts that the vendor can access (Use, List) will provide the necessary permissions and to which you can add internal users with more permissions if necessary.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Nov 2025 05:01:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-articles/alero-is-there-a-configuration-setting-that-allows-internal-and/ta-p/1429948</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-11-05T05:01:21Z</dc:date>
    </item>
  </channel>
</rss>

