Skip to content

docs: document Account Center identifier query parameter #1381

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wangsijie wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs: document Account Center identifier query parameter #1381

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion docs/end-user-flows/account-settings/by-account-center-ui.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ Configure the field permissions according to your needs:

To use the prebuilt Account Center UI, you need to redirect users from your application to the appropriate Logto pages. There are two approaches:

#### Approach A: Direct linking with redirect parameter \{#approach-a-direct-linking}
#### Approach A: Direct linking with query parameters \{#approach-a-direct-linking}

Add links in your application that redirect users to the prebuilt pages. Include a `redirect` query parameter to bring users back to your app after they complete the action:

Expand All @@ -68,6 +68,14 @@ https://[tenant-id].logto.app/account/email?redirect=https://your-app.com/settin

When users complete updating their email, they will be redirected back to `https://your-app.com/settings`.

For identifier-based pages (`/account/email`, `/account/phone`, and `/account/username`), you can also include an optional `identifier` query parameter to pre-fill the input field:

```
https://[tenant-id].logto.app/account/email?redirect=https://your-app.com/settings&identifier=user%40example.com
```

This is useful when your application already knows the new email address, phone number, or username that the user is about to verify or update.

#### Approach B: Embedding in your account settings flow \{#approach-b-embedding}

You can integrate the prebuilt pages into your existing account settings workflow:
Expand Down
Loading