When I send an invite to a user to allow them to view a page, they are forced to first create an account. Once they do that, they are taken to the Apps page which gives them access to all the apps I've created and the ability to change those apps. Is that how it is suppose to work?
I have tried sending out a public link and when I do that, the links in my navigation component do not work for them. I have opened the page in a private browser window, and they do not work there either.
I would like for other users to be able to have access without having access to edit an app.
Hey @tomm - thanks for reaching out. Permission control in Retool can be a nuanced topic, so I certainly understand the desire for clarification.
The most important thing to understand is that - by default - all users have the ability to edit apps. The only way to restrict this is to configure role-based access controls within your org settings. Note that this feature is is only available on Business and Enterprise plans.
If you don't want a given user to have edit access, you simply need to add them to the Viewer group. It may also be necessary to reduce the permissions associated with the All Users group, depending on how that is currently configured.
The other option that you mentioned above is generating a public link to your app. This makes your app viewable by anybody on the internet - without requiring them to have a Retool account - but does come with certain limitations. Specifically, public apps are not allowed to make requests to authenticated resources. This may be why your navigation component isn't working.
I'd be interested in hearing more about your particular use case in order to provide better advice.
