When an experience asks a reader to log in or sign up, such as the Log in button on an access wall, UniSignIn sends them to the login you choose. The choice applies to your whole account: every experience, and logins started from the account menu, checkout or a subscription offer.
| Choice | Where readers log in | Best for |
|---|---|---|
| Popup on the page (default) | In a popup over the page they are reading | One website, where readers shouldn't leave the page |
| Shared login page | On your UniSignIn login page, then back to the page they were on | Several websites sharing one login, and longer logins |
| Your own login page | On your website's login page, then back to the page they were on | Sites where readers already have accounts with you |
Readers log in without leaving the article. Each of your websites keeps its own login, so a reader who uses two of your sites logs in on each. Some browsers, such as Safari, limit logins inside popups and ask readers to log in again more often.
Readers go to your UniSignIn login page, for example account.example.com, log in, and come back to the page they were on, logged in.
account.example.com.Readers go to your website's login page and come back to the page they were on, logged in. Your site signs them in to UniSignIn as well, see Connect your own login system. Use a page that requires login and has the UniSignIn tag.
Features > Account Center > Authentication.Only the account owner and Super Administrators can change this setting, see Team and Roles.
Readers are only sent back to your project's website and the domains in Features > Account Center > Other Settings > Domains allowlist. Add every site that should share the login.
Logging out on one site logs the reader out of that site only.
Identity, consent, audience, and subscription insights for publishers. A few emails a month, no spam.