Publish an unpublished project to a Space

Move prepared work into its department without creating a second project.

Use Publish to Space when a personal unpublished project is ready to belong to a department. Publication moves the existing project into the selected Space. It does not create a copy or publish a public web page.

Before you publish

Confirm the organization and the project you intend to move. You need the appropriate authority for the project and a permitted destination. The destination list comes from your project-creation authority, not simply from the Spaces you can read.

Decide whether the project is ready for the destination’s access context. Review its task descriptions, notes, files, and sharing. “Unpublished” describes where the project lives; it is not a blanket confidentiality guarantee.

Publish the project

  1. Find the unpublished project in My Spaces.
  2. Open its project menu and choose Publish to Space….
  3. Select an available department in the dialog.
  4. Choose Publish and wait for the action to complete.
  5. Find the project under its destination and open All Tasks to confirm the work is still present.
  6. Review effective access in the destination before telling the team to use it.

The publication picker places the project at the Space’s top level. It does not offer a folder destination. If a folder is needed later, use the supported move flow and satisfy that operation’s permissions.

If no destination is available

The dialog leaves the project in your personal projects and explains that no Space is currently available. Ask an Owner or Admin to review your primary department and creation exceptions. Sharing an existing department project with you does not necessarily make the department available for publication.

What to check after publication

The project should leave the personal unpublished list and appear in its departmental context wherever you have the corresponding navigation access. Confirm its existing tasks and views rather than creating a replacement. Review who can access it now: moving into a Space can affect inherited access, while direct grants and blocks also matter.

A colleague may still be unable to open the project because of their organization, area access, organization role, or resource permissions. Sending the new location or copying its URL does not grant access.