fastpath

packages/@okta/vuepress-site/docs/guides/update-oin-app/main/index.md

@@ -38,15 +38,41 @@ The OIN Wizard currently supports updates for integrations that use the followin
 
 > **Note:** You can use the [OIN Wizard](/docs/guides/update-oin-app/) to update OIDC, SAML 2.0, SCIM 2.0, and API service integrations that were originally submitted through the [OIN Manager](/docs/guides/submit-app/).
 
+If you need to update only catalog information, such as your app name, description, logo, or support contact information, the **Edit** button on the **Home** page directs your submission through a dedicated path. This path allows you to submit minor branding updates directly to the OIN Ops team for review without requiring functional re-testing or backward-compatibility verification.
+
 When you edit a published OIN integration, you need to test the flows for the updated version and the published version for backwards compatibility. The integration version that was previously installed in your customer's org isn't modified with the updated version from the OIN catalog. Testing the published version for backwards compatibility ensures that your integration still works for customers who have already installed it. See [Update integration considerations](#update-integration-considerations) before you edit your published integration.
 
 After you successfully test the updated and published versions of your integration, resubmit your integration to the OIN team. Your integration goes through a [submission review process](/docs/guides/submit-app-overview/#understand-the-submission-review-process) before the updated version is published in the OIN catalog.
 
 ## Update integration considerations
 
+### Update catalog information only
+
+To keep your listing accurate without consuming engineering resources, you can update catalog information independently.
+
+The edit catalog information path is available exclusively for published integrations when you access your apps from the **Home** page. Go to the **Home** page, locate the **Your apps** section, click **Edit** next to the app that you want to modify, and select **Catalog Info**. You can use this accelerated, no-test pathway to update the following catalog fields:
+
+- App name
+- Logo
+- App description
+- Contact information
+
+When you modify only these fields on a published integration, the OIN Wizard bypasses the standard technical testing environment. Once submitted, your changes are tracked through an automated operations ticket and deployed immediately upon OIN Ops team approval.
+
+If your update includes changes to functional configurations such as SAML settings, SCIM provisioning, or URLs, you must select the **Edit** >  **Integration** option instead of **Edit** > **Catalog Info** and complete the full end-to-end testing Workflow.
+
+### Functional configuration considerations
+
+To update functional settings for your published app, you can use either of the following navigation paths:
+
+- Go to the **Home** page, locate the **Your apps** section, click **Edit** next to the app, and select **Integration**.
+- Go to **Applications > Your OIN Integrations**, click your published integration, and select the standard editing option.
+
+Review the following guidelines before you edit and resubmit your configurations:
+
 For published integrations that were migrated from the OIN Manager, if you need to update configured properties that aren't available in the OIN Wizard, contact <oin@okta.com>.
 
-> **Note:** Some considerations on this page are specifically for the **<StackSnippet snippet="protocol-name" inline/>** . <br>
+> **Note:** Some considerations on this page are specifically for the **<StackSnippet snippet="protocol-name" inline/>**. <br>
 > If you want to change the instructions that you see on this page, select a different option from the **Instructions for** dropdown list.
 
 <StackSnippet snippet="considerations" />
@@ -86,28 +112,36 @@ To update a previously published OIN integration:
 1. Click your published integration to update from the dashboard. Your published OIN submission appears in read-only mode.
 
 1. From the **This integration is read-only** information box, click **Edit integration**. The **Add integration capabilities** page appears.
+
     > **Note:** You can skip this step if your submission is in draft status. The **Edit integration** option isn't available for submissions in draft status because it's not in read-only mode.
 
     <StackSnippet snippet="detect-old-instance" />
 
 1. Click **Add integration details**. The **OIN catalog properties** page appears.
 1. Update [OIN catalog properties](/docs/guides/submit-oin-app/openidconnect/main/#oin-catalog-properties) as required for your integration.
-1. Click **Configure your integration** to proceed to update your integration as required in the following sections of the OIN Wizard:
+1. Determine your update path based on your changes:
+
+    - Catalog information only updates: If you changed only catalog data (such as the name, logo, description, or contact information), confirm your intent on the prompt. The OIN Wizard bypasses configuration and testing, prompting you to submit immediately. After clicking submit, the app displays an in review status under **Your apps** section. The live version remains active in the public OIN catalog while Okta reviews your changes. See, [Update catalog information only](#update-catalog-information-only).
+    - Functional updates: If you altered settings like tenant properties, OIDC capabilities, or Universal Logout protocols, click **Configure your integration** to proceed through the standard testing tabs. See, [Functional configuration considerations](#functional-configuration-considerations).
+
+1. (For functional updates only) Click **Configure your integration** to proceed to update your integration as required in the following sections of the OIN Wizard:
 
    <StackSnippet snippet="edit-links" />
 
 1. Click **Test your integration** to save your updates and move to the testing section of the OIN Wizard.
 
 ## Test integration updates
 
+>**Note:** Test your integration only when making functional updates. When updating catalog information only, the OIN Wizard bypasses testing and proceeds directly to submission.
+
 The OIN Wizard journey includes the **Test integration** experience page to help you configure and test your updated integration within the same org before submission. These are the tasks that you need to complete:
 
 <StackSnippet snippet="test-steps" />
 <br>
 
 See [Submit your updated integration](#submit-your-updates) after all required tests are successful.
 
-> **Note:** Test steps on this page are specifically for the **<StackSnippet snippet="protocol-name" inline/>** . <br>
+> **Note:** Test steps on this page are specifically for the **<StackSnippet snippet="protocol-name" inline/>**. <br>
 > If you want to change the instructions that you see on this page, select a different option from the **Instructions for** dropdown list.
 
 ### Generate instances for testing
@@ -128,6 +162,8 @@ Generate instances for testing your updates directly from the OIN Wizard. See [R
 
 ## Submit your updates
 
+>**Note:** Submit catalog information only updates directly without configuration or testing. Your app displays an in-review status while the live version remains active in the public OIN catalog.
+
 After you successfully test your updated integration, you're ready to submit.
 
 <StackSnippet snippet="submit-checks" />