--- title: "Set up and publish a space" canonical: "https://support.appfire.com/space/AHP/649954539/Set%20up%20and%20publish%20a%20space" format: markdown --- > Macro (aura-html) > Macro (excerpt) > > You've installed the app and added the global permissions. What's next? The space administrator is now in charge! ## Overview A space administrator can link two spaces for space publishing (or a one-off copy) and publish and sync documents between the two spaces. > ℹ️ A space administrator can also [configure the space to use snapshot publishing](https://appfire.atlassian.net/wiki/spaces/AHP/pages/2229274320). ## Configure a space for space publishing Using Comala Publishing, a space administrator must [link two spaces](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649758232): the **draft source space** and a **published target space**. You need to be: - A space administrator with permissions for both spaces - A member of the Confluence group added to the app **Publishers Group **(in global permissions) You can then - [Link the two spaces](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649758232) - [Configure ](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649726972)the content to be published - Initialize the synchronization of the two spaces ## Link the draft and the published space for space publishing There are two options to set up the draft and published spaces: - **Option 1**: Publish content from one space to a new published space. - **Option 2**: Publish existing public content from a new draft space. Here are two example scenarios that can help you understand these two options. #### **Option 1: A new documentation space** > ✅ **Use this option if **you are starting a new documentation space, > ✅ > ✅ **OR **you have an existing space you want to use as the draft (source) space, and this is then published to a new space (the target space) Let's say you're starting a new documentation space - Your content is ready for your audience - You occasionally update the content - You want a clean and approved version for your audience to read You can create a new space, then use Comala Publishing to link and sync your [draft documentation space](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649758232) with this new space, which becomes the published version to share with your audience. ![image](media://b975bbb0-641d-4f85-86d7-13afc2900200) Any time you make a change to a page in the draft space, the page's state changes to **out of sync** until you publish the [space](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649692474) or the [page](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649561680). You first need to create a new *empty space*. > ℹ️ This becomes the **Published space** (the target space). ![image](media://0fc0e1f5-fa27-43d2-9e7c-51c571a4dc55) - Link the current space to the target space that will be the **Published space** ![image](media://30a6db98-f909-48ad-b8bc-78128490c921) - Choose **Publish** to synchronize the content in the two space ![image](media://4e4f8138-873e-49b2-ad05-4091235949aa) > ℹ️ Before choosing **Publish,** you can > ℹ️ > ℹ️ - **[Configure](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649726972)** the publishing options > ℹ️ - **[View Changes](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649694201)** that are pending in each of the draft and the published spaces Once synced, you can make changes to your content in the new **draft space (the source space),** then publish [the whole space](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649692474) or individual [pages](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649561680). #### **Option 2: Adding to a populated space** > ✅ **Use this option if **you have an existing space, on which people have comments, watched pages, etc, > ✅ > ✅ **AND **you need a draft space to which you can make changes, and when approved, publish this to your existing space Let's say you have a space that: - Is rich in content - Already has comments - Has users watching pages and user labels You need a new draft space that you can publish from to the pre-existing populated space. ![image](media://9c064187-982d-4c80-b21f-ee2fb98dbf21) You first need to create a new *empty space*. > ℹ️ This becomes the **Draft space** (the source space). The existing populated space is the **Published space,** and the initial configuration of Comala Publishing for this **Option *****2**** is in the space tools in this populated space*. In the populated **Published space** space tools use the Comala Publishing option to **Publish from another Space** ![image](media://677413c0-b497-4b53-9ce3-06842e5291dd) - Link two spaces by using the dropdown menu to choose the **draft space** ![image](media://bf6f1e92-eae6-49ea-b3cf-d73a84abb9a2) - Choose **Link** An on-screen dialog confirms linking the two spaces. ![image](media://4723ea53-5b44-4cda-ac52-9be45fe12ba1) - Choose **Finish** The next step is to synchronize the content in the two spaces. ![image](media://7a36ca5c-2a09-4614-8921-d5ec627830fd) - Choose** Synchronize** to copy the populated space content to the new **draft space** All the content on the current populated space is copied over to the linked **draft space**. > ℹ️ Before choosing **Synchronize**, you can select **Advanced options** to manage the configuration for this initial copy process. ![image](media://c1a35e0b-d0da-4f95-a7e8-4410f3c253ad) Once this initial synchronization is complete, navigate to the new linked **Draft space **(source space). In the new **Draft space **(source space)**,** **[configure publishing options](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649662146)**** **to decide how to handle deleted pages, labels, properties, and more. > ℹ️ All further configuration and publishing of Comala Publishing is now undertaken in this linked **Draft space **(source space). You can make changes to your documents in the new **Draft space** (source space) and then publish [the whole space](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649692474) or individual [pages](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649561680). > 📝 Unlinking the spaces can only be completed in the **Draft space **space tools **Publishing dashboard.** ### Options for space publishing In the publishing screen, configure[ what to include when you publish](https://appfire.atlassian.net/wiki/spaces/AHP/pages/650119607) your draft space content. You can [set publishing options](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649662146), including - Link or change the target space using the dropdown menu - Enable users (with edit permission) to [publish single pages](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649561680) using the **Single Page Publish** slider - Exclude pages or blog posts from the publish action - Clean up of [out-of-sync pages](https://appfire.atlassian.net/wiki/spaces/AHP/pages/650249630) - Keep labels intact when publishing For publishing actions, you can use check buttons to configure the document and data to be published: - [Page content options](https://appfire.atlassian.net/wiki/spaces/AHP/pages/650119607) to determine what data is published - [Visualization options](https://appfire.atlassian.net/wiki/spaces/AHP/pages/650153492) let you choose whether or not to display the publishing status lozenge and draft watermark - [Space sync conditions](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649662146) let you publish pages, blog posts, space home page, or orphan pages, limit whole space publishing to changed content, or always publish all documents, and whether to use the sync-label to limit or exclude the documents in a publish action You can also set conditions based on an applied Comala workflow final state (*when a Comala Document Management family app is applied*). ### Exclude some page content from being published What can you do if you don't want some of the page content to be published? Comala Publishing provides a simple solution. You can - [Add the ignore-publish macro to the page](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649954840) - Place the content that you don't want published in the body of the macro ![image](media://b1d40a3c-a90c-4cf4-b383-c5847019a8c4) ### Publishing status lozenges When the **Display Publishing Lozenge** is checked, a publishing status lozenge is added to the published and synced documents in both spaces to easily identify the state of each draft and published page. ![image](media://dba45f93-a982-498d-afd3-14cfdb6bc692) The publishing status lozenges are one of - **NEW - **Content not yet published [new] - **OUT OF SYNC - **Previously published  content is now different in each space [out of sync] - **PUBLISHED **- Published content that is the same in each space [published] ### Viewing the publishing changes The **[View Changes](https://appfire.atlassian.net/wiki/spaces/AHP/pages/649694201)** option button displays any content that is out of synchronization between the draft and published space. ![image](media://2fe2b7f4-e27a-4123-badc-b18cf34ef857) Filter buttons allow you to choose the - Date range - Publishing status of content - User who last updated the content > 📝 If content is not shown as expected, check the filters in the **View changes** screen. Toggle between the target and published space to view the content in that space that is out of sync. The report lists new or edited content since the last **Publish** action within the set date filters. Here, the **Published Space** has content that is not in the **Draft Space**.0 ![image](media://2330b473-69d0-420f-89e2-d4c0fc3d2072) The report lists new or edited content since the last **Publish** action. > 📝 Some content might be listed due to the publishing configuration. > 📝 > 📝 For example, the **NOT IN DRAFT** changes lozenge in the published space can be due to the checked configuration setting **“Ignore all the top-level pages**”.  If you publish a page whose parent does not exist in the target space, it becomes an orphan in the target published space - it is published to the root of the target space. Publishing to a target space with a different home page name from the draft space home page can cause publishing problems, as the app is not designed to publish a page that is the child of the **Draft Space homepage** to be a child of a different-named homepage in the **Published Space**. ### Related pages > Macro (contentbylabel)