Hi Katheeja, Well, a simple, customizable way would be put the user's role into the token, and redirect based on that. Don't do that inside the router. Instead, make it part of your authentication flow. You use route-guards in your router to prevent users from accessing a route they have no permission to.
Regards Sander -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
