E
egarcia
Guest
Hello Louis, I received feedback from the developers of this functionality. They provided the following information: We don't support that officially yet, however, level access to modules/views and even grid columns is high on our backlog and we will look into it very soon. Currently there is an unofficial way to replace the navigation panel through the extensibility mechanism of our AngularJS apps. You can define your own custom AngularJS module to achieve that in app/src/scripts/extensions/index.js The code would look like the following: var myModule = angular.module('myCustomModule', []); myModule.run(['$state', function($state) { var state = $state.get('module.default'); if (state && state.views && state.views['side-navigation']) { state.views['side-navigation'].template = ' Customized Menu '; } }]); export default angular.module('app.extensions.module', [ 'myCustomModule' ]).name; You can take a look at app/src/scripts/common/side-navigation/index.html to see the actual text of the side-navigation so that you keep the appropriate style. Have in mind that this will only replace the navigation panel. You can define different templates and use the right one depending on the user access. If you know the url you will be able to navigate to that view. We are still considering the approach – whether we will need to remove the views from routing (which will have implications on what happens when you login/logout) or we will do the check on view loading showing you “you don’t have access for this view”. And of course how we will get the user access level is still unknown. Could you please give us more details on your business case? We are interested in how you determine the user access level and how you would like to restrict based on that level. Thank you and regards.
Continue reading...
Continue reading...