Skip to content

Commit 6e99f04

Browse files
kennyj42maxvp
andauthored
Update seat-management.mdx (#17990)
Co-authored-by: Max Phillips <[email protected]>
1 parent 25a6e63 commit 6e99f04

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ The amount of seats available in your Zero Trust account depends on the amount o
1111

1212
## Authentication events
1313

14-
A user consumes a seat when they perform an authentication event. For Access, this is any Cloudflare Access authentication event, such as a login to the [App Launcher](/cloudflare-one/applications/app-launcher/) or an application. For Gateway, this means any Cloudflare WARP authentication event, such as enrolling a device to your Zero Trust organization.
14+
A user consumes a seat when they perform an authentication event. For Access, this is any Cloudflare Access authentication event, such as a login to the [App Launcher](/cloudflare-one/applications/app-launcher/) or an application. For Gateway, this is when any devices associated with the user connect to Zero Trust within the [specified period](#enable-seat-expiration).
1515

1616
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.
1717

0 commit comments

Comments
 (0)