Skip to content

Commit 7b6e802

Browse files
author
gitName
committed
review
1 parent ad212ca commit 7b6e802

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

articles/api-management/api-management-howto-create-groups.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ API Management has the following immutable groups:
2323
> [!NOTE]
2424
> At any time, a service owner can update the administrator [email settings](api-management-howto-configure-notifications.md#configure-email-settings) that are used in notifications from your API Management instance.
2525
26-
* **Developers** - Authenticated developer portal users fall into this group. Developers are the customers that build applications using your APIs. Developers are granted access to the developer portal and build applications that call the operations of an API.
26+
* **Developers** - Authenticated developer portal [users](api-management-howto-create-or-invite-developers.md) fall into this group. Developers are the customers that build applications using your APIs. Developers are granted access to the developer portal and build applications that call the operations of an API.
2727
* **Guests** - Unauthenticated developer portal users, such as prospective customers visiting the developer portal of an API Management instance fall into this group. They can be granted certain read-only access, such as the ability to view APIs but not call them.
2828

2929
In addition to these system groups, administrators can create custom groups or [use external groups in associated Microsoft Entra tenants][leverage external groups in associated Azure Active Directory tenants]. Custom and external groups can be used alongside system groups in giving developers visibility and access to API products. For example, you could create one custom group for developers affiliated with a specific partner organization and allow them access to the APIs from a product containing relevant APIs only. A user can be a member of more than one group.

articles/api-management/api-management-howto-create-or-invite-developers.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ To invite a developer, follow the steps in this section:
4545

4646
When a developer is invited, by default an email is sent to the developer. This email is generated using a template and is customizable. For more information, see [Configure email templates][Configure email templates].
4747

48-
The developer can accept the invitation by following the instructions in the email. Once the invitation is accepted, the account becomes active.
48+
The developer can accept the invitation by following the instructions in the email. Once the invitation is accepted, the account becomes **Active**.
4949

5050
The invitation link is active for 2 days.
5151

@@ -61,7 +61,7 @@ To block a user, follow the following steps.
6161

6262
## Reset a user password
6363

64-
When you create a developer account or a developer is invited, a password is set. You can send an email to a user to reset the password:.
64+
When you create a developer account or a developer is invited, a password is set. You can send an email to a user to reset the password:
6565

6666
1. In the left menu, under **Developer portal**, select **Users**.
6767
1. Select the user whose password you want to reset.

0 commit comments

Comments
 (0)