Hi,

I've answered the questions, but there are some assumptions made around current functionality being correct which I think need a bit more exploring. Firstly, the "Job assignment-based instances" feature really needs to lead to assignment per-job rather than per-person, because some activities will be suitable for one role but not for another. At the moment, if I assign an activity to somebody, I'm doing it for all Job assignments which is fine for some things (universal activities) but not for others (activities related to a specific job responsibility or area of work). This would need a little bit of thinking about in terms of being able to re-attach activities where a job assignment is accidentally deleted and then recreated, but that doesn't feel too tricky from an administrative perspective.

Secondly, where a manager changes, there is already functionality to identify who input something (because you have multiple manager instances), but there really should be further options to control how closed instances are handled (visible to others holding the same relationship, deleted if there is no data present, etc.).

Finally, I think this links into a bigger question around how job assignments are handled (which I've submitted an "Idea" for), because at the moment things like audiences are groupings of users rather than job assignments and some of the above might necessitate some new way to capture groups of job assignments.