Skip to content

Commit dd86a4b

Browse files
Merge pull request #5644 from himeshsiriwardana/bug-fix-10-16
Broken link fixes and improvements
2 parents 1b75e4f + 5069882 commit dd86a4b

File tree

2 files changed

+11
-7
lines changed

2 files changed

+11
-7
lines changed

en/identity-server/next/docs/get-started/about-this-release.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,11 +22,13 @@ With these building blocks, you can create flexible, secure, and user-friendly f
2222

2323
The flow builder supports the following use cases:
2424

25-
- **Self-registration** - Design custom self-registration flows with multiple steps, conditional logic, and data collection. Learn about building a [self-registration flow using the flow builder]({{base_path}}/guides/flows/self-registration/).
25+
- **Self-registration** - Design custom self-registration flows with multiple steps, conditional logic, and data collection.
2626

27-
- **Password recovery** - Create tailored password recovery experiences with identity verification and secure reset options. Learn about building a [password recovery flow using the flow builder]({{base_path}}/guides/flows/password-recovery/).
27+
- **Password recovery** - Create tailored password recovery experiences with identity verification and secure reset options.
2828

29-
- **Invited user registration** - Build invitation-based registration flows that collect necessary information and set up user accounts. Learn about building an [invited user registration flow using the flow builder]({{base_path}}/guides/flows/invited-user-registration/).
29+
- **Invited user registration** - Build invitation-based registration flows that collect necessary information and set up user accounts.
30+
31+
Learn more about [Flows]({{base_path}}/guides/flows/).
3032

3133
### AI agent identity management
3234

@@ -430,7 +432,7 @@ This separation provides a clear distinction between the organization’s identi
430432

431433
### Legacy user registration and management flows
432434

433-
Previously, WSO2 Identity Server offered built-in flows for user registration and management that provided basic functionality and limited customization options. These are
435+
Previously, WSO2 Identity Server offered built-in flows for user registration and management that provided basic functionality and limited customization options.
434436

435437
These flows are now deprecated and replaced with the new **Flow Builder**, which offers a more flexible and powerful way to design and manage user registration and management journeys.
436438

en/includes/guides/users/onboard-users.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ You can use one of the following methods to onboard users to your organization i
44

55
- The user can self-register via the My Account portal or the login page of an application if self-registration is enabled in the organization. Learn how to [configure self-registration]({{base_path}}/guides/account-configurations/user-onboarding/self-registration/).
66

7-
- An administrator can onboard users from a secondary user store by [configuring a secondary user store in {{product_name}}]({{base_path}}/guides/users/user-stores/configure-secondary-user-stores/).
7+
- An administrator can onboard users from a secondary user store by [configuring a secondary user store in {{product_name}}]({{base_path}}/guides/users/user-stores/configure-a-user-store/).
88

99
!!! note
1010
If the secondary user store access type is read-only, you cannot update the user profiles of users onboarded from this read-only user store.
@@ -21,8 +21,10 @@ Let's look at how administrators can onboard users from the {{ product_name }} C
2121
![Add user]({{base_path}}/assets/img/guides/users/add-user-form.png){: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"}
2222

2323
!!! note
24-
- The user's username is always unique to the organization and you can't change the username once it is created.
24+
{% if product_name == "WSO2 Identiy Server" %}-{% endif %} The user's username is always unique to the organization and you can't change the username once it is created.
25+
{% if product_name == "WSO2 Identity Server "%}
2526
- Optionally, you can [configure email address as the username]({{base_path}}/guides/users/attributes/enable-email-as-username/). Then, the user must enter the email address when logging in.
27+
{% endif %}
2628

2729
!!! tip "Add additional fields to the user onboarding form"
2830
The default form requests for basic information of the user. If you wish to include additional details, such as the user's phone number, address, and other custom attributes, you need to make these attributes available in the **Administrator Console**. Learn how to do so in [attribute configurations]({{base_path}}/guides/users/attributes/manage-attributes/#configure-attributes).
@@ -248,7 +250,7 @@ During user onboarding, you can enforce email verification to confirm the provid
248250
"HTTP/1.1 201 Created"
249251
```
250252
251-
5. If you selected the confirmation link option, use can click the link to verify. If you configured OTP, validate it by submitting the OTP using the following API.
253+
5. If you selected the confirmation link option, users can click the link to verify. If you configured OTP, validate it by submitting the OTP using the following API.
252254
253255
!!! abstract ""
254256

0 commit comments

Comments
 (0)