When you create a custom role, you have to give it a unique name so you can tell it apart from other roles. Those role names should be fine as long as they make sense to whoever will be assigning roles to users.
When creating custom roles, you should think about who would be assigned those roles, what work they would be doing, and then what permissions are needed to do that work. Starting with a similar out of the box role and adding or removing permissions is the easiest way to do so.
For example, we have a custom Department Manager role that we use to have these managers do their GIS work and help manage the GIS content their department creates. We started with the out of the box publisher role and enabled some of the content administration permissions, such as creating shared update groups and changing ownership of content.
- Jen
