Issue
- What to do before migration
- What happens during migration
- Managing access rights after migration
- Summary
Details
When your account is migrated from ESET Business Account and/or ESET MSP Administrator to ESET PROTECT Hub, some users may receive reduced permissions if their current access rights are inconsistent across portals.
This does not block migration. However, some users may lose access to areas they could previously use.
This article explains what to review before migration and how to correct user permissions after migration if needed.
Solution
What to do before migration
We recommend that superusers and users with Write access review existing user accounts before migration. Users with Read access cannot change permissions.
Focus on users whose permissions differ between:
- ESET Business Account and/or ESET MSP Administrator
- and ESET PROTECT / ESET Inspect
If conflicting permissions exist, the migration applies the most restrictive access level.
Pay special attention to users who:
- Manage customers or sites
- Use multiple ESET cloud environments
- Need Write access for daily tasks
What happens during migration
During migration to ESET PROTECT Hub:
- Existing users are migrated
- Their access rights are compared across connected systems
- If permissions conflict, the lowest permission level is applied
- Access scope (organization-wide vs. limited to specific sites or managed units) is preserved but not expanded
This approach ensures that users do not receive broader access than they previously had.
Managing access rights after migration
Although the migration is performed by ESET, organizations retain full control over access configuration after migration.
Summary
- ESET performs the migration of all users from ESET Business Account and ESET MSP Administrator to ESET PROTECT Hub.
- Some access rights may change as part of security‑driven standardization.
- Permissions in ESET PROTECT and ESET Inspect may be reduced where inconsistencies previously existed.
- Access to ESET Cloud Office Security is preserved and is not affected by ESET PROTECT or ESET Inspect changes.
- Users with appropriate permissions can review and adjust access after migration in ESET PROTECT Hub.
Permission changes after automatic migration of access rights:
| Console |
ESET Business Account/ESET MSP Administrator
|
ESET PROTECT Hub | ||||
| Use case |
Access rights
|
ESET PROTECT/ESET Inspect
|
ESET Cloud Office Security
|
Access rights – after migration | ESET PROTECT/ESET Inspect | ESET Cloud Office Security |
| ESET Business Account/ESET MSP Administrator access is broader than ESET PROTECT/ESET INSPECT access | Write | Read | Access | Read | Access (Read) | Access |
| Write | Read | No access | Read | Access (Read) | No access | |
| ESET Business Account/ESET MSP Administrator access is more limited than ESET PROTECT/ESET INSPECT access | Read | Write | Access | Read | Access (Read) | Access |
| Read | Write | No access | Read | Access (Read) | No access | |
| ESET Business Account/ESET MSP Administrator access is set to No access, with elevated access for some customers with Write/Read ESET PROTECT/ESET INSPECT access | No company-level access (Read/Write for selected customer/site only) |
Write | Access | No access to My Company and Read/Write access to selected customer/site | Access (Write) (only selected customer/site) | Access |
| Read | No access to My Company and Read access to selected customer/site | Access (Read) (only selected customer/site) | ||||
| No company-level access (Read/Write for selected customer/site only) |
Write | No access | No access to My Company and Read/Write access to selected customer/site | Access (Write) (only selected customer/site) | No access |
|
| Read | No access to My Company and Read access to selected customer/site | Access (Read) (only selected customer/site) | ||||
| ESET PROTECT/ESET INSPECT access is set to Custom | Read | Custom | Access | Read | Custom | Access |
| Read | Custom | No access | Read | Custom | No access | |
- The green cells indicate scenarios where no changes are made during the automated migration
- The red cells indicate scenarios where the automated migration changes user rights to weaker access levels
