nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Allow non-space admin to move pages to another space

Munisense Administrator

Hi,

Is there any way to allow a non-space admin to move pages to a different space? I don't understand why that would not be possible. The user has rights to delete pages in space A and create pages in space B. They can still do a "copy" and a "delete" but that doesn't convert the history so that is kinda sad.

Why is it this way? How can I make sure this is possible?

Thanks!

Accepted answers

All comments

Tessa Tuteleers

Hi Munisense,

You are correct, you need space admin permissions in the source space to be able to move pages to another space.
Atlassian wrote a blog about why this was done, you can read it here.

They also mention an improvement by adding specific "move" permissions in the spaces, vote and watch it here.

- Tessa

Tom_Carrott_Adaptavist

Hi Munisense,

It sounds like Tessa has addressed your question, but the process you're working through really piqued my interest. We've recently launched an application on the Atlassian Marketplace called Panorama for Confluence, which I think could be a great fit for your needs.

With Panorama, you can:

✅ Gain a clear, centralised view of multiple spaces and their content
✅ Sort, filter, move, archive, delete, and make changes across multiple spaces with ease
✅ Update labels, permissions, page ownership, and more—all from one centralised location
✅ Replace multiple tools with a single app, saving both time and costs

If you’d like to learn more or have any questions, feel free to reach out. I’d be happy to connect and discuss further.

Many thanks,
Tom

Tessa Tuteleers

Hi Tom,

interesting take on things!
The security issue that Atlassian addressed (however frustrating for non-admins) is valid though, how does your app address this security problem?

- Tessa

Tom_Carrott_Adaptavist

Hi Tessa,

Thanks for your response! You’re absolutely right—the security issue Atlassian addressed is valid, and Panorama doesn’t directly solve that problem. Apologies if that wasn’t clear in my original message.

My suggestion was based on Munisense’s use case around moving and organising content, which aligns closely with some of the tools and features built into Panorama. I thought it might be worth highlighting as there could be some helpful crossover.

Let me know if you’d like more information, or if I can clarify further!

Many thanks,
Tom

Matthijs_s6cht9

Thanks, that explains it indeed. It is not how we manage restrictions so for us that would not be a problem. I commented on the improvement ticket.

Matthijs_s6cht9

Thanks, I'll have a look at this!

Barbara Szczesniak

@Matthijs If you look at this page (https://support.atlassian.com/confluence-cloud/docs/move-copy-and-hide-pages/), you can see that the Space Admin permissions are needed to move, but not to copy, the pages.

I'm not sure if copying the pages and then having the user remove them (if they have Delete permission on Pages, whiteboards, databases, and Smart Links) works the same way as moving the pages.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud