Why is the "Update Communities" permission required to view API Browser?
I learned today from a support case I opened that granting developers the "API Browser" and the "View Studio in read-only mode" permissions did not actually enable them to view the API Browser. I had to grant the "Update Communities" permission as well, and then they could access it.
This seems strange and unintuitive to me, since Update Communities is really intended as an admin permission (per the tooltip) and API Browser is needed for developers (who may not need to be admins).
I would prefer (and I think it makes more sense, unless I'm missing something) that the permissions be more granular so that Granting API Browser would actually do so.
Thanks to DereckC for troubleshooting this and finding the solution (for now) to get my developers access to the API Browser.
Hi Eric,
Thank you for reporting this. I tested it out myself, and sure enough, there is a bug here.
There is a permission for using the API browser called "Use the API Browser":
Granting that permission should be the only thing you need to do to enable them to use the api browser tab.
I filed a bug to fix this and have fixed it so that all you should need to do is add them to a role that has the "User the API browser" permission. This fix should go into our version 17.8 release.
Thanks,
-Doug