To define a new rule, you simply select a role from the dropdown (that
is built against the database to include all rules on the current
portal) and specify a URL to redirect to. Not that you can input
anything you like in the URL, so it can be a relative or absolute URL,
it can be on any protocol and port, etc.
Furthermore, if you have My Tokens installed, you can
include tokens in URL, so you truly turn the redirects into dynamic
redirects. 
Note that there is no separate edit control for role redirects. Just by
adding a new redirect will overwrite any rule that exists for that role.
Also, make sure your redirects will not cause an infinite loop. If you accidentally run into this scenario, then you'll need to manually delete entries in avtRedirect tables in the database. Manage Role RedirectsThis is made from the section represented below:
In this section redirects can be removed and priorities set. DNN Redirect will parse rules in the order given by their priority. So, for users with multiple role, you have full control to define which one is relevant (or matters most) in terms of redirection. Note that priorities can be both positive and negative. The redirect that has the highest priority number is parsed first. Go to DotNetNuke DNN Redirect Homepage |
Product Documentation |
Avatar Software Product Documentation > DNN Redirect- DotNetNuke Redirects Module > Settings Explained >
Role Redirects |