Sign-in page
When a partner application signs a member in through Allegro, the member lands on your organization's hosted sign-in page. That page is served from your Allegro domain, so unlike an embedded component there is no surrounding site whose markup your developers control.
Organization Settings › Sign-in page is where you add your own copy to it — most commonly the Terms of Service and Privacy Policy links a sign-up flow needs to display.
Header and footer
| Field | Where it appears |
|---|---|
| Header | Above the sign-in form only. |
| Footer | Below the sign-in form, and below the "Continue as …" prompt shown to a member who is already signed in. |
Neither appears while the page is loading, and neither appears on the sign-in error page.
What HTML is allowed
The fields accept HTML, but only a deliberately small subset survives:
| Allowed | Purpose |
|---|---|
<a href="…"> | Links |
<strong> | Bold text |
<em> | Italic text |
Everything else is removed when you save:
- Any other tag is stripped, but the words inside it are kept —
<p>Read the terms</p>saves asRead the terms. Structure collapses to one run of text, so a pasted list saves as its items separated by spaces rather than as bullets. Copy that needs to read as separate lines belongs on your own site, behind a link. <script>and<style>are removed along with their contents.- All attributes are removed, including
class,style, and anyon…event handler. - Link destinations must be
https:ormailto:. A link to anything else — includinghttp:, a relative path, orjavascript:— loses its link and becomes plain text.
Because saving rewrites your input to the cleaned version, the editor always shows exactly what the page will render. If something disappears after you save, it was not in the list above.
This is the one page in Allegro that completes an authorization and briefly handles the member's signed-in session. Markup that could run script there could capture a member's session, so the page accepts only what a legal footer genuinely needs.
Links always open in a new tab
Every link is given target="_blank" automatically. The authorization request
lives in the tab the member started in, so a member who navigated away to read
your terms would otherwise have to begin signing in again.
Example
By continuing you agree to our
<a href="https://example.org/terms">Terms of Service</a>
and <a href="https://example.org/privacy">Privacy Policy</a>.
Styling it
This page controls the words. Their appearance — text color, font, size, and link color — is set in the OAuth page scope of the Branding editor, under the Header text and Footer text groups. The branding preview renders your saved copy, so you can switch to the OAuth page scope there to see the result in place.