Team Member Roles in an Enterprise system
Please see below for further notes on how to use these roles.
The highest level role in an Enterprise system. This is an over-arching role used to perform high-level administrative tasks in the database.
In an Enterprise system the Enterprise Administrator is the only role that can:
1/ Add projects or change project names
2/ Add or modify types (stakeholder group names, issue types, event types) and assign them to Projects.
3/ Add new Team Members (however once a Team Member can be added to the system a Team Leader on a project can assign them to their project)
4/ Import data
5/ Use the audit functions of Consultation Manager
6/ Assign Stakeholders and Properties to Projects
Team Leaders have full responsibility for the Project/s they are assigned to. Team Leaders can manage the Project team on their Projects (once the Enterprise Administrator has created these Team Members). They have full ability to add, delete and modify data in their Project/s.
Can add, delete and modify data in the Project/s they are assigned to.
Can add data and only delete or modify data that they themselves have personally put into a Project/s.
This login is typically given to upper management or those overseeing a Project as it enables them to view all the data and run reports, however they can't enter data into the system or make any changes.
Don't actually have a login to the Project however appear in the team list and can be recorded on events and can have Actions assigned to them.
In addition, as Team Members cannot login, this is the role you set someone to when they leave your team. Changing them to a Team Member keeps their history of interactions in the database but prevents them from accessing the system.
Alternatively, you can view a video on Managing Your Team here.
You can find information on managing your Team in a Project licence in this article here.