Update seat-management.mdx #17990
Update seat-management.mdx #17990
Conversation
This was incorrect, we look at the last seen value from gateway
| ## What constitutes 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 ZT organization. | ||
| 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 is if any devices associated have been seen in the specified period. |
There was a problem hiding this comment.
| 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 is if any devices associated have been seen in the specified period. | |
| 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 is if any devices associated with the user have been seen in the specified period. |
There was a problem hiding this comment.
What is the specified period?
There was a problem hiding this comment.
The period is the setting in https://developers.cloudflare.com/cloudflare-one/identity/users/seat-management/#enable-seat-expiration.
However after looking at this page again I think we should leave the original statement. That is what constitutes an authentication event. However we consider any seat active for the purposes of seat expiration if they have any devices associated that have been seen. I'm not sure how we should rework the page for that.
There was a problem hiding this comment.
However we consider any seat active for the purposes of seat expiration if they have any devices associated that have been seen.
@maxvp perhaps this info could go into the Seat Expiration section:
https://github.com/cloudflare/cloudflare-docs/pull/18081/files#diff-50a1ac1c6b0bd5ec93cc24a705dc80e9bed38d044bc889dc39d41eba6bdb2ce1R60
|
relates to #18081 |
|
Yes they would. Your change still has the "or trigger a WARP enrollment" portion which isn't correct. |
Deploying cloudflare-docs with
|
| Latest commit: |
6ace9d2
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9f72069e.cloudflare-docs-7ou.pages.dev |
| Branch Preview URL: | https://kennyj42-patch-3.cloudflare-docs-7ou.pages.dev |
|
Files with changes (up to 15) |
Co-authored-by: Max Phillips <[email protected]>
4 participants
This was incorrect, we look at the last seen value from gateway
Summary
Screenshots (optional)
Documentation checklist