Security Access

Hi Chris, I have a spreadsheet which lists security for each of our groups across the organisation. Not a perfect document but may help. I'll email it to you. Justin

One of the interesting questions for me is what groups have you used.  I could imagine a long-ish list of groups. Like:

• System Administrators
• Basic Development / Membership
• Power User Development / Membership
• Basic Contribution Entry 
• Power Users Contribution Entry
• Major Gift Office and Execs
• Basic Marketing
• Power User Marketing
• Basic Box Office / Visitor Services
• Power User Box Office  / Visitor Services
• Phone Room Staff
• Web Site
• Basic Education
• Power Users Education
• Basic Finance 
• Power Users Finance
• Specialty groups for targeted processes like
  • NOCA
  • Order Export-Import
  • Manage Attributes & Constituencies
  • Membership Update Utility
  • HMH Culture Segments
  • Wordfly or Mail2 or __________

Interns might be their own group or the Basics of their division.

However, I'm aware that some organizations may have very few groups, defaulting to a "limited access group." and an almost system supervisor like access.

And this is not considering the complexities of the world of consortiums, where each of these groups has to be recreated for every organization.

One of the challenges that I have found with Tessitura Security is that it does not work in an additive way.  A user group has to have defined for it all of the acces that are available for that user.  You can't give a login the sum of multiple groups.

I've often run into situations where a user for one reason or another works in a cross-functional way.  Maybe regularly does Education Setup and Contribution entry.  With a setup like the above you either have to ask the user to log out and back in, which can be a real main for the user.  Or you find youself creating these groups with just one user.  

One of the interesting questions for me is what groups have you used.  I could imagine a long-ish list of groups. Like:

• System Administrators
• Basic Development / Membership
• Power User Development / Membership
• Basic Contribution Entry 
• Power Users Contribution Entry
• Major Gift Office and Execs
• Basic Marketing
• Power User Marketing
• Basic Box Office / Visitor Services
• Power User Box Office  / Visitor Services
• Phone Room Staff
• Web Site
• Basic Education
• Power Users Education
• Basic Finance 
• Power Users Finance
• Specialty groups for targeted processes like
  • NOCA
  • Order Export-Import
  • Manage Attributes & Constituencies
  • Membership Update Utility
  • HMH Culture Segments
  • Wordfly or Mail2 or __________

Interns might be their own group or the Basics of their division.

However, I'm aware that some organizations may have very few groups, defaulting to a "limited access group." and an almost system supervisor like access.

And this is not considering the complexities of the world of consortiums, where each of these groups has to be recreated for every organization.

One of the challenges that I have found with Tessitura Security is that it does not work in an additive way.  A user group has to have defined for it all of the acces that are available for that user.  You can't give a login the sum of multiple groups.

I've often run into situations where a user for one reason or another works in a cross-functional way.  Maybe regularly does Education Setup and Contribution entry.  With a setup like the above you either have to ask the user to log out and back in, which can be a real main for the user.  Or you find youself creating these groups with just one user.