Skip to content

Commit b175a78

Browse files
committed
update
Signed-off-by: ZihanKuang <zihan_kuang@outlook.com>
1 parent 6f179c1 commit b175a78

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

  • content/en/cloud/identity/users/user-invitations

content/en/cloud/identity/users/user-invitations/index.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ categories: [Identity]
77
tags: [users]
88
---
99

10-
The new invitation system gives you precise control over how members join your community, allowing you to streamline onboarding and enhance security.
10+
The new invitation system gives you precise control over how members join your organization, allowing you to streamline onboarding and enhance security.
1111

1212
You can create highly customized invitations for any scenario, from onboarding specific individuals to launching large-scale community challenges. Each invitation can be configured with expiration dates, usage quotas, and pre-assigned roles, ensuring new members get the right access from the moment they join.
1313

@@ -19,14 +19,14 @@ The invitation system provides three main areas of control to help you manage ac
1919
Tailor each invitation to your specific needs with three flexible modes:
2020
- Precise invitation: Target a single user by specifying their full email address.
2121
- Domain-wide invitation: Onboard an entire organization at once by allowing any email from a specific domain (e.g., `*@layer5.io`).
22-
- Public invitation: Leave the email field blank to create an open link for public events (e.g., Academy Challenge invites).
22+
- Public invitation: Leave the email field blank to create an open link for public events (e.g., Academy Challenge invitations).
2323

2424
{{< alert type="warning" title="Use domain wildcards carefully" >}}
25-
Patterns like `*@company.com` allow anyone with that domain. Verify ownership and pair with roles/teams that grant only necessary access.
25+
Patterns like `*@company.com` allow anyone with that domain. Verify ownership and pair with roles and teams that grant only necessary access.
2626
{{< /alert >}}
2727

2828
#### Control the invitation lifecycle
29-
Manage access with security settings that put you in control:
29+
Manage access with settings that put you in control:
3030
- Expiration date: Set a specific date and time for an invitation to automatically become invalid.
3131
- Usage quota: Limit the number of times an invitation can be used.
3232

@@ -59,7 +59,7 @@ The invitation system offers flexible configurations to fit a variety of use cas
5959

6060
#### Scenario 1: Inviting a single team member
6161

62-
- Goal: Provide a new employee with a secure, single-use invitation that grants correct initial permissions.
62+
- Goal: Provide a new employee with a secure, single-use invitation that grants the correct initial permissions.
6363
- Configuration:
6464
- Email: Set to the new member's specific email.
6565
- Roles: Assign their specific role (e.g., `Developer`).
@@ -75,7 +75,7 @@ The invitation system offers flexible configurations to fit a variety of use cas
7575

7676
#### Scenario 3: Launching a community challenge
7777

78-
- Goal: Create a public sign-up link for a limited-time community event with a maximum number of participants.
78+
- Goal: Create a public signup link for a limited-time community event with a maximum number of participants.
7979
- Configuration:
8080
- Email: Leave blank for public access.
8181
- Name: Give it a clear name like "Layer5 Challenge 2025".

0 commit comments

Comments
 (0)