Planning Analytics

Hi Ronan,

Thank you for your feedback, let us investigate your scenario and provide you with the answer after that.

That area of book including the websheets with inherited permissions is indeed important as it propagate how the assets are being accessed by the plan users.

Best regards,

Hi Ronan,

We design the Plann access to the assets such as books in the following way:

If a parent folder does not have full access, a book won't have full access and you will see the error.

Could you check what kind of an inherited permissions you have for a parent folder and try the permissions? 

Best regards,

Hi Svetlana,

Thank you for the reply and context.

I just tried a test. Assigned 'Full Control' to the group accessing the plan on the parent folder and my book inherit permissions from this folder but still receiving the error. 

From a security point of view, assigning full control to a user group (to enable the plan access without error) for a folder means they can edit/delete folders and assets. This seems like a security issue as we are only trying to give plan access.

Ronan 

Hi Ronan,

Thank you for the update.

We are working on more capabilities for Plans assets, so it'd be much better behaviour for PAW users to engage the books for Plans.

Plans would be defining the access for the plan groups to allow the proper access to the assets to Contributor, Aprover and upcoming Viewer groups.

Please check:

Q3 2026 Workflow roadmap

Best regards,

This is an interesting distinction between asset permissions and Plan access.

Ronan’s test is important here: Full Control on the parent folder with inheritance still left the task unable to save. So this is not only “grant Full Control on the folder”.

If a Plan requires the underlying book/folder to provide Full Control just to allow the task to use the book, that effectively makes permission inheritance difficult to use for a common folder structure where users should be able to access the books without being able to modify or delete the assets.

The upcoming Plan-specific access model sounds like it is intended to address exactly this separation, as also flagged on the Q3 2026 workflow roadmap. Until then, it would be useful to clarify whether there is any supported permission combination that allows a Plan group to use an inherited book without granting Full Control on the parent folder.

Otherwise, the current model appears to force administrators to choose between duplicating permissions on individual books or granting broader folder permissions than the Plan itself requires.