Updating Dates for Service Account Sunset and Webhook Info (#281)

Co-authored-by: Andrew Hemry <[email protected]>

Author: jimj-procoretech

announcements/service_account_deprecation.md

@@ -7,11 +7,11 @@ section_title: Announcements
 
 >**Sunset of Traditional Service Accounts** (updated 12/03/2024)
 >
->*All Traditional Service Accounts will sunset on March 24, 2025.*
+>*All Traditional Service Accounts will sunset on March 18, 2025.*
 >
 >Traditional Service Accounts were deprecated on December 9, 2021.
 >Beginning January 21, 2025, we will no longer allow the creation of new Traditional Service Accounts.
->Existing Traditional Service Accounts will continue to function until March 24, 2025.
+>Existing Traditional Service Accounts will continue to function until March 18, 2025.
 >
 >In accordance with this timeline, developers of data connection applications that currently use Traditional Service Accounts are required to update their applications to use Developer Managed Service Accounts, and customers will be required to install these updated applications before the sunset date.
 >All data connection applications not migrated by the sunset date will cease to function.

api_essentials/api_security_overview.md

@@ -32,7 +32,7 @@ Disconnecting the app in a specific company will not revoke tokens on behalf of
 >
 > Traditional Service Accounts were deprecated on December 9, 2021.
 > Beginning January 21, 2025, we will no longer allow the creation of new Traditional Service Accounts.
-> Existing Traditional Service Accounts will continue to function until March 24, 2025.
+> Existing Traditional Service Accounts will continue to function until March 18, 2025.
 > As a result of this deprecation, developers of data connection applications that currently use traditional service accounts are required to update their applications to use Developer Managed Service Accounts (DMMSAs), and customers will be required to install these updated applications before the sunset date.
 > See the following articles for information on DMSAs and steps for migrating your projects from traditional service accounts.
 > - [Deprecation of Traditional Service Accounts]({{ site.url }}{{ site.baseurl }}{% link announcements/service_account_deprecation.md %})

building_applications/developer_managed_service_accounts.md

@@ -10,7 +10,7 @@ section_title: Building Applications
 >
 > Traditional Service Accounts were deprecated on December 9, 2021.
 > Beginning January 21, 2025, we will no longer allow the creation of new Traditional Service Accounts.
-> Existing Traditional Service Accounts will continue to function until March 24, 2025.
+> Existing Traditional Service Accounts will continue to function until March 18, 2025.
 > As a result of this deprecation, developers of data connection applications that currently use traditional service accounts are required to update their applications to use DMSAs, and customers will be required to install these updated applications before the sunset date.
 > See [Deprecation of Traditional Service Accounts]({{ site.url }}{{ site.baseurl }}{% link announcements/service_account_deprecation.md %}) for additional information.
 

webhooks/webhooks_api.md

@@ -43,7 +43,7 @@ Here is an example request body for creating a Webhooks Hook at the company leve
 ```
 
 In the example above we are creating a Hook for the company associated with `"company_id":5358233`.
-In the `hook` object we specify "v2" for the api_version attribute, "procore" for the `namespace` attribute (see additional information on namespaces below), we use the `destination_url` attribute to define the URL for the Notification Endpoint, and the `destination_headers` attribute to include an Authorization Header.
+In the `hook` object we specify "v2" for the api_version attribute, "your-company-name" for the `namespace` attribute (see additional information on namespaces below), we use the `destination_url` attribute to define the URL for the Notification Endpoint, and the `destination_headers` attribute to include an Authorization Header.
 
 If we compare the example request body to what we see on the Company Webhooks page in the Procore Web user interface, we find that attributes of the `hook` object are exposed in the Endpoint Configuration section.
 See [Configure Company Webhooks](https://support.procore.com/products/online/user-guide/company-level/admin/tutorials/configure-company-webhooks) for additional information.
@@ -132,8 +132,7 @@ When using the `namespace` parameter, there are a number of requirements and bes
 
 - Namespaces are string values restricted to lowercase a-z, digits 0-9, and dashes (-).
 - Uppercase letters and special characters are not supported in namespaces.
-- If no namespace is provided with a call, the default "procore" namespace is assumed.
-- We recommend the format <publisher name>-<application name> for defining namespaces.
+- We recommend using the integration name as the <code>namespace</code> so it is isolated from other namespaces.
 
 ## Webhooks Deliveries