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; } } }

Why is it not possible to create user macro's as non-admin user?

unknown

Why is a "normal" user not allowed to create macro's?

Isn't it the "normal" user who wishes to improve things he/she is documenting?

I dont't want administrator rights, but I do want to see what other options there are to improve our documentation by automating stuff. And I think it can be done by creating my own macro.. but well.. I am not allowed.. Why, why, WHY?

The same goes for why I am not allowed to see how our confluence is hosted, which is needed info to create this question..

Accepted answers

Nic Brough -Adaptavist-

Badly written or incorrect user macros can do damage ranging from page errors or making pages unusable through to taking down a Confluence system. The ability to do that should never be given to general users, it has to be controlled by the people who have to look after the system.

If you want a new user macro, you could do it in your own development system and then give it to your admins to add for you when you've got it right in dev.

All comments

Nic Brough -Adaptavist-

If you want a new user macro, you could do it in your own development system and then give it to your admins to add for you when you've got it right in dev.

unknown

Thank you for your answer Nic,

That sounds fair enough.

But is there no possibility to give normall users the ability to create a macro that cannot have such an impact on the system?

So I can build my own confluence sandbox somehow? That would be a thing what I would want anyway, without others bothering with my useless changes.

Nic Brough -Adaptavist-

No, because almost all the power in user macros is granted by access to things that could break. There's some minor formatting stuff you could do with them safely, but a whole "protection" layer would have to be wrapped in to prevent even those being allowed to do moderately bad things, and it's simply not worth it.

Your admins should have access to a "developer licence" for your Confluence sandbox - you can do a simple standalone install on your local machine and use the dev licence for it.

unknown

Thanks for the explanation. Too bad it cannot be done easily, or it might just also not be the thing I would want to have anyway. Since I don't know what I am looking for exactly, it doesn't make it easier to find out with just reading some documentation.

I will look into the developer license with our admin. Thank you for pointing me in that direction.