[Progic] Employee Field Protection
Gain greater control over employee data while maintaining the flexibility of integrations and the security of protecting strategic information when necessary.
- What is Field Protection?
- How to Enable Protection for a Field
- Which Fields Can Be Protected?
- What Happens During an Import?
- What Happens with API Integrations?
- How to Identify Protected Fields During an Import
- Frequently Asked Questions
- Benefits of Field Protection
What is Field Protection?
Field Protection allows you to define which employee information cannot be automatically modified through spreadsheet imports or API integrations.
This feature is useful when certain data is managed manually and should not be overwritten by external systems.
Example
Imagine that HR manually updated an employee's email address in Manager DS.
Later, an integration with the HR system sends the old email address again.
Without Field Protection enabled, the updated value would be replaced.
With Field Protection enabled, Manager DS keeps the manually defined value and ignores the update received through the integration.
When Should You Use Field Protection?
We recommend using this feature when specific information must remain exactly as it was defined in Manager DS.
Some common examples include:
- Social name manually adjusted.
- Corporate email managed internally.
- Job title or department used for specific segmentations.
- Employee ID number or identifiers controlled by the platform administrator.
- Segmentation lists managed directly in Manager DS.
How to Enable Protection for a Field
- Go to Employees.
- Locate and edit the desired employee.
- Identify the field you want to protect.
- Enable the 🔒 Protect Field option.
- Save your changes.
Once enabled, the field will remain protected against future automatic updates.
Important: Administrators can still edit the field normally through the Manager DS interface.
Which Fields Can Be Protected?
Protection can be applied to various employee data fields, including:
- First Name and Last Name
- Social Name and Social Last Name
- Alias
- Phone Number
- Work Email
- Personal Email
- Unit
- Department
- Job Title
- Employee ID
- Date of Birth
- Hire Date
- Vacation Period
- Sex
- Gender
- Nationality
- Birthday Settings
- Ranking Settings
- Segmentation Lists
- External ID
- Company Code
- Windows Domain
What Happens During an Import?
When a spreadsheet attempts to update a protected field, Manager DS ignores only that specific field.
All other employee information continues to be processed normally.
Example
Current Value in Manager DS
| Field | Value |
|---|---|
| joao.silva@company.com |
Value Sent in the Spreadsheet
| Field | Value |
|---|---|
| joao@company.com |
Result
Since the Email field is protected:
✅ The employee is processed normally.
✅ The protected value is preserved.
✅ Only the email update is ignored.
What Happens with API Integrations?
The behavior is similar to spreadsheet imports.
When a protected field receives an automatic update through an integration, the system keeps the existing value and ignores the incoming change.
This ensures that manually configured information is not overwritten by automated processes.
How to Identify Protected Fields During an Import
When an import encounters protected fields, the system displays a warning indicating which information was not updated.
Example
Protected fields were ignored during the import: First Name and Last Name, Email.
This message helps administrators understand which information remained unchanged during processing.
Frequently Asked Questions
Does Field Protection Prevent Administrators from Making Changes?
No.
Field Protection only affects spreadsheet imports and API integrations.
Administrators can continue editing data normally through the interface.
Does the Import Fail When It Encounters a Protected Field?
No.
The employee record is still processed normally.
Only the protected field is not updated.
Can I Protect More Than One Field at the Same Time?
Yes.
You can enable protection for as many fields as needed.
Does the Protection Apply to Future Imports?
Yes.
Once enabled, the protection remains active until it is manually removed.
Benefits of Field Protection
✅ Prevents unwanted overwrites caused by integrations or imports.
✅ Preserves manual changes.
✅ Reduces inconsistencies between systems.
✅ Provides greater control over critical employee data.
✅ Improves the security and governance of employee records.