So the idea is that I want to restrict certain features from an author that a publisher would have access to. That feature is the action buttons in the super header field. On the data model, there are 3 action buttons. Submit, decline and publish. The author is only allowed to see the submit button only, but at the moment they can see all the options. Is there a way to modify that accordingly to a condition (i.e. hierarchical roles)?
1 Like
Yeah, you could totally do that!
I’d just fork the existing Super Header interface, and since you’re on the app side, you can use the permissions store to check access control and adjust actions accordingly.
Make sure you check out the guides on extensions in the docs:
Here’s some sample code for working with the permissions store:
This should give you everything you need to customize the interface based on user permissions! 