LinkedIn: record CMA self-serve blocker (auto-added default products grey Request access; app 257140099 created+verified, client 86z1h5ic86lw65, org 3090253)

aae7c9c8d0eb218c3d23c82f44400a37921d8f0e · 2026-07-21 17:19:30 -0700 · Steve Abrams

Files touched

M docs/submissions/linkedin-app-review.md

Diff

commit aae7c9c8d0eb218c3d23c82f44400a37921d8f0e
Author: Steve Abrams <steve@designerwallcoverings.com>
Date:   Tue Jul 21 17:19:30 2026 -0700

    LinkedIn: record CMA self-serve blocker (auto-added default products grey Request access; app 257140099 created+verified, client 86z1h5ic86lw65, org 3090253)
---
 docs/submissions/linkedin-app-review.md | 24 +++++++++++++++++++++++-
 1 file changed, 23 insertions(+), 1 deletion(-)

diff --git a/docs/submissions/linkedin-app-review.md b/docs/submissions/linkedin-app-review.md
index 010acd8..d09d9eb 100644
--- a/docs/submissions/linkedin-app-review.md
+++ b/docs/submissions/linkedin-app-review.md
@@ -11,7 +11,29 @@ deploy → verify a real post) run. Budget two work sessions separated by the re
 
 ---
 
-## 0. Why a NEW app (the root blocker, tooltip-confirmed 2026-07-21)
+## ⛔ BLOCKER FOUND 2026-07-21 — the "new app = CMA-only" plan does NOT work as written
+
+Created the dedicated app **`DW Marketing – Community`** (app id `257140099`, **Client ID
+`86z1h5ic86lw65`**, **Company verified** to the DW Page automatically — Steve created it as a
+Page admin). But on the new app's **Products** tab, LinkedIn had **auto-provisioned three default
+products** — **Share on LinkedIn**, **Sign In with LinkedIn (OpenID Connect)**, **Verified on
+LinkedIn** — and there is **NO UI to remove them** (product cards expose only "View docs" /
+"Endpoints"; no remove/manage control anywhere). That greys out CMA's **Request access**, tooltip
+verbatim:
+
+> "This API product requires that it be the only product on the application for legal and security
+> reasons. This product cannot be requested because there are currently other provisioned products
+> or other pending product requests. A new developer application can be created to request this product."
+
+So a brand-new dedicated app hits the **exact same wall** as the old one — creating yet another app
+won't help if it too auto-gets the defaults. **Self-serve CMA request is blocked.** Realistic paths
+(need Steve): (a) **LinkedIn API Partner Support** ticket to strip the default products OR grant CMA
+directly (channel: Microsoft Learn "LinkedIn API Partner Support Guide"); (b) confirm whether an app
+created *without* a Company Page association avoids the defaults (but CMA requires a verified Page —
+likely circular). Until this is resolved, Steps 1–4 below cannot proceed. **Captured for the eventual
+finish:** Client ID `86z1h5ic86lw65`; DW Company Page org id **3090253** → `LINKEDIN_ORG_URN=urn:li:organization:3090253`.
+
+## 0. Why a NEW app (the ORIGINAL plan — superseded by the blocker above)
 
 Posting to the DW **Company Page** requires the `w_organization_social` scope, which is only
 granted by the **Community Management API** product. LinkedIn enforces a hard policy:

← 2becbe5 submissions: Facebook pages_manage_posts App Review package · back to Marketing Command Center · LinkedIn: filed Developer Support ticket CAS-11523819 to unb 5459b68 →