How members sign in to your site

People who buy, enroll, book or join on your site have an account on that site only — they never see VPress. They sign in at /account/sign-in, with a 6-digit code we email them or with one of the Continue with … buttons under it. You choose those buttons under Users → Sign-in.

The providers

Each provider is a separate part of your plan, such as Sign in with Google. One your plan doesn't include is shown on the Sign-in tab as Not in your plan; see Plans and billing.

Choosing the buttons

1. 1Open Users → Sign-in.
2. 2Turn a provider's switch on or off and press Save on its card.
3. 3Use the arrows on the cards to put the buttons in the order you want them on your sign-in page.

Each card's badge says whether its button is On your site now. Not showing means it's switched on but can't appear yet — your own app isn't finished, say, or VPress hasn't set up that provider yet. Switching a provider off takes effect at once, even for someone halfway through signing in with it.

When members are asked for a code

A member's email address is the key to their account on your site, so a provider is only linked to an account once the address is proven to be theirs. Google, Apple, Yahoo, GitHub and gitlab.com vouch for the address themselves. Facebook doesn't, and neither do some Microsoft work accounts or an organization's own GitLab: the first time someone signs in that way, we email them a code to type in, just as when they sign in by email. After that, the button signs them straight in.

VPress's app or your own

Out of the box, the buttons sign in through VPress's own apps: there's nothing to set up, but the provider's consent screen names VPress. If your plan includes Own sign-in apps, choose Your own app on a card and the consent screen shows your site's name and logo instead.

1. 1On the provider's card, choose Your own app.
2. 2Copy the Redirect address — it's on your site's primary domain — and follow How to set up your app on the card to create the app at that provider.
3. 3Paste the app's client ID and secret and press Save. For Apple that's the Services ID, Team ID, Key ID and the .p8 key file.
4. 4Press Test sign-in. You sign in at the provider with the saved settings and come back to the Sign-in tab with what it said. Nobody is signed in to your site.
5. 5Once the test works, switch the provider on and save.

• Secrets are stored encrypted and never shown again: the card only says one is saved. Type a new one to replace it.
• Microsoft client secrets expire. Enter the date under Secret expires and the card warns you a month ahead.
• For a Microsoft app that's only for your organization, enter its directory under Directory. For your own GitLab, enter its hostname under GitLab server.
• If the provider shows an error about the redirect URI during the test, the redirect address isn't registered on your app exactly as shown.

Moving a provider between VPress's app and your own keeps your members' accounts. Facebook members confirm their email with a code once more, because Facebook gives each app its own id for a person.

Who can change this

Anyone whose role can see Users can see the Sign-in tab. Changing it, and running a test, takes permission to manage Users; see Team roles and permissions. The Google photos switch is on this tab too: whether a member's Google picture becomes their photo when they have none.