I'm trying to create a profile for an external worker, which should:
- see projects in which is working
- see/manage only activities which he is assigned to
- be forbidden any activity in which he is not working
So I've modified the external worker profile, but I have problems because:
- This person is assigned an activity, but he is not responsable not creator of the task
- He cannot see any activity assigned to him, unless I set him as responsable
I lack a unique permission like dealing with affected elements: elements for which is responsable, or assigned to, or creator of.
In this case he should have, on activities:
- reading: affected elements
- update: affected elements (or none)
- creation: none
- deletion: none
How can I manage this situation? He should not be able to create any activity, but only be assigned an activity, and should see and/or manage only assigned activities.
The ideal should be to allow him to change only secondary attributes, i.e. even if responsable he should not be able to change title, responsable and other fundamental datas of the activities.
Did I miss something in profile/permissions creation, or is it something to be evaluated for tufure?
Regards,
Tonino
what you try to do oes not exist.
and is not planned in the roadmap.
It would semplify a lot external resource management.
In next future I'd love to work by myself for a solution (to share, eventually).
Do you see this change troublesome, or with a good analisys it could be done without too much stress?
Thanks,
Tonino
will not be easy to implement. 🙁
really not :S
and very restrictive as it will only concern access rights to activities.
It should be applied to any element which is assigned to, responsable of, created by, and then usable for activities, tickets, questions, and so on.
When I'll have more time I'll give a try, and ask here more infos (don't worry, I need some months before I can do 🙂 )..
Today I met an external worker. He needs to see only a couple of activities, which I created and assigned to him, but I was forced to let him see all activities, which makes his interaction with projeqtor more difficult. Specially with people which works seldom with me, it would be better to give them only the limited view of "their" activities, so their learning path with the application will be a lot more easy.
Regards,
Tonino
Best way is to give visibility to activities "he is responsible of" and set him as responsible.
He several users have such need on same activity, maybe it means the activity should be split into several ones.
It's an idea, but responsable can do changes an external person should not be allowed to do.
I will explore later what's possible to do, and if there are less troublesome ways.
For example, it would be useful a filter on display for "affected elements", but I feel it would need anyway a core filtering rule.
but responsable can do changes
No this is not mandatory.
All depends on how you configure your access rights.
It is correct a responsable can make changes, I would like to avoid changing responsable permission only for limiting an external resource.
I'll experiment more on rules possibility, and will think about.
Thanks.