Configure connected apps

when to use this feature in the usual setup, a hub is always connected to exactly one app all content will be published to a publication inside of this app, and all taxonomy terms, menus, collections etc will all be published to this app however, there can be cases where you need to have multiple apps connected to a hub multiple apps should share the same content you have multiple apps that should share the same content, but differ somewhere else, like the dynamic resources that are configured in the purple manager connecting a staging environment you need the exact same contents as in the production app, but want to test a feature first inside of a staging app, like an update of the pxp version or a new entitlement for these situations you can set up multiple apps that are connected to one hub this way, the content appears in all apps that use this publication, and entities that are connected to apps, like taxonomies and menus, will get published to all connected apps content will always be published to the publication that you select (or the default publication) with this feature you can assign post types to apps, but this feature is not relevant for publishing instead it only matters inside the hub, for example when generating links for a newsletter getting started accessing hub apps settings log in to your wordpress admin panel navigate to settings → purple ds hub you'll see the hub apps configuration interface your first app when you first access the settings, you'll see your currently configured app this is your primary app that receives all published content and configuration adding a new app step 1 enter the app id in the "add new app" section, enter the app id of the app you want to add click the "add app" button step 2 validation the system will automatically check ✅ team verification the new app belongs to the same team as your existing apps ✅ publication overlap the new app shares at least one publication with your existing apps if any validation fails, you'll see a clear error message explaining what needs to be fixed note if your hub has more than 100 taxonomy terms, the "add new app" section will be hidden and you'll see a warning message this limit prevents extremely long bulk republish operations step 3 automatic publishing once validation passes, the system automatically adds the app to your configuration starts publishing all existing configuration entities to the new app all taxonomies (categories, tags, custom taxonomies) all collections all menus step 4 monitor progress a progress modal will appear showing total number of entities being published how many have been completed how many failed (if any) overall completion percentage the process runs in the background, so you can close the modal and continue working the system will complete the publishing automatically managing multiple apps single app vs multiple apps single app mode when you have only one app configured, everything works as it always has all content types automatically use that app for links and publishing multiple apps mode when you add a second app, you'll see new options to assign specific content types to specific apps this assignment isn't relevant for content publishing as content always will get published to the specified publication this setting is relevant for generating links inside the slug, for example when a post is used inside a newsletter where the correct link needs to be generated based on the app url resolver assigning content types to apps once you have multiple apps configured you'll see a "post types" column in the apps table each app can be assigned specific content types (posts, pages, custom post types, etc ) click the post type selector for an app to choose which content types it should handle when you assign a content type to one app, it's automatically removed from other apps (each content type can only belong to one app) why this matters when generating links for content, the system needs to know which app to link to by assigning content types to apps, you control which app is used for each type of content what gets published where automatically published to all apps these configuration entities are always published to all configured apps simultaneously taxonomies categories, tags, and custom taxonomies collections static collections menus navigation menus settings plugin configuration you don't need to do anything special the system handles this automatically whenever you update these entities app specific entities these entities require you to select which app to publish to dynamic collections feeds redirects when you publish these, you'll see an app selector to choose which specific app should receive them regular content (posts, articles, issues) your regular content publishing is not affected by hub apps configuration content continues to publish through your existing publication setup, which already supports multiple apps independently removing an app when to remove an app you might want to remove an app when decommissioning a staging environment discontinuing a white label variant consolidating multiple apps into one how to remove an app find the app in the configured apps table click the "remove" button read the confirmation dialog carefully click "remove" to confirm important data cleanup ⚠️ warning when you remove an app from your hub the app is removed from your hub configuration future updates to taxonomies, collections, and menus will no longer be sent to that app data remains in the removed app it is not automatically deleted you must manually clean up data in the removed app if needed you cannot remove the last remaining app your hub must always have at least one app configured updating an app id (when only one app is configured) if you need to change an app's id (for example, switching from a test app to a production app) find the app in the configured apps table click the edit icon next to the app id enter the new app id click the save icon to confirm the system will update the configuration immediately note that this doesn't trigger a bulk republish only future updates will be sent to the new app id understanding validation requirements team requirement all apps in your hub must belong to the same team this ensures consistent access permissions proper billing and usage tracking authorized data sharing error example "cannot add app the app belongs to a different team current team team 123, app team team 456" solution contact your team administrator to ensure the app is created in the correct team publication overlap requirement all configured apps must share at least one publication this ensures content can flow between apps through publications consistent content structure across apps valid linking between content and configuration error example "cannot add app the app does not share any publications with the existing configured apps " solution in purple manager, configure at least one shared publication between your apps before adding them to the hub taxonomy term limit when adding a new app, the system checks if you have more than 100 taxonomy terms this limit prevents extremely long bulk republish operations error example "cannot add app more than 100 taxonomy terms exist current count 250" solutions clean up unused taxonomy terms (categories, tags you no longer use) manually republish entities in smaller batches instead of using automatic bulk publishing contact support if you need assistance with large scale migration you can check your current term count anytime the count is displayed in the error message you see in the hub settings common scenarios scenario 1 setting up a staging environment goal add a staging app to test changes before production create your staging app in purple manager ensure the staging app has the same publications as your production app add the staging app id in hub apps settings wait for bulk republish to complete ( 2 minutes) assign test content types to the staging app if needed your staging environment now receives all configuration updates automatically scenario 2 white label variants goal manage multiple branded apps with the same content structure create branded apps in purple manager (e g , "brand a app", "brand b app") configure shared publications for all branded apps add each branded app to your hub assign content types to control which app handles which content all brands automatically receive taxonomy, collection, and menu updates scenario 3 removing a decommissioned app goal stop publishing to an app that's no longer in use ensure you have at least 2 apps configured (cannot remove the last app) click "remove" on the decommissioned app confirm the removal reassign any post types that were assigned to the removed app optionally manually delete data from the decommissioned app in purple manager best practices before adding a new app verify team membership confirm the app belongs to your team configure publications set up shared publications in purple manager plan for downtime bulk republish may take several minutes for large sites test with staging first add a staging app before production apps