I'm trying to set up a workflow for making specimen requests that requires approval from the study PI. I'm having some trouble getting the permissions the way I want them, and maybe it isn't possible.
First, I have marked a few people as specimen coordinators, because this gives them the permissions to move the request through each stage to a final resolution. However, this also gives them permission to change the requirements, actors, notifications, etc, and I really don't want them to be able to do this - I only want them to be able to work with existing requests. Is there any way around this?
Second, I set up a general requirement for actor "Reviewer". Obviously I defined an actor called "Reviewer", and I made the study PI the only member of the "Reviewer" group. It appears that any specimen coordinator can complete the requirement, even though they are not part of the "Reviewer" group. In addition, any specimen coordinator can move this request to a final state, even if the requirement has not been completed.
I guess I'm a little confused about the purpose of a requirement, if it doesn't actually have to be completed, and if it is completed, it doesn't need to be done by the specified actor. Have I set something up wrong? Or is this really not a process at all, but just supposed to be a guideline for people to follow?
Thanks for any suggestions,
Jen
(using 13.2) |
| |
| Dave Bradlee responded: |
2013-12-02 14:52 |
Hi,
Re your first question about the specimen coordinator role, there's no current way to do what you would like. A role, such as Specimen Coordinator, has a fixed set of permissions associated with it. There is not a way to give a user that role, but subtract from the permission set. There is also not a way to give a user a set of permissions or to create a custom role with the set of permissions you want. You can only give a user one or more of the existing roles for various folders.
Re your second question, we do not enforce the requirements you place on requests. We'll tell you if they are not complete, but not prevent you from moving the request to different states including final states. So, a requirement is essentially a guideline. We do, however, prevent you from changing requirements (e.g. marking them complete) when the request is in a final state, because a final state means that nothing else can change in the request.
Hope that helps.
Thanks.
Dave |
| |
|
|