<?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: Which role permissions allow access to user.provisions property? in ArcGIS API for Python Questions</title>
    <link>https://community.esri.com/t5/arcgis-api-for-python-questions/which-role-permissions-allow-access-to-user/m-p/1709334#M11972</link>
    <description>&lt;P&gt;For anyone else doing the same kind of work, it seems the user.provisions property doesn't report on any assigned ArcGIS Pro extensions. ArcGIS Pro itself will appear in the provisions if the user was given a license separately from their user type, but if they were also given Spatial Analyst (for example), it will not appear here. It appears you can only get those through the gis.admin.license class (which requires an admin account to access). So, while I thought the "Manage Licenses" user role privilege was a bit too broad, it actually does both too much and too little. It would be nice if the API could be updated to provide a simpler way to summarize/report on licenses, because currently the info is spread all over the place depending on portal type and license type and seems quite convoluted. But&amp;nbsp;I understand the platform has evolved over time and this is how things go sometimes when you are building on top of an existing system.&lt;/P&gt;&lt;P&gt;If anyone could confirm, clarify, or elaborate, it would still be appreciated.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 23 Jun 2026 15:29:15 GMT</pubDate>
    <dc:creator>AaronKoelker</dc:creator>
    <dc:date>2026-06-23T15:29:15Z</dc:date>
    <item>
      <title>Which role permissions allow access to user.provisions property?</title>
      <link>https://community.esri.com/t5/arcgis-api-for-python-questions/which-role-permissions-allow-access-to-user/m-p/1687159#M11860</link>
      <description>&lt;P&gt;&lt;A href="https://developers.arcgis.com/python/latest/api-reference/arcgis.gis.toc.html#arcgis.gis.User.provisions" target="_blank" rel="noopener"&gt;https://developers.arcgis.com/python/latest/api-reference/arcgis.gis.toc.html#arcgis.gis.User.provisions&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Does anybody know what specific user permissions are needed to access the User.Provisions property (linked above) via the API? When I'm logged in with an admin account, I'm able to pull this property no problem. But we're trying to create a custom role for reporting purposes that can essentially only view all user information, not manage it, so that the script doesn't require a full admin account.&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the options for creating a custom role, the only permission I see related to licenses is under Admin -&amp;gt; Content -&amp;gt; Manage licenses, which is described as "&lt;SPAN&gt;Allow member to assign licenses to members of your portal." Enabling this lets me read the user.provisions property—but I'm wondering if there is another permission that would allow read-only? Separating out the ability to view and manage would be ideal.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Edit 4/3/2026—to add, while the permission mentioned above works for most things (even if it's not ideal because it also allows for assigning/revoking licenses), I do get an error when trying to read add-on license for admin accounts. Specifically in one ArcGIS Online org we have, but haven't seen the issue when running on Enterprise orgs. Have not been able to figure out which specific add-on or extension causes this, or whether it's some sort of license/extension inherent to admin accounts that non-admin accounts are not allowed to view in the API. I suspect it may be an organization extension like ArcGIS Velocity. The specific error is a &lt;EM&gt;403:&amp;nbsp;You do not have permissions to access this resource or perform this operation.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Would really appreciate some clarification or insight here&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Apr 2026 15:18:01 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-api-for-python-questions/which-role-permissions-allow-access-to-user/m-p/1687159#M11860</guid>
      <dc:creator>AaronKoelker</dc:creator>
      <dc:date>2026-04-03T15:18:01Z</dc:date>
    </item>
    <item>
      <title>Re: Which role permissions allow access to user.provisions property?</title>
      <link>https://community.esri.com/t5/arcgis-api-for-python-questions/which-role-permissions-allow-access-to-user/m-p/1709334#M11972</link>
      <description>&lt;P&gt;For anyone else doing the same kind of work, it seems the user.provisions property doesn't report on any assigned ArcGIS Pro extensions. ArcGIS Pro itself will appear in the provisions if the user was given a license separately from their user type, but if they were also given Spatial Analyst (for example), it will not appear here. It appears you can only get those through the gis.admin.license class (which requires an admin account to access). So, while I thought the "Manage Licenses" user role privilege was a bit too broad, it actually does both too much and too little. It would be nice if the API could be updated to provide a simpler way to summarize/report on licenses, because currently the info is spread all over the place depending on portal type and license type and seems quite convoluted. But&amp;nbsp;I understand the platform has evolved over time and this is how things go sometimes when you are building on top of an existing system.&lt;/P&gt;&lt;P&gt;If anyone could confirm, clarify, or elaborate, it would still be appreciated.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2026 15:29:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-api-for-python-questions/which-role-permissions-allow-access-to-user/m-p/1709334#M11972</guid>
      <dc:creator>AaronKoelker</dc:creator>
      <dc:date>2026-06-23T15:29:15Z</dc:date>
    </item>
  </channel>
</rss>

