Provide preference to always allow anyone with a link to access my Content Fusion tasks

Are you missing a feature? Request its implementation here.
RuthHoward8
Posts: 2
Joined: Tue Apr 08, 2025 2:50 pm

Provide preference to always allow anyone with a link to access my Content Fusion tasks

Post by RuthHoward8 »

Every time I create a CF task, I have to set the sharing on that task to allow anyone with the link to access it. Then I email the link to the reviewers.
Sometimes (often) I forget to change the task sharing and then the reviewers reply that they don't have access.
Please can we have a preference that allows me to have the sharing set to "anyone with the link" on all tasks that I create, rather than having to set it manually each time.
cosminef
Site Admin
Posts: 233
Joined: Wed Aug 30, 2023 2:33 pm

Re: Provide preference to always allow anyone with a link to access my Content Fusion tasks

Post by cosminef »

Hello,

Thank you for contacting us.

We have logged a feature request (CF-4516) related to the use case you described. For now, it is not scheduled for development, but we will notify you once it is implemented.

Best,
Cosmin
Cosmin Eftenie
www.oxygenxml.com
cosminef
Site Admin
Posts: 233
Joined: Wed Aug 30, 2023 2:33 pm

Re: Provide preference to always allow anyone with a link to access my Content Fusion tasks

Post by cosminef »

As a workaround, until this option is added to the UI (according to the registered ticket CF-4516), you can set the task_default_access variable to PUBLIC in the api.properties file that can be found on the machine where Content Fusion is installed at: /fusion/data/config/api/ [1].

So, on the machine where Content Fusion is installed, you need to modify the file /fusion/data/config/api/api.properties by adding the following line:

Code: Select all

task_default_access=PUBLIC
This means that all newly created tasks from the moment of this change will have the checkbox "Anyone who opens the link is automatically granted access as a Reviewer" selected.

Of course, for the change made in the api.properties file to take effect, the Content Fusion server needs to be restarted [2].

Best,
Cosmin

[1] https://www.oxygenxml.com/doc/versions/ ... iting.html
[2] https://www.oxygenxml.com/doc/versions/ ... 45_zhw_43b
Cosmin Eftenie
www.oxygenxml.com
Post Reply