Pages Permissions Management

App Building
1

  • Goal: want to manage the access per page in our new multipage application

  • Steps:
    1- have create a multipage application with global nav and header
    2- already we have permission groups to manage access across our applications, so now we want it on scope of pages as well
    3- currently we aren't able to configure the permissions of pages meaning that if user tries to access page using its url to be directed for example to 403 page if he/she doesn't have the access
    4- but we found here that permissions are allowed to the whole multipage app

  • Details:
    we are self hosted on version 3.75.3

  • Screenshots: image
    here in the attached image we are blocked to customize access in the multipage app

1 Like
2

Hey @davidwageh! Page permissions is not supported but on our upcoming roadmap. I'll let you know when we start working on it

1 Like
3

+1 for page permissions feature

4

While page permissions is on the way, what the best practice would you suggest as a warkaround?

We're facing the issue: now we have different apps for different roles — so there's a lot of "repeated" code (for the resources and for the interface)

In regular "hand-written" app you can check permissions/roles on the front - and show only required info (eg you can hide some columns in the table for less privileged role). And then do the same checks on the back to ensure there's no access to restricted data.

Is there a best practice how to do that with Retool now?

5

Hmm that's an interesting question, @AppsTrain. Generally speaking, the best practice for reducing duplicate code is utilizing modules and the query library.

One relatively crude solution for restricting access to a given page is to define a JS query that reads the value of current_user.groups on page load and redirects back to a generic landing page if they aren't a member of the correct group.