Skip to content

Commit

Permalink
Update seat-management.mdx (#17990)
Browse files Browse the repository at this point in the history
Co-authored-by: Max Phillips <[email protected]>
  • Loading branch information
kennyj42 and maxvp authored Nov 19, 2024
1 parent 25a6e63 commit 6e99f04
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ The amount of seats available in your Zero Trust account depends on the amount o

## Authentication events

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.
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).

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.

Expand Down

0 comments on commit 6e99f04

Please sign in to comment.