| Page Properties | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
There are multiple ways to control user access to your site and content.
Before users log in
Control what users see before logging in by making your site private or public preview.
...
Keep your site privateso that users only see the welcome page before logging in. See welcome page configuration options.
...
An example private site before logging in.
Public preview site
Make a public preview siteto show potential users what they could get once they join. They can navigate around the site and preview content. But once they try to interact with content, they are prompted to log in.
...
| Widget Connector | ||||||
|---|---|---|---|---|---|---|
|
An example public preview site. You can preview content but must log in once you try to interact.
After users log in
After users log in, the system knows who they are. Now they can be treated differently depending on their access level.
...
| Widget Connector | ||||||
|---|---|---|---|---|---|---|
|
An example of content with locked by an access level restrictionstag.
Curtains on pages
Curtains hide navigation pages from users who don’t have the correct access level tag or user level (like site admin). The link is completely hidden from the navigation menu.
...
Or use curtains to create different experiences for different users on the same page. We do this by creating two versions of the same page. Then with access level tags or user levels (like site admin), users are assigned to only see one of the pages.
Note that it doesn't work with note that can’t be used on multi site? Check with jami or scrilla