Permissions settings
How are Roles added to Sitefinity?
The SSO Authentication process creates the new ‘role’ in Sitefinity when a user of that role/group first logs in. Once the role exists in Sitefinity, LeadingAge PA staff can set permissions restricted to that role.
Results Direct recommends having a test account for each role, and log in with that role, so LeadingAge PA can restrict content for that role.
Restrict a Page, or Content Block?
You can restrict entire Pages, or you can restrict by Content Blocks.
* If you restrict an entire page, the non-logged in users will not see the page at all unless they are logged in. They will not see it in the navigation.
* We recommend a better user experience is to restrict content by content blocks. The page title shows in the navigation and you can include messages for the non-logged in user that is a teaser of the member benefit content, and has the note to login.
The Three content blocks below show an example of how to structure the content. The reminder note to in the side column explains the settings for each of the three blocks. (You can also edit this page in the Sitefinity admin area and see the permissions for each block.)
Welcome
Add a teaser of what this content is. Note that it is a member benefit.
Please log in to view this content.
Reminder
If you are viewing this page as a Sitefinity Admin, you see all three permission content blocks.
An anonymous user sees the welcome block "Log in to view this content." The content block More > Permissions, has View set to Role = Anonymous.
A logged in, non-member sees "You need to be a Member to view this content." The content block More > Permissions, has View set to Role = Authenticated, and deny Member.
A logged in member sees "This is the protected content." The content block More > Permissions, has View set to Role = Member.