Access rights and planned dates storage into requested/validated dates

Hello

I am working on planification of activities for project schedule.
I think I start to understand how it works and how to use it.
But I have noticed something which looks quite strange to me:

When a profile has rights to compute the planning, but no rights to modify existing activities (in my case: he can create and update his own activities, but not the others, and he has rights to compute the planning to have a gantt view), everything goes well.
If his activities have an impact on planning, delayed activities appears in red in gantt view.

But, he also has rights to store planned dates to requested/validated dates, and by this way he can modify elements of activities on which he has no rights.
For me, it is a problem, because the planning is delayed and there is no backup on initial requested/validated dates.
I think he should not be able to change requested/validated dates on activities he cannot update.

Do you think this behaviour is normal, or is it a bug or something in access rights?

Thank you very much.

Jean-François.

Hi Babynus,

Thanks for your answer.

I understand this use case was not planned. In fact, it seems strange to me also.
But I see no alternative when a profile has rights to create and update his own elements.
The solution should be to forbid planning computation to this profile, but this is not satisfactory because his own activities will not be planned...

I agree with your remark: in fact, this profile should have no right to update planned dates on "read only" activities. But it works...

The aim of this configuration was to limit the number of activities created by project manager to macro-activities.
Then, members has rights to create sub-activities for each macro-activity for their own convenience.
Do you have an idea of a possible way to do this?

Jean-François