Skip to main content

Account Experience Overview

The Ory Account Experience is the default user interface for all self-service screens like login, registration, or consent. It can be accessed under https://your-slug.projects.oryapis.com/login. New Ory Network projects are automatically configured to use the Account Experience. You can find various customizations and settings in the Ory Console under Account Experience.

Theming

The Account Experience can be themed using the Ory Console. Head over to the theming settings. It is also possible to set a custom logo and favicon.

The Account Experience can show links to your Terms of Service, Privacy Policy, and Contact pages in the footer of all self-service pages. Configure them in BrandingTheming in the Ory Console under Legal and footer links:

  • Terms of Service URL and Privacy Policy URL accept http(s) URLs.
  • Contact URL accepts an http(s) URL or a mailto: link.

Leave a field empty to hide that link. If no URL is set, the Account Experience doesn't render the footer. All links open in a new tab.

The link labels are localized automatically based on the user's language and can be customized per language.

Translations (i18n) & Message Customization

The Ory Account Experience is available in 83 languages.

Full list of supported languages
  • Afrikaans (af)
  • Akan (ak)
  • Amharic (am)
  • Arabic (ar)
  • Assamese (as)
  • Azerbaijani (Latin) (az)
  • Belarusian (be)
  • Bulgarian (bg)
  • Bamanankan (bm)
  • Bangla (bn)
  • Catalan (ca)
  • Czech (cs)
  • Danish (da)
  • German (de)
  • Greek (el)
  • English (en)
  • Spanish (es)
  • Estonian (et)
  • Persian (fa)
  • Finnish (fi)
  • French (fr)
  • Gujarati (gu)
  • Hausa (Latin) (ha)
  • Hebrew (he)
  • Hindi (hi)
  • Croatian (hr)
  • Hungarian (hu)
  • Armenian (hy)
  • Indonesian (id)
  • Igbo (ig)
  • Italian (it)
  • Japanese (ja)
  • Georgian (ka)
  • Kazakh (kk)
  • Khmer (km)
  • Kannada (kn)
  • Korean (ko)
  • Central Kurdish (ku)
  • Kyrgyz (ky)
  • Lithuanian (lt)
  • Latvian (lv)
  • Macedonian (mk)
  • Malayalam (ml)
  • Mongolian (Cyrillic) (mn)
  • Marathi (mr)
  • Malay (ms)
  • Burmese (my)
  • Nepali (ne)
  • Dutch (nl)
  • Norwegian (Bokmal) (no)
  • Odia (or)
  • Punjabi (pa)
  • Polish (pl)
  • Pashto (ps)
  • Portuguese (pt)
  • Romanian (ro)
  • Russian (ru)
  • Sindhi (sd)
  • Sinhala (si)
  • Slovak (sk)
  • Slovenian (sl)
  • Somali (so)
  • Albanian (sq)
  • Serbian (Latin) (sr)
  • Sundanese (su)
  • Swedish (sv)
  • Kiswahili (sw)
  • Tamil (ta)
  • Telugu (te)
  • Tajik (Cyrillic) (tg)
  • Thai (th)
  • Turkmen (tk)
  • Tagalog (tl)
  • Turkish (tr)
  • Uyghur (ug)
  • Ukrainian (uk)
  • Urdu (ur)
  • Uzbek (Latin) (uz)
  • Vietnamese (vi)
  • Xhosa (xh)
  • Yoruba (yo)
  • Chinese (Simplified) (zh)
  • Zulu (zu)

The source is available in the GitHub repository of Ory Elements.

To determine the language to use, the Account Experience uses the Accept-Language header. If the language isn't available, the fallback language (English) is used. Custom translations are supported as well, use the edit button next to the language to override the default translations.

The legal footer links use these translation keys:

KeyDefault (English)
footer.terms_of_service.labelTerms of Service
footer.privacy_policy.labelPrivacy Policy
footer.contact.labelContact

Override them like any other message in BrandingLocalization in the Ory Console to change a label for a specific language. If a language has no override or built-in translation, the English label is used.

A label override can also contain a markdown link, for example [Nutzungsbedingungen](https://example.com/agb). In that case the URL from the label replaces the URL configured on the theming page for that language. Use this to point users to a translated version of the document. Only http(s) and mailto: URLs are allowed in markdown links; other URLs render as plain text. The corresponding URL must still be set on the theming page — an empty field hides the link for all languages.

Custom Domains

The Account Experience is also available under custom domains the same way it works on the slug URL.