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

Commit 64fbbb9

Browse files
remaining token creation changes
1 parent fbb7249 commit 64fbbb9

File tree

1 file changed

+10
-5
lines changed

1 file changed

+10
-5
lines changed

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

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ To manage your access (org) tokens:
4040

4141
#. Open the :guilabel:`Settings` menu.
4242
#. Select :menuselection:`Access Tokens`.
43-
#. To find the access token in a large list, start entering its name in the search box. Splunk Observability Cloud returns matching results.
43+
#. To find the access token in a large list, use the :guilabel:`Status` and :guilabel:`Scope` filters or enter the token name in the search bar.
4444
#. To look at the details for an access token, select the expand icon next to the token name.
4545

4646
For information about the access token permissions allowed by the :guilabel:`Authorization Scopes` field value, see the permissions step in :ref:`create-access-token`.
@@ -105,7 +105,7 @@ Next, complete each step in the access token creation guided setup:
105105

106106
.. _create-access-token-name:
107107

108-
#. Name the token and select the authorization scope
108+
Name the token and select the authorization scope
109109
-------------------------------------------------------------------------
110110

111111
To get started with creating the token, enter a name and scope for the token. Complete the following steps:
@@ -144,7 +144,7 @@ To get started with creating the token, enter a name and scope for the token. Co
144144

145145
.. _create-access-token-permissions:
146146

147-
#. Determine who can view and use the token
147+
Determine who can view and use the token
148148
--------------------------------------------------------
149149

150150
Next, configure token permissions so your organization's users and teams can use the token. Complete the following steps:
@@ -179,14 +179,19 @@ Next, configure token permissions so your organization's users and teams can use
179179

180180
.. _create-access-token-date:
181181

182-
#. Configure an expiration date
182+
Configure an expiration date
183183
-----------------------------------------------
184184

185185
To finish creating the token, select an expiration date for the token.
186186

187187
#. In the :guilabel:`Expiration date` box, select a date at which the token will expire. The date can't be over 5 years from the token creation date.
188+
#. In the :guilabel:`Expiration alert` box, select from one of the following options:
188189

189-
#. To create the new token, select :guilabel:`Create`.
190+
* :menuselection:`Only admins can receive alert`: Only admins receive an alert when the token is close to its expiration date.
191+
* :menuselection:`Admins and users or teams with token permissions can receive alert`: Admins and any users with token permissions receive an alert when the token is close to its expiration date.
192+
193+
#. Optionally, set a time for when Splunk Observability Cloud sends an expiration alert. For example, a value of 7 days means Splunk Observability Cloud will send an alert 7 days before the token expires.
194+
#. Select :guilabel:`Create` to finish creating the new token.
190195

191196
.. _access-token-rotate:
192197

0 commit comments

Comments
 (0)