Community
Q&A
Confluence
Questions
Restring blogposts in automation unable to succeed

Restring blogposts in automation unable to succeed

Hi,
I am currently trying to set up an automation flow which looks for newly created blogposts and turns their access from editable for everyone in space to "Anyone in space can view, only some can edit." with the edit permission given to admin.

However, the "Restrict page" action keeps failing with the error message "Content must be of type page." I suspect that the "Restrict page" action doesn't work for the blogposts.

Note that the extraction of the blogposts that were newly created has been implemented by placing a "Branch flow/related entity" block, which works fine according to the audit log.

I am wondering if there is any workaround for implementing the automated access changer dedicated for blogposts, preferably within the Automation framework. Any comments and suggestions would be appreciated.

2 answers

2 accepted

0 votes

Answer accepted

Hi @Kiwamu Izumi

Welcome to the community.

Blog posts are not considered pages, but a type of page, you can only manage permissions on a post in the GUI.

Also via API the restrictions can't be edited, vai automation also not as blogpost are not considered as a standard page

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Yes, you can add/update restrictions via API > Confluence REST API / Content restrictions / Add restriction

I did try this for pages, but it should be valid for blog posts as well.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi @Marc -Devoteam- , @Tomislav Tobijas
Thank you so much for answering to my question! I see the point.
I might set up a work around as suggested by @Tomislav Tobijas where the web request is triggered so that the administrator can change the permission via the GUI.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • like this

0 votes

Answer accepted

Hi @Kiwamu Izumi ,

You could try using Send web request action for this. So, instead of the "Restrict page" action, add a "Send web request" block after your branch:

URL: https://your-domain.atlassian.net/wiki/rest/api/content/{{blogpost.id}}/restriction/byOperation/update/user

Method: PUT

Headers:

Accept: application/json

Content-Type: application/json

Body: Include the accountId of the admin you wish to grant edit access to

Note that I haven't tested this myself, but I've built something similar on one site and it worked.

There's also this feature request related to what you're looking for (and some broader features as well): CONFCLOUD-82971: Enable native blog post creation as an action in Automation for Confluence

Cheers,
Tobi

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi @Tomislav Tobijas ,
Thank you for the suggestion --- seems like this is a good workaround. I will try setting this up!

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Tomislav Tobijas likes this

Suggest an answer

Was this helpful?

Thanks!

Confluence

DEPLOYMENT TYPE

CLOUD

PRODUCT PLAN

STANDARD

PERMISSIONS LEVEL

Product Admin

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Restring blogposts in automation unable to succeed

2 answers

2 accepted

Suggest an answer

Was this helpful?

Thanks!

DEPLOYMENT TYPE

PRODUCT PLAN

PERMISSIONS LEVEL

TAGS

Atlassian Community Events