Skip to content

Deactivated premium features on user level

Bram Wiepjes requested to merge 597-deactivated-premium-features-on-user-level into 597-licensing-final

Related to #597 (closed)

This is an early proof of concept that allows us to activate or deactivate the premium features on user level. The idea is that we have a single function that can be called to check if a user has an active license to the premium version. This now always returns False, but can be replaced with something that checks if there is an active license for the related user.

The features are visible in the web-frontend, but if the user doesn't have access, they are grayed out and show a message that it is only available in the premium version. This has been created in a decoupled way, so everything would still work if the premium Django app and Nuxt module are not loaded. But if they are loaded, it depends on if the check function to see if it has an active license.

image

image

image

Merge Request Checklist

  • changelog.md has been updated if required
  • Documentation has been updated
  • Quality Standards are met
  • The UI/UX has been updated following UI Style Guide
  • The redoc API pages have been updated for any REST API changes
  • The per database user API docs page has been updated for any REST API changes made to endpoints which can be accessed via a user created token
  • Has performance been considered and tested when appropriate? Ideally Baserow should be performant when working with hundreds of thousands of rows
  • New/Changed Premium features are separated correctly in the premium folder
  • There are tests for and it has been checked that any changed/new django ORM code is sensible, doesn't perform N queries and that table models are not generated needlessly or generated with all columns when only a few are needed.
Edited by Bram Wiepjes

Merge request reports