Skip to main content

Work with personnel managed by an external HR system

Some organisations use an external HR system as the source of truth for personnel and organisation data. When this is enabled, People shows a Managed by external HR system notice and protects synchronized data from being changed in Markular.

This prevents a correction made in Markular from being overwritten by the next HR synchronization, and keeps both systems consistent.

What is managed by the HR system​

The external HR system controls core personnel and organisation data, including:

  • names, birth date, sex, primary email, work and personal phone numbers;
  • employee, ERP, JDE and user-principal-name identifiers;
  • hire date, employee type, country and employment lifecycle;
  • emergency contacts, position assignments and position history;
  • positions, reporting lines and departments.

People created by the integration must also be created or removed in the HR system. Manual person creation, deletion and batch import are unavailable while external HR master data is enabled.

What you can still do in Markular​

You can still view, search, filter and export personnel data. Depending on your permissions, you can also manage information that is not owned by the HR integration, including competencies and their attachments, documents, issued documents, profile pictures and other fields that are not shown as locked.

People administrators can continue to assign Markular access roles and country restrictions. The person's synchronized identity, email and employment status must still be corrected in the HR system.

Change a synchronized value​

  1. Open the person's profile or the relevant organisation page in People.
  2. Look for the Managed by external HR system notice or a locked field.
  3. Make the correction in your organisation's HR system, not in Markular.
  4. Allow the normal synchronization to run, then refresh People and confirm the value.
  5. If the value does not arrive, contact the person responsible for your HR integration and include the person's name, the field and when it was changed.

Do not work around a locked value by creating a second person. That produces duplicate records and separates competencies, documents and planning history from the authoritative person.