Granular Permission System

Thank you @Abdel for sharing your case.
Previously, we designed our Permission System on the working role basis because we believed that most of the companies will follow it:

  • Admin: The most powerful role who controls the whole analytics stack and account
  • Analyst (or data builders): Those who supports Admins in building the data stack; therefore, they are able to access to most of the things except for the admin management/settings
  • Explorer: A hybrid of data builders and data consumers - We introduce this role to serve a group of semi-tech users who can understand and explore data themselves, which can help release the data bottleneck. Therefore, they can explore the underlying data and save results with minimum help from data team.
  • Viewer (or data consumers): Those who is just able to view reports

However, recently we realized that there are more and more complex permission cases that our customers have to deal with, and we totally agree that our team should enhance our permission system to better solve these cases.


And yah you’re right, we believe that custom role would better solve your case: You can add or remove permission rules to a specific default role, and/or create new roles for your team.
However, since Permission System is a complicated beast, we are still waiting for more permission use cases (from other customers) before making decisions on the final approach. So we really appreciate your patience and understanding this time.

Feel free to share with us more about your new use cases on this topic, it will be really helpful for us! Thank you!