You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
instructions: "Use for documentation related to custom authenticators, login flows, registration flows, application authentication settings, login UI, identity providers in login, MFA configuration and authentication steps."
16
+
- label: "Team/User & identity administration"
17
+
instructions: "Use for documentation related to user management, identity management, profile management, account settings, password management, user roles and permissions."
18
+
- label: "Team/API Access Mgt & Authorization"
19
+
instructions: "Use for documentation related to API authorization, OAuth/OIDC authorization issues, role management, permission management, consent management, scope management, access policies."
20
+
- label: "Team/B2B"
21
+
instructions: "Use for documentation related to sub-organization management, partner authentication, partner identity management, organization hierarchy."
22
+
- label: "Team/Identity Server Core"
23
+
instructions: "Use for documentation related to email provider configuration, SMS provider configuration, deployment configuration, server performance improvements, infrastructure issues, core backend services, tenant management, web application or API performance and maintenance."
Copy file name to clipboardExpand all lines: en/identity-server/next/docs/guides/users/manage-users.md
+43-20Lines changed: 43 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,24 @@ This guide walks you through how you can manage user accounts as an administrato
8
8
9
9
To learn more about onboarding users, see [Onboard users]({{base_path}}/guides/users/onboard-users/).
10
10
11
+
## Filter users
12
+
13
+
Administrators can filter users based on their account status from the {{ product_name }} Console.
14
+
15
+
To filter users by account status:
16
+
17
+
1. On the {{ product_name }} Console, go to **User Management** > **Users**.
18
+
2. Click the **Account Status** dropdown and select the relevant filter criteria:
19
+
20
+
-**Locked**: Filters users with locked accounts.
21
+
-**Disabled**: Filters users with deactivated accounts.
22
+
-**Pending password reset**: Filters users for whom the administrator has initiated a forced password reset, but the users haven't yet reset their passwords.
23
+
-**Pending initial password setup**: Filters users an administrator invited to set their own password during initial account creation but who haven't done so yet.
24
+
-**Pending email verification**: Filters users who haven't yet verified their primary email addresses.
25
+
-**Pending mobile verification**: Filters users who haven't yet verified their primary mobile numbers.
Groups are useful when you wish to assign a certain permission level to multiple users. A user can be a member of multiple groups in the organization. Learn how to [manage groups]({{base_path}}/guides/users/manage-groups/).
@@ -55,6 +73,30 @@ To update the user profile:
55
73
56
74
4. Click **Update** to save.
57
75
76
+
## Share user with organizations
77
+
78
+
An administrator can share a user with an organization (or multiple organizations) via the WSO2 Identity Server Console.
79
+
80
+
To share a user with organizations:
81
+
82
+
1. On the WSO2 Identity Server Console, go to **User Management** > **Users**.
83
+
84
+
2. Find the user's account in the user list and click **Edit**.
85
+
86
+
3. Navigate to the **Shared Access** tab.
87
+
88
+
4. Select the appropriate sharing option.
89
+
90
+
-**Do not share user with any organization** - user will not be shared with any organizations.
91
+
92
+
-**Share user with all organizations** - user is shared with all current and future organizations. When the user is shared, administrators can also configure which roles should be assigned to the user in the shared organizations.
93
+
94
+
{: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"}
95
+
96
+
-**Share user with selected organizations** - user is shared with a specific set of existing organizations, but they are not shared with the future children organizations. Administrators can configure which roles should be assigned to the user in the shared organizations.
97
+
98
+
5. Once selected and configured, click **Save**.
99
+
58
100
## Resend invitation links and codes
59
101
60
102
Administrators can resend expired invitation links or verification codes to users. This applies when users need to:
@@ -142,7 +184,6 @@ Specify the **recovery scenario** in the `properties` parameter of the API reque
142
184
- Provide the username without the user store domain prefix
143
185
- Specify the relevant user store domain name in the `realm` parameter
144
186
145
-
146
187
---
147
188
**Response**
148
189
```
@@ -195,7 +236,7 @@ To reset the password:
195
236
196
237
3. Click **Reset Password**.
197
238
198
-
**Using the API**
239
+
### Using the API
199
240
200
241
You can also use WSO2 Identity Server's [SCIM API]({{base_path}}/apis/scim2-users-rest-apis/#tag/Users-Endpoint/operation/patchUser) to initiate the admin initiated password recovery flow.
201
242
@@ -319,21 +360,3 @@ To delete a user account:
319
360
320
361
3. Select the checkbox to confirm your action.
321
362
4. Click **Confirm**.
322
-
323
-
## Filter users
324
-
325
-
Administrators can filter users based on their account status from the {{ product_name }} Console.
326
-
327
-
To filter users by account status:
328
-
329
-
1. On the {{ product_name }} Console, go to **User Management** > **Users**.
330
-
2. Click the **Account Status** dropdown and select the relevant filter criteria:
331
-
332
-
- **Locked**: Filters users with locked accounts.
333
-
- **Disabled**: Filters users with deactivated accounts.
334
-
- **Pending password reset**: Filters users for whom the administrator has initiated a forced password reset, but the users haven't yet reset their passwords.
335
-
- **Pending initial password setup**: Filters users an administrator invited to set their own password during initial account creation but who haven't done so yet.
336
-
- **Pending email verification**: Filters users who haven't yet verified their primary email addresses.
337
-
- **Pending mobile verification**: Filters users who haven't yet verified their primary mobile numbers.
Copy file name to clipboardExpand all lines: en/includes/guides/organization-management/share-user-profiles.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ There are three ways how user profiles are shared between organizations:
10
10
11
11
2. An organization admin can invite users from the immediate parent organization to join the organization. Once the user accepts the invitation, the user profile is automatically shared with the child organization. Learn more about [inviting existing users from the parent organization]({{base_path}}/guides/organization-management/onboard-users/#invite-existing-users-from-the-parent-organization).
12
12
13
-
3. An admin can share users of an organization with other organizations lower in the hierarchy using the [User Sharing API]({{base_path}}/apis/organization-user-share-rest-api).
13
+
3. An admin can share users of an organization with other organizations lower in the hierarchy {% if product_name == "WSO2 Identity Server" and is_version > "7.2.0" %}[through the {{product_name}} Console]({{base_path}}/guides/users/manage-users/#share-user-with-organizations) or {% endif %} using the [User Sharing API]({{base_path}}/apis/organization-user-share-rest-api).
14
14
15
15
## Customize user attributes in shared user profiles
16
16
@@ -31,7 +31,7 @@ If your organization has a user whose profile is managed by another organization
31
31
<tr>
32
32
<td>From Shared Profile</td>
33
33
<td>The organization can customize the user attribute value.</td>
34
-
</tr>
34
+
</tr>
35
35
<tr>
36
36
<td>From First Found in Hierarchy</td>
37
37
<td>The user attribute inherits the value from the nearest organization in the hierarchy that has assigned a non-null value to it.</td>
@@ -40,5 +40,3 @@ If your organization has a user whose profile is managed by another organization
40
40
</table>
41
41
42
42
Learn more about attribute configurations in [configure attributes]({{base_path}}/guides/users/attributes/manage-attributes/#configure-attributes).
0 commit comments