Skip to content

Commit 69f79c3

Browse files
committed
Clarifying edit
1 parent 5f7b00c commit 69f79c3

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

src/content/docs/cloudflare-one/identity/users/seat-management.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Access [service tokens](/cloudflare-one/identity/service-tokens/) do not consume
1313

1414
## Authentication events
1515

16-
For Access, this is any Cloudflare Access authentication event, like a login to the [App Launcher](/cloudflare-one/applications/app-launcher/) or an application. For Gateway, this means any Cloudflare WARP authentication event, like enrolling a device to your ZT organization.
16+
A user consumes a seat when they perform an authentication event. For Access, this is any Cloudflare Access authentication event, like a login to the [App Launcher](/cloudflare-one/applications/app-launcher/) or an application. For Gateway, this means any Cloudflare WARP authentication event, like enrolling a device to your Zero Trust organization.
1717

1818
If either one of these events occurs, that user's identity is added as an Active user to Zero Trust and consumes one seat from your plan. The user will occupy and consume a single seat regardless of the number of applications accessed or login events from their user account. Once the total amount of seats in the subscription has been consumed, additional users who attempt to log in are blocked.
1919

@@ -51,13 +51,13 @@ The user will now show as **Inactive** and will no longer occupy a seat. If a us
5151

5252
To automate the removal of users who have not logged in or triggered a device enrollment in a specific amount of time, turn on [seat expiration](#enable-seat-expiration).
5353

54-
### Delete a user record
55-
56-
There is currently no way to delete or archive a user record. You can [remove a user](#remove-a-user) from a seat, but their user record will remain in your Zero Trust organization.
54+
:::note[User record persistence]
55+
You cannot delete or archive a user record. You can [remove a user](#remove-a-user) from a seat, but their user record will remain in your Zero Trust organization.
56+
:::
5757

5858
### Enable seat expiration
5959

60-
Cloudflare Zero Trust can automatically remove any user who does not log in to an Access application or who does not trigger a device enrollment event within a specified time period (between one month and one year). These users will no longer count against your seat count.
60+
Cloudflare Zero Trust can automatically remove any user who does not log in to an Access application or who does not trigger a device enrollment event within a specified time period (between one month and one year). These users will no longer count against your number of seats.
6161

6262
To enable user seat expiration:
6363

@@ -68,4 +68,4 @@ To enable user seat expiration:
6868

6969
If a user is removed but authenticates later, they will consume a seat again.
7070

71-
For more information about the consequences of removing a user for Access and Gateway, refer to the [FAQ](/cloudflare-one/faq/getting-started-faq/#removing-users).
71+
For more information about removing a user for Access and Gateway, refer to the [FAQ](/cloudflare-one/faq/getting-started-faq/#removing-users).

0 commit comments

Comments
 (0)