Permissions Required for the Migrate Functionality in SnapLogic
Based on the search results, here is a clear breakdown of the permissions needed to use the migrate functionality in SnapLogic:
---
🔐 Required Permissions
To migrate a SnapLogic project from one Environment/Org to another, you need two distinct permissions:
| Scope | Required Permission |
|---|---|
| Source Project | Read access |
| Target Environment/Org | Write access |
---
📋 Permission Details
SnapLogic projects support the following permission levels, which map to the above requirements:
| Permission Level | Read | Write | Execute |
|---|---|---|---|
| Read Only | ✅ | ❌ | ❌ |
| Read & Write | ✅ | ✅ | ❌ |
| Read & Execute | ✅ | ❌ | ✅ |
| Full Access | ✅ | ✅ | ✅ |
| Owner | ✅ | ✅ | ✅ |
So for migration:
- On the source project: At minimum Read Only (or higher) permission is sufficient.
- On the target Environment/Org: At minimum Read & Write (or higher) permission is required.
---
⚠️ Additional Considerations
If you are migrating Accounts or Policies across different Environments/Orgs, there are extra requirements:
1. The source Environment/Org must recognize the destination Environment/Org as a Trusted Environment/Org.
2. The destination Environment/Org must have at least the same security level as the source.
---
👤 Who Can Assign Permissions?
- Org Admins can assign permissions to any user or group across any project or project space.
- Project Owners can assign permissions to users or groups within their own projects.
---
💡 Tip: If you are an Org Admin, you can also set permissions at the Project Space level and propagate them to all child projects at once, which simplifies permission management across large environments.
