Enterprise - Why there should be only one Enterprise Administrator

Enterprise Administrator

When we release an Enterprise system to a client we set up one Enterprise Administrator login.  The name of this team member in the database is first name 'Enterprise' and last name 'Administrator' and they are given the 'Role' of Enterprise Administrator.

We do not restrict you from creating other team members and giving them a role of Enterprise Administrator.  However we highly recommend you do not do this.  

The reason:  a very common support query is when a team member has been given the 'role' of Enterprise Administrator on their own login and then find they have difficulty viewing certain projects or adding/amending other team members.  The reasons for this are many and could include that they have a different role on one or more of the projects, or that they haven't been given access to all the projects.  To avoid these complications do not give anyone other than the real Enterprise Administrator this role.  If you find yourself in this position please have the real Enterprise Administrator change your role to that of Team Leader or below on all projects.  Then have them make the required change (such as adding the new Team member) for you.

So what is the Enterprise Administrator's role?

The Enterprise Administrator is the highest privilege level in an Enterprise system.  This is an over-arching role and should only be used to perform higher level administrative tasks in the database.  It should NOT be used as a day to day login.  Anyone who has access to the Enterprise Administrator login should also have another login that they use day to day to enter data.

For example if you need to add a stakeholder group or a new Team Member then the Enterprise Administrator login should be used, but then if you want to enter an interaction with a stakeholder you should logout and then log back in with your day to day login to do this.

Enterprise Administrator is the only role that can:

1/  Add Projects or change project names

2/  Add or modify Types (eg stakeholder group names, issue types, event types) 

3/  Add completely new Team Members (however once a Team Member has been added to the system a Team Leader on a Project can add them to their Project)

4/  Import data

5/  Use the various Audit functions

6/  Make Stakeholders and Properties private to a Project 

As these functions are so high level we always recommend there only be one login with this power in the database and that this login be shared between more than one.  This login should be passed on to the next Enterprise Administrator should the existing one leave.

Did you find it helpful? Yes No