Global Employees instead of Project Employees
Florian Altmann
The Employee module is project specific, so there is no global list of employees.
The original idea for creating it project specific was, that there are large projects with many subcontractors, and subcontractor employees are usually working for one project. Thus a global list would be bloatet with many subcontractors only working on one site.
Over the years we have received frequent feedback that this is an issue for managing internal employees, who are working on many Insite LMS projects.
Thus the request would be to convert the Project Employees to Global Employees, allowing one central management of employees and it's certificates.
The downside may be, that this is a large list if you are working with many subcontractors.
A Global/Project Employee setup may look similar to Global/Project Tool modules.
Log In
D
Daniele Brandolin
Moving from a Project Employees model to a Global Employees model naturally comes with both advantages and drawbacks, from an operational, governance, and compliance perspective.
For this reason, a possible transitional and balanced approach could be to support both models in parallel, allowing organizations to adopt the most appropriate option depending on the specific context.
More specifically, the proposal could be:
- to introduce Global Employees, managed through a central (global) module, which can be linked and made visible to one or more projects; in this case, employee master data and certifications would not be editable at project level, but only within the Global module, ensuring data consistency, centralized governance, and better control;
- at the same time, to keep the existing Project Employees model, where employees are created, managed, and used exclusively within a single project, exactly as it works today.
This hybrid approach would:
- enable centralized management for internal employees working across multiple projects,
- preserve project-level segregation and simplicity for subcontractor-heavy scenarios,
- reduce the risks associated with a full and immediate shift to a global model,
- allow a gradual evaluation of impacts, including GDPR and data access considerations.
N
Nogueira Itamar
Please check GDPR restrictions in case of a global employee module. This is our concern related to this application. What happens if we have a Global Employee like we have tools ... will it be visible for every one? Robert Resch Florian Altmann
Florian Altmann
Nogueira Itamar If we would go into the direction of global employees, by default all employees would be visible for all users who have access to this global module yes.
It would require custom data restrictions to limit the access.
The same is true for employee certificates, which would also be global and would require custom data restrictions.
We are very aware that this is a critical change and will require a lot more analysis on the possible implications.
M
Markus Scheucher
it´s a yes from my side, would be great to us!
K
Kolb Richard
I would vote ten times for this if it was possible :) Atleast some central management for employee certifications would really improve our workflow
P
Peter Schulze
Thank you, this would help our business a lot and open the door to synchronize HR data automatically between SAP and LMS!