All Users group not having access to custom resource (REST API)

[kiwigas]

Current plan level (Free, Team, Business, or Enterprise: https://retool.com/pricing): Free
Monthly/Annual (if Team or Business):
Version of Retool (if self-hosted):

Question / Description:
I have created a resource that is of type REST API which is pointing to another website & application. However users that are only members of ‘All Users” permission group… are unable to execute the REST API, a permission error is thrown.
Yes, I am aware that as a ‘Free’ account I am not able to adjust the permission setting on that resource. However, when looking at plan comparisons there is a tick in “Connect to all databases and APIs” under the Resources section. Retool | Pricing
Like wise in the design mode, when the resource is added to the page there is a option under ‘Advanced’ to set the ‘Access controls’ on the REST API resource, this has zero effect as well.

This leads me to believe that the ‘All Users’ group not having use permission on any custom resources that do not ship out of the box from retool is the issue and will override anything else I try, not having a paid plan prevent me from changing the permission.

Is this correct?
Is this expected behaviour?
Where does the documentation make mention that customer resource are not inscope or auto assigned to the ‘All User’ permission group?

Thanks,

L-J

[ChiEn]

Hello @kiwigas L-J, I saw that you were directed here by our Customer Service Representatives, welcome to the Community!!

Hmm you and all your users should be able to add, edit, and remove resources according to this doc.

How is it going on your end now? Have you noticed any changes?

Also just to double check, did you by any chance downgrade from another plan recently?

[kiwigas]

Hi,
no this is a new Retool instance / account, I then migrated the application from another retool instance/account into this current one. Both are on ‘free’ plan. My mistake when testing is everybody that tested was part of the ‘admin’ group. .

This morning I recreated the REST API resource from scratch and tested it. However I suspect it will behave the same as the previous one due to the fact that the system does not set the permission on the resource automatically for the ‘all users’ group.

I have included some screen shots below to show setups & behaviour…

Using the ‘resource’ in a execution as a user in the ‘admin’ group the new api executes with no permission issues.