BLOCKS: Login Block
What is the Login Block?
The Login Block puts a real sign-in on a page you build, so somebody can sign in where they already are instead of being sent to your separate login page first. It is the same sign-in your Portal already offers: the same methods, the same messages, the same lockout and the same limits.
It offers exactly the ways to sign in you have switched on, and it greets somebody who is already signed in rather than asking again. Placed and published with nothing changed, it is a working sign-in.
Where can I place it?
In the block picker it is listed as Login Block, described as "Let visitors sign in from this page". It is offered on five surfaces:
Public Landing Pages, public profile pages, Stacks (both header and footer bars), course landing pages and Proposals.
IMPORTANT: It is deliberately not offered where a sign-in would make no sense or would be unsafe: Documents, marketing campaign emails, error pages, pages inside the Portal, Dashboards, course lessons, Sales Funnels and the Sales Room. A sign-in form inside a marketing email in particular is refused, because it cannot be told apart from a phishing attempt.
How do I add it?
- Edit one of the pages above and add the Login Block from the block picker.
- Choose how it appears under Display: Inline on the Page, which shows the sign-in in the page, or A Button That Opens a Login Panel, which shows a button that opens the same sign-in over the page.
- Adjust the wording if you want to, and save.
The options
Ways to Sign In is a read-only list, there for reference. It shows Email and Password always, plus Continue with Google, Continue with Microsoft and the emailed sign-in link when you have switched those on. Change them under Login Options on the Manage Custom Domain & Login Page screen and every block you have placed follows, with no page to reopen.
Title and Subtitle head the first step. An empty Title shows "Log In".
Button Label sets the wording on the button when you chose the button display. Empty shows "Log In", translated for each visitor.
Greeting When Already Signed In is shown to somebody already signed in, followed by their first name. Empty shows "Welcome back, ".
Button for a Signed-In Visitor is the one button that person sees. Empty shows "Go to My Portal".
After Signing In, Go To sends people somewhere specific after they sign in. Leave it empty to send them wherever they would normally land.
IMPORTANT: That destination has to be a page inside your Portal. An address on another website, or one of the sign-in pages, is refused on save with "Use a page inside your portal, such as /dashboard. Links to other sites or to the sign-in pages cannot be used here." If the page you choose is one a particular person's role cannot open, they land where they normally would instead.
How do I put a Log In button in my header?
A header carries its own Log In, and it is a separate control rather than the Login Block placed in a header. Open the header block's options, go to its Log In tab, and switch on Show a Log In Button. Every public page under that header then carries the button.
The tab carries its own Button Label and Greeting When Already Signed In, and its own After Signing In, Go To with three choices: This Page, which is the default and leaves the visitor exactly where they were reading, Usual Landing Page, or a Portal Page you name.
TIP: Leaving the header on This Page is what makes it feel seamless. Somebody reading your pricing page presses Log In, signs in in the panel over the page, and is still on the pricing page, now signed in.
What does a visitor experience?
Everything finishes where they are.
The sign-in itself. With the inline display they type their email and password and press Log In, and the page does not change around them. With the button, the sign-in opens over the page: a compact panel on a wide screen, a sheet up from the bottom on a phone. Closing it leaves nothing typed behind.
Extra steps stay in place. If the account uses two-step sign-in, the same panel asks for the code. If the email and password open accounts in more than one business, the panel asks which one. "Having Trouble?" and the emailed sign-in link are asked for in the same panel.
Google and Microsoft bring the visitor back to the page they started on, now signed in, rather than to the login page.
Already signed in. Instead of a form they are greeted: inline, their initials, your greeting with their first name and one button through to their Portal; in a header, a small chip with their initials and your greeting, shown as initials alone on a phone.
Why do emailed links now wait for a press?
Every link the platform emails to let somebody in, or to confirm something for them, now opens a page with one button, and only a person's press does anything. That covers invitations, emailed sign-in links, password resets, undoing an email address change, confirming a new address, an autoresponder unsubscribe and a file delivery's download. The button reads Continue, Confirm or Unsubscribe depending on what it is for.
This matters because mail security scanners, link previews and crawlers open the links in a message to check them. Before, that first open could sign the person in, use the link up, or trip a lockout, so the real recipient found a dead link. Now opening the page does none of those things: no sign-in, nothing used up, no lockout cleared, nothing confirmed. The page never submits itself.
A new Client accepting an invitation opens the link, presses Continue, and goes on to set their password exactly as before. No email carries a code to type.
CLICK HERE to learn about customizing your Login Page.