Freshness updates

Author: v-wendysmith

support/dynamics-365/field-service/administration/cannot-find-user-set-up-frontline-workers.md

@@ -1,10 +1,10 @@
 ---
 title: Can't find a user when setting up frontline workers
 description: Resolves an issue where you can't find a user when trying to assign security roles in a new Field Service environment.
-author: jasonxian-msft
-ms.author: jasonxian
+ms.author: jacoh
+author: jasonccohen
 ms.reviewer: v-wendysmith
-ms.date: 11/25/2024
+ms.date: 01/09/2026
 ms.custom: sap:Administration
 ---
 # Can't find a user when setting up frontline workers in Dynamics 365 Field Service

support/dynamics-365/field-service/administration/cant-identify-user.md

@@ -4,7 +4,7 @@ description: Resolves an issue where you can't identify the user shown in an err
 author: jasonxian-msft
 ms.author: jasonxian
 ms.reviewer: v-wendysmith
-ms.date: 11/25/2024
+ms.date: 01/09/2026
 ms.custom: sap:Administration
 ---
 # Can't identify the user shown in an error message in Dynamics 365 Field Service

support/dynamics-365/field-service/administration/disable-auto-geo-code.md

@@ -15,19 +15,19 @@ Users can't save records, such as work orders, accounts, contacts, or system use
 
 ## Cause
 
-The issue originates from a service degradation in the location APIs that the [Universal Resource Scheduling](/dynamics365/field-service/universal-resource-scheduling-for-field-service) solution uses to get the latitude and longitude information for addresses.
+The issue comes from service degradation in the location APIs that the [Universal Resource Scheduling](/dynamics365/field-service/universal-resource-scheduling-for-field-service) solution uses to get the latitude and longitude information for addresses.
 
 ## Workaround
 
 As a user, try saving the record again to ensure it's not a temporary issue.
 
 As an administrator:
 
-- To unblock operations like creating or updating records in case of a consistent failure, you can temporarily disable the [Auto Geo Code Addresses](/dynamics365/field-service/turn-on-auto-geocoding) setting in **Field Service Settings**. After re-enabling the setting, users need to manually geocode records that were updated during the outage.
+- To unblock operations like creating or updating records in case of a consistent failure, temporarily disable the [Auto Geo Code Addresses](/dynamics365/field-service/turn-on-auto-geocoding) setting in **Field Service Settings**. After re-enabling the setting, users need to manually geocode records that you updated during the outage.
 
   > [!CAUTION]
   >
-  > Disabling automatic geocoding doesn't update the geocoded information for records with updated addresses. Records might have no location information or outdated latitude and longitude values, which might affect scheduling activities that rely on location coordinates. We recommend tracking the updated records while the setting is disabled to address data gaps retroactively.
+  > Disabling automatic geocoding doesn't update the geocoded information for records with updated addresses. Records might have no location information or outdated latitude and longitude values, which might affect scheduling activities that rely on location coordinates. Track the updated records while the setting is disabled to address data gaps retroactively.
 
 - If your organization uses custom apps that call the location APIs directly from any of their processes, adjust the processes to stop calling them until the service degradation is resolved.
 

support/dynamics-365/field-service/administration/media/cant-identify-user/systemuser-id.png

@@ -1,10 +1,10 @@
 ---
 title: Incorrect user privileges errors in Dynamics 365 Field Service
 description: Resolves privileges errors that occur when a user tries to access work orders in Microsoft Dynamics 365 Field Service.
-author: jasonxian-msft
-ms.author: jasonxian
+ms.author: jacoh
+author: jasonccohen
 ms.reviewer: v-wendysmith
-ms.date: 11/25/2024
+ms.date: 01/09/2026
 ms.custom: sap:Administration
 ---
 # Incorrect user privileges errors in Dynamics 365 Field Service
@@ -28,8 +28,5 @@ When a user tries to access work orders, the following error messages appear, in
 > [!NOTE]
 > You need administrator permissions in Dynamics 365 Field Service to perform the following action.
 
-To solve this issue, [assign the correct security role and field security profile](/dynamics365/field-service/flw-admin?tabs=viva#assign-security-roles-and-field-security-profiles) to the user.
+To resolve this issue, [assign the correct security role](/dynamics365/field-service/users-licenses-permissions#assign-security-roles) and [field security profile](/dynamics365/field-service/security-permissions) to the user.
 
-## More information
-
-[Set up users, licenses, and security roles](/dynamics365/field-service/users-licenses-permissions)

support/dynamics-365/field-service/administration/user-has-no-roles.md

@@ -21,6 +21,6 @@ This issue occurs if the value of [msdyn_CascadeCrewChanges](/common-data-model/
 
 ## Resolution
 
-To fix the issue, open the booking and set the value of `msdyn_CascadeCrewChanges` to **Yes**. Then, assign the booking to a crew again.
+To fix the issue, open the `Booking` entity and set the value of `msdyn_CascadeCrewChanges` to **Yes**. Then, assign the booking to a crew again.
 
 For more information, go to [Group resources in crews](/dynamics365/field-service/resource-crews).