This guide walks you through the decisions you’ll make as you plan a multi-site JUNO platform.
...
| Widget Connector | ||||||
|---|---|---|---|---|---|---|
|
An example public site. You can preview pages but must log in once you try to open content.
Private access: Or keep your site privateso that users only see the welcome page before logging in.
...
An example private site. You only see the welcome page before logging in.
Content-specific restrictions: In addition to the above site-wide access options, you can restrict individual pieces of content with an access level tag. It doesn’t matter if the site is public or private. Even if someone is logged in, they can only open the content if they have the correct access level. For example, within an event site, you might create multiple ticket levels. If a user has access to a site, but not that content, they are alerted and can be prompted to upgrade.
...
User authentication
| Anchor | ||||
|---|---|---|---|---|
|
| Excerpt | ||
|---|---|---|
| ||
To ensure a smooth JUNO experience, we strongly recommend choosing one way to authenticate users for the entire platform. Fewer interacting systems mean fewer unexpected complications! We understand that many organizations already have multiple authentication methods in place. For example, maybe your existing association members use SSO, while prospective members are invited to an event via registration. In this case, we recommend consolidating your registration into your SSO, if possible. Then, we will only need to integrate one database with JUNO. |
Site content and configuration
| Anchor | ||||
|---|---|---|---|---|
|
...