Rename the 'Service Accounts' user guide section

sirosen · sirosen · commit 1d2881fe0be5 · 2026-01-14T10:15:11.000-06:00
To follow our structure of concept/noun naming for the categories in the
usage patterns section.
diff --git a/docs/user_guide/usage_patterns/index.rst b/docs/user_guide/usage_patterns/index.rst
@@ -29,4 +29,4 @@ transfers.
 
     data_transfer/index
     sessions_and_consents/index
-    client_identities/index
+    service_accounts/index
diff --git a/docs/user_guide/usage_patterns/service_accounts/index.rst b/docs/user_guide/usage_patterns/service_accounts/index.rst
@@ -1,16 +1,18 @@
-.. _userguide_client_identities:
+.. _userguide_service_accounts:
 
-Using Client Identities
-=======================
+Service Accounts
+================
 
 Some clients registered in Globus may operate as independent "service accounts",
 distinct actors with their own identities.
-This is useful for a wide range of automation tasks, in which users want to
-leverage Globus APIs, but without handling login flows and user credentials.
-
-To make use of Client Identities in this way, the client must be registered as a
-"service account", capable of performing a *client credentials grant* to get
-its tokens.
+These are also referred to as "client identities" because the actor in question
+is the client itself.
+Service accounts useful for a wide range of automation tasks, in which users
+want to leverage Globus APIs, but without handling login flows and user
+credentials.
+
+To make use of clients in this way, the client must be registered as a Service
+Account, capable of performing a *client credentials grant* to get its tokens.
 Once it is so registered, such a client will have an ID and secret, which can be
 passed into interfaces in the SDK.
 The client credentials (ID and secret) are used to get tokens to power
@@ -19,7 +21,7 @@ these tokens appropriately.
 
 .. note::
 
-    In order to be used as a Client Identity, a client must have an ID and secret.
+    In order to be used as a Service Account, a client must have an ID and secret.
     However, not every client with an ID and secret supports this usage! Clients
     may be registered with various different OAuth2 grant types enabled, and some
     clients have an ID and secret but are used to authenticate user logins!
@@ -28,8 +30,8 @@ these tokens appropriately.
     for this kind of usage.
 
 .. toctree::
-    :caption: Using Client Identities with the SDK
+    :caption: Using Service Accounts with the SDK
     :maxdepth: 1
 
-    registering_a_client_identity
+    registering_a_service_account
     using_client_app/index
diff --git a/docs/user_guide/usage_patterns/service_accounts/registering_a_service_account.rst b/docs/user_guide/usage_patterns/service_accounts/registering_a_service_account.rst
@@ -1,17 +1,17 @@
-.. _userguide_register_client_identity:
+.. _userguide_register_service_account:
 
-Registering a Client Identity
+Registering a Service Account
 =============================
 
-In order to be used as a Client Identity or "service account", a client must
+In order to be used as a Service Account or "Client Identity", a client must
 be registered in Globus Auth under the correct type.
 
 This is similar to the
 :ref:`getting started documentation on registering an app <tutorial_register_app>`,
 but using some different settings.
 
-Creating the Client Identity
-----------------------------
+Creating the Client
+-------------------
 
 The following steps will walk you through how to register a client for use as a
 service account.
diff --git a/docs/user_guide/usage_patterns/service_accounts/using_client_app/client_app_ls.py b/docs/user_guide/usage_patterns/service_accounts/using_client_app/client_app_ls.py
diff --git a/docs/user_guide/usage_patterns/service_accounts/using_client_app/index.rst b/docs/user_guide/usage_patterns/service_accounts/using_client_app/index.rst
@@ -15,7 +15,7 @@ Instantiating a ClientApp
 
 Constructing an app takes three required parameters,
 
-- a human readable name to identify your app in HTTP requests and token caching (e.g., “My Cool Weathervane”).
+- a human readable name to identify your app in HTTP requests and token caching (e.g., "My Cool Weathervane").
    - this does not need match the name you supplied during client registration.
 - the client ID
 - the client secret
