Discuss Configuration & User Management Tips / Best Practices

We know that effectively configuring elluminate will make a big difference in the daily tasks of users. That’s why we’d love to hear your tips, tricks, and techniques for Platform Configuration, Study Configuration, Module Specific Configuration, User Management, eForms, eDrive, Orchestrator, Global and Study Data Stores, etc! Whether you’ve discovered shortcuts, best practices, or innovative ways to configure our software appropriately for your workflow, your insights can help others enhance their experience.

Let’s build a resourceful community where we can all learn from each other. Please share your advice in the comments below!

Best Practice for User Management using Groups for Roles and Units:

To support ease of long-term maintenance, I highly recommend the following guidelines for defining elluminate Groups. Use one set of groups to define Roles and another set of groups to define organizational Units. Then individual users are managed by assigning them one or more roles as well as one or more units. The key to making this work is to only assign the View privilege and only the View privilege for Units, and all other privileges only for Roles. For the study level privileges within a Role definition, grant them access to ALL studies. The key here is that while this allows that privilege to be applied to any study, the ability to see any study is constrained by the View privilege which is set in the Unit group. When assigning the View privilege for a given Unit, the selection of studies associated with that Unit controls what studies any user assigned to that Unit can see.

Roles manage privilege assignments

Units manage granting study access

Adopt a naming convention using a prefix to distinguish roles from units as illustrated in the following table:

Prefix |

Category |

Example |

Assignment Notes

R_ |

Role |

R_DM |

Assign privileges, but NOT the View privilege. For study level privileges, grant access to All studies.

U_ |

Unit |

U_CNS |

Assign only the View privilege, and for it the associated set of studies for that organizational unit.

Now when a user is created, simply grant them the appropriate group(s), defined by the role(s) and unit(s), that they should have access to.

Notes:

The Unit's "View" privilege setting controls which studies the user can see and work with, so stating an individual privilege applies to All studies at the Role level will be constrained by the View setting at the Unit level.

Privileges are additive, so if a user is granted 2 or more Roles, they get all the privileges from both sets of Role definitions. Same holds true for the Unit assignments controlling what studies they can see and work with.

Because privilege assignments are additive, any special individual user requirements can be managed by simply granting additional privileges and/or study view permissions (above and beyond the group assignments) at the individual user level.

Discuss Configuration & User Management Tips / Best Practices

Comments

Best Practice for User Management using Groups for Roles and Units:

Was this article helpful?