LinkedIn org scopes (r_organization_admin / w_organization_social) on Connect MCP — how to add them to my auth config? (ref: issue #4138)

Hi Composio team,

Setup: Composio Connect MCP (connect.composio.dev/mcp) with a consumer API key, workspace bakarrkhann_workspace, LinkedIn toolkit.

Goal: Publish only to my company page (Synaptix Studio) as urn:li:organization:... via LINKEDIN_CREATE_LINKED_IN_POST — never as a person.

Problem: LINKEDIN_GET_COMPANY_INFO returns 403 on every admin-side connection, including one freshly authorized today:

"Forbidden. You don't have permission to access organization ACLs. Ensure you have the r_organization_admin scope."

Connections: linkedin_aswell-maimon and linkedin_posted-maggy (same LinkedIn login, both ACTIVE) Failed call log IDs: log_7RftuLjWyTUe, log_-ozyECJSi2N_ LINKEDIN_GET_MY_INFO succeeds on the same connections, so the connection is healthy — personal scopes only. I already did a full OAuth re-authorize via a Connect link after the first 403; the new grant still has no org scopes. This matches your KB note ("reconnecting an unchanged config does not add scopes") and open issue #4138. Questions:

What are the exact dashboard steps to edit/create a custom auth config for the linkedin toolkit that requests r_organization_admin + w_organization_social (± r_organization_social)? Are org scopes possible on the default managed LinkedIn config, or does company-page posting require the linkedin_ads toolkit or my own LinkedIn developer app? If my own app: which products must be enabled, and what redirect URI should I register? After the config is updated, do existing connected accounts pick up the new scopes, or must I connect fresh (and then delete the old connections)? Is there a way to verify which scopes a connected account actually holds via the MCP consumer key or API, without dashboard access? Thanks!