Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties

Status

Status
colourRed
titlenot visible to public
Status
titleDraft

Type

Explanation

Reader

Clients

Reader goal

Contributors

JUNO version

V2.3

Reviewers (check the box when you’re done!)

  •  

Review deadline

Notes for reviewers

Before users log in

Control what users see before logging in by making your site private or public preview.

...

Info

For a multi-site platform, private and public preview sites can be combined in creative ways. Learn more about multi-site access combinations.

Private site

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.

You can control which content is previewable! Learn more about what preview looks like and see all configuration options.

[VIDEO]

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 users can be treated differently depending on their access level.

You can control who has access to specific pieces of content or site navigation pages. For example, within an event site, you might create multiple ticket levels or restrict admin-only content.

Access levels on content

Individual pieces of content are controlled by access level tags.

...

Info

Access-level-restricted content looks a little different when it’s also previewable. Learn more about using public preview and access levels together.

[VIDEO]

An example of content with access level restrictions.

Curtains on pages

Curtains hide navigation pages from users who don’t have the correct access level tag or user level (like site admin).

...

Or use them 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 multi site? Check with jami or scrilla