Best practice for new user attributes like department?

Hi all,

for the user there are some custom fileds (1-10). Is it best practice to use them for information like department or cost centre?

Maybe there is another way one of you guys prefer?

Thank you in advance,
Chris

OriginalPostID-260186

  Discussion posts and replies are publicly visible

Parents
  • I would recommend you to list users in groups with these properties rather than saving them as custom properties because there are many advantages with groups.
    Say if you want to pick users of a particular department in particular region/cost center for task assignment
    then if you are having both of them as custom properties you need to search for match within list of almost all users. In the other case you just need get intersection of users in region_group and department_group.
    Not just this, groups will allow you to add user into multiple departments/roles where as custom properties you always need to have one value for costum properties.
    Also Say when one user is moved to other region then moving them in groups will automatically manage their pending tasks and any reassignment is not required.
Reply
  • I would recommend you to list users in groups with these properties rather than saving them as custom properties because there are many advantages with groups.
    Say if you want to pick users of a particular department in particular region/cost center for task assignment
    then if you are having both of them as custom properties you need to search for match within list of almost all users. In the other case you just need get intersection of users in region_group and department_group.
    Not just this, groups will allow you to add user into multiple departments/roles where as custom properties you always need to have one value for costum properties.
    Also Say when one user is moved to other region then moving them in groups will automatically manage their pending tasks and any reassignment is not required.
Children
No Data