Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit d9a32a0

Browse files
token date updates
1 parent 507001f commit d9a32a0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

admin/authentication/authentication-tokens/org-tokens.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,9 +22,9 @@ Power users who have access to tokens in an organization see a banner, but only
2222
Token expiry
2323
================
2424

25-
By default, access tokens expire one year after the creation date. You can change the expiration date For access tokens created prior to February 28, 2022, the expiration date remains 5 years from the creation date. You can rotate a token before it expires. For details, see :ref:`access-token-rotate`.
25+
You can view the expiration dates of your tokens through the access token page. To view this page, select :guilabel:`Settings` and select :guilabel:`Access tokens`. By default, access tokens expire 18 years after the creation date. You can rotate a token before it expires. For details, see :ref:`access-token-rotate`.
2626

27-
Every organization admin receives an email 30 days before a token in their org expires. The email includes a link to Splunk Observability Cloud that displays a list of expiring tokens. You cannot customize the token expiration email.
27+
By default, every organization admin receives an email 30 days before a token in their org expires. The email includes a link to Splunk Observability Cloud that displays a list of expiring tokens. To change the expiration reminder date, see :ref:`create-access-token-date`.
2828

2929
The default access token
3030
===========================

0 commit comments

Comments
 (0)