I created a plan with an approval hierarchy, but users who are only in the approval groups do not have access to the plan. Only the groups in the collaboration section have access. I tested this in versions 2.0.95 and 2.0.97. Approval group users receive emails about tasks needing approval, but they can't access the application when clicking the link. I bypassed this by creating a disabled task with access to a dummy book and granting direct access to the required book. Is this behavior expected, or should the plan automatically grant access to approvers?

Hi Alessandro,

I am the community manager for Planning Analytics and i'm checking to see if you were able to resolve your issue or obtained a response to your question. If not, I will follow-up on your behalf.

Thanks,

Nick

I created a plan with an approval hierarchy, but users who are only in the approval groups do not have access to the plan. Only the groups in the collaboration section have access. I tested this in versions 2.0.95 and 2.0.97. Approval group users receive emails about tasks needing approval, but they can't access the application when clicking the link. I bypassed this by creating a disabled task with access to a dummy book and granting direct access to the required book. Is this behavior expected, or should the plan automatically grant access to approvers?

Hi, I haven't received any response to this. The problem still persists.

Hi Alessandro,

I am the community manager for Planning Analytics and i'm checking to see if you were able to resolve your issue or obtained a response to your question. If not, I will follow-up on your behalf.

Thanks,

Nick

I created a plan with an approval hierarchy, but users who are only in the approval groups do not have access to the plan. Only the groups in the collaboration section have access. I tested this in versions 2.0.95 and 2.0.97. Approval group users receive emails about tasks needing approval, but they can't access the application when clicking the link. I bypassed this by creating a disabled task with access to a dummy book and granting direct access to the required book. Is this behavior expected, or should the plan automatically grant access to approvers?

I will look into this.  My understanding is that any user should have access to the plan if they belong to a group that was added to the task as either an contributor or approver.

When you add a PAW group as a contributor or reviewer the plan does check the permission level of the group to all assets (books and views) used in the task.  If the group does not have at least 'View only 'permissions the plan will try to set 'View only' permissions ('View only' does allow users to interact with the book and enter data).  If the group already has at least 'View only' access then the plan does not change permissions.  However, there are possible reasons why permissions cannot be assigned to an asset in the task.  For example, the folder containing the books has permissions set to prevent access and the asset has the inherit permissions from parent folder option enabled.  The plan will typically throw a warning in this case.  Another possible cause if the plan owner not having the permission that is required (Full control) to modify the permissions on the asset used in the task.  Is it possible that either of these explain the problem? 

This might be a good time to open a support case.

Hi, I haven't received any response to this. The problem still persists.

Hi Alessandro,

I am the community manager for Planning Analytics and i'm checking to see if you were able to resolve your issue or obtained a response to your question. If not, I will follow-up on your behalf.

Thanks,

Nick

I created a plan with an approval hierarchy, but users who are only in the approval groups do not have access to the plan. Only the groups in the collaboration section have access. I tested this in versions 2.0.95 and 2.0.97. Approval group users receive emails about tasks needing approval, but they can't access the application when clicking the link. I bypassed this by creating a disabled task with access to a dummy book and granting direct access to the required book. Is this behavior expected, or should the plan automatically grant access to approvers?

Hi, Stuart! Thanks for the response.

The application doesn't throw any errors when I refresh the security. I have full control access to the book, and the folders have no permissions blocking access to any groups nor inherit permissions. I don't think any of the problems you mentioned are the case because otherwise, the plan wouldn't grant view-only access to the groups who are collaborators. As I said, when I put the approvers' groups in the "collaborators" section of a task on the same plan, they are granted access to view the plan.

I opened a ticket for this, just wondering if you guys could replicate this behavior.

I will look into this.  My understanding is that any user should have access to the plan if they belong to a group that was added to the task as either an contributor or approver.

When you add a PAW group as a contributor or reviewer the plan does check the permission level of the group to all assets (books and views) used in the task.  If the group does not have at least 'View only 'permissions the plan will try to set 'View only' permissions ('View only' does allow users to interact with the book and enter data).  If the group already has at least 'View only' access then the plan does not change permissions.  However, there are possible reasons why permissions cannot be assigned to an asset in the task.  For example, the folder containing the books has permissions set to prevent access and the asset has the inherit permissions from parent folder option enabled.  The plan will typically throw a warning in this case.  Another possible cause if the plan owner not having the permission that is required (Full control) to modify the permissions on the asset used in the task.  Is it possible that either of these explain the problem? 

This might be a good time to open a support case.

Hi, I haven't received any response to this. The problem still persists.

Hi Alessandro,

I am the community manager for Planning Analytics and i'm checking to see if you were able to resolve your issue or obtained a response to your question. If not, I will follow-up on your behalf.

Thanks,

Nick

I created a plan with an approval hierarchy, but users who are only in the approval groups do not have access to the plan. Only the groups in the collaboration section have access. I tested this in versions 2.0.95 and 2.0.97. Approval group users receive emails about tasks needing approval, but they can't access the application when clicking the link. I bypassed this by creating a disabled task with access to a dummy book and granting direct access to the required book. Is this behavior expected, or should the plan automatically grant access to approvers?

Hi Alessandro,

I can confirm you have hit a defect.  The good news is that we have a fix for the upcoming 2.0.98 (or 2.1.5) release of Workspace.  ETA is mid third week of August.   

I appreciate you bringing this issue to our attention.  We will take a look into our QC testcases around this area of the product.   

Hi, Stuart! Thanks for the response.

The application doesn't throw any errors when I refresh the security. I have full control access to the book, and the folders have no permissions blocking access to any groups nor inherit permissions. I don't think any of the problems you mentioned are the case because otherwise, the plan wouldn't grant view-only access to the groups who are collaborators. As I said, when I put the approvers' groups in the "collaborators" section of a task on the same plan, they are granted access to view the plan.

I opened a ticket for this, just wondering if you guys could replicate this behavior.

I will look into this.  My understanding is that any user should have access to the plan if they belong to a group that was added to the task as either an contributor or approver.

When you add a PAW group as a contributor or reviewer the plan does check the permission level of the group to all assets (books and views) used in the task.  If the group does not have at least 'View only 'permissions the plan will try to set 'View only' permissions ('View only' does allow users to interact with the book and enter data).  If the group already has at least 'View only' access then the plan does not change permissions.  However, there are possible reasons why permissions cannot be assigned to an asset in the task.  For example, the folder containing the books has permissions set to prevent access and the asset has the inherit permissions from parent folder option enabled.  The plan will typically throw a warning in this case.  Another possible cause if the plan owner not having the permission that is required (Full control) to modify the permissions on the asset used in the task.  Is it possible that either of these explain the problem? 

This might be a good time to open a support case.

Hi, I haven't received any response to this. The problem still persists.

Hi Alessandro,

I am the community manager for Planning Analytics and i'm checking to see if you were able to resolve your issue or obtained a response to your question. If not, I will follow-up on your behalf.

Thanks,

Nick

I created a plan with an approval hierarchy, but users who are only in the approval groups do not have access to the plan. Only the groups in the collaboration section have access. I tested this in versions 2.0.95 and 2.0.97. Approval group users receive emails about tasks needing approval, but they can't access the application when clicking the link. I bypassed this by creating a disabled task with access to a dummy book and granting direct access to the required book. Is this behavior expected, or should the plan automatically grant access to approvers?

Hi Alessandro,

I can confirm you have hit a defect.  The good news is that we have a fix for the upcoming 2.0.98 (or 2.1.5) release of Workspace.  ETA is mid third week of August.   

I appreciate you bringing this issue to our attention.  We will take a look into our QC testcases around this area of the product.   

Hi, Stuart! Thanks for the response.

The application doesn't throw any errors when I refresh the security. I have full control access to the book, and the folders have no permissions blocking access to any groups nor inherit permissions. I don't think any of the problems you mentioned are the case because otherwise, the plan wouldn't grant view-only access to the groups who are collaborators. As I said, when I put the approvers' groups in the "collaborators" section of a task on the same plan, they are granted access to view the plan.

I opened a ticket for this, just wondering if you guys could replicate this behavior.

I will look into this.  My understanding is that any user should have access to the plan if they belong to a group that was added to the task as either an contributor or approver.

When you add a PAW group as a contributor or reviewer the plan does check the permission level of the group to all assets (books and views) used in the task.  If the group does not have at least 'View only 'permissions the plan will try to set 'View only' permissions ('View only' does allow users to interact with the book and enter data).  If the group already has at least 'View only' access then the plan does not change permissions.  However, there are possible reasons why permissions cannot be assigned to an asset in the task.  For example, the folder containing the books has permissions set to prevent access and the asset has the inherit permissions from parent folder option enabled.  The plan will typically throw a warning in this case.  Another possible cause if the plan owner not having the permission that is required (Full control) to modify the permissions on the asset used in the task.  Is it possible that either of these explain the problem? 

This might be a good time to open a support case.

------------------------------
Stuart King
Product Manager
IBM Planning Analytics

Original Message:
Sent: Thu August 01, 2024 11:49 AM
From: Alessandro Lucas Lima
Subject: PAW Plans - Approval groups

Hi, I haven't received any response to this. The problem still persists.

Hi Alessandro,

I am the community manager for Planning Analytics and i'm checking to see if you were able to resolve your issue or obtained a response to your question. If not, I will follow-up on your behalf.

Thanks,

Nick

I created a plan with an approval hierarchy, but users who are only in the approval groups do not have access to the plan. Only the groups in the collaboration section have access. I tested this in versions 2.0.95 and 2.0.97. Approval group users receive emails about tasks needing approval, but they can't access the application when clicking the link. I bypassed this by creating a disabled task with access to a dummy book and granting direct access to the required book. Is this behavior expected, or should the plan automatically grant access to approvers?