Skip to main content
Solved

Authorization to variant of table

  • November 1, 2024
  • 1 reply
  • 49 views

Forum|alt.badge.img+5

We process different types of events, questionnaires and more. So we created different variants for that.

To assign the authorization roles, we should be able to assign full rights to a webinar event, but only read access to e.g. masterclasses. Or looking at questionnaires: full access to invitations and no rights to session tests. 

Of course based on the menu we can limit the access to webinars / masterclasses. But giving full access to table evnt (for events, webinars, masterclasses, examinations) for webinars and read to masterclasses, the user has full access to both.

So, can we get the option to grant access for a variant of a table?

Best answer by Jeroen van den Belt

Hi @avandervelden,

avandervelden wrote:

So, can we get the option to grant access for a variant of a table?

We already have some plans to apply permissions-related variant settings in the future.

By determining and storing the effective rights for variants as well, based on the subject's existing role rights, it will eventually be possible to use variant-specific prefilters, column access, and allowed CRUD actions, for example, for authorization purposes. Thus, reducing the need for views even more.

However, these plans still need further development and are not part of the 2025 H1 roadmap. I can assure you that this is on our radar.

View original
Did this topic help you find an answer to your question?
This topic has been closed for replies.

1 reply

Jeroen van den Belt
Administrator
Forum|alt.badge.img+9

Hi @avandervelden,

avandervelden wrote:

So, can we get the option to grant access for a variant of a table?

We already have some plans to apply permissions-related variant settings in the future.

By determining and storing the effective rights for variants as well, based on the subject's existing role rights, it will eventually be possible to use variant-specific prefilters, column access, and allowed CRUD actions, for example, for authorization purposes. Thus, reducing the need for views even more.

However, these plans still need further development and are not part of the 2025 H1 roadmap. I can assure you that this is on our radar.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings