Manage Roles
In PlanTeam-SPACE, the rights to execute specific functions are controlled via roles. Therefore, what a particular member is allowed or not allowed to do in a project depends on the role assigned to them. Furthermore, the roles describe the tasks that the respective person undertakes in the web space or project.
Roles are distinguished as being outside (cross-project) and inside the project. The roles within the project can differ for a person from project to project. The role outside the project provides a template for the role that the person assumes as a member in a project. Of course, it can be changed there again.
Via PlanTeam-SPACE, it is possible to set roles for individual members.
The following roles are available:
| Administrator | The Administrator has the right to configure organization settings. Thus, the administrator can create and remove organizations and departments. The Administrator assigns persons with their identifiers to their departments and assigns roles for the persons. |
| Project Manager | The role of the Project Manager includes setting up new projects with groups and members and the associated rights for the project documentation. The Project Manager always has access to all projects, without necessarily being a project member themselves. With the creation of a project, the Project Manager is initially created as a member with the role of Project Lead. After another project member has been appointed as Project Lead, the Project Manager can remove themselves from the project. |
| PTS Project Lead | The role PTS Project Lead enables the administration of the project itself (e.g., adjusting properties) and the project participants (e.g., assignment of roles), as well as read-only access to the communication journals and the complete documentation, regardless of the access rights set there. Write access corresponds to that of an Editor. |
| Document Manager | The Document Manager is responsible for documentation in a project and always has read and write access to the complete documentation. He thus has the possibility to make further adjustments to the documentation, such as creating, changing, and deleting folders or directories, as well as deleting other users' documents - even from the recycle bin. Templates for project documentation are exclusively managed by Document Manager. |
| Communication Manager | The Role Communication Manager enables reading and deletion of all input and output journals (received and sent emails) in the project, creation and customization of distribution templates, as well as management or cancellation of active subscriptions for all participants. |
| Organizer Manager | The Role Organizer Manager allows full access to all tasks and appointments in the project organizer. These can be edited or deleted; depending on the project configuration, creating new tasks and appointments may also be reserved for the organizer manager. |
| BIM Manager | The BIM Manager is responsible for managing the BIM component. He is able to change the attributes of all BCF topics as well as set their status. The BIM Manager can also define presets for tree and color display in the BIM Viewer. |
| Area Manager | The Area Manager is responsible for the FM view. It sets up new properties and can, for example, create or import rooms. |
| Inventory Manager | The Inventory Manager is responsible for inventory management. He can create or import new inventory. |
| Component Manager | The Component Manager creates components, imports them from Excel, and manages them. |
| Plant Managers | The Facility Manager records technical facilities and manages them. |
| Cost Manager | The Cost Manager is responsible for cost management. He records and processes costs and consumptions. |
| Defect Manager | The Defect Manager manages defects recorded for building components. |
| Incident Manager | The Incident Manager manages incidents recorded for technical facilities. |
| Workflow Manager | The Workflow Manager manages workflows and their templates. |
| Log Manager | The Log Manager has access to all entries of the event log. |
| Editor | The Editor is the "normal" user of the project. He can view the parts of the documentation released for him and store documents in them, download them, send them or distribute them. The Editor can also create tasks and appointments. All administrative roles (e.g., Area Manager, Exchange Manager, etc.) have, in addition to their own rights, simultaneously the rights of the role of the Editor. |
| Observer | The Observer is exclusively authorized to view the project structure and planning documents. He may not make any additions or changes to the project. |