Import and Permissions

Import and Permissions

This page explains who can import Power Components Kit (PCK) solutions, what to do when import fails, and how IT can roll out PCK across environments.

Who can import a solution?

To import a solution into a Power Platform environment, you need one of the following:

• System Administrator — Full access to the environment; can import any solution.
• System Customizer — Can customize the environment and import solutions (subject to DLP and tenant settings).
• Environment Maker — In some configurations, can import solutions into environments they create or manage.

Caution

If you see an error like “You don’t have permission to import a solution,” your role in that environment does not include solution import. Ask your Power Platform or Microsoft 365 admin to either grant you a role that can import solutions or to import the PCK solution for you.

For the official list of roles and capabilities, see Microsoft Learn: Environment permissions.

What to do if import fails

Symptom	What to try
”You don’t have permission”	Your account lacks a role that can import solutions. Ask an admin to import the solution or to assign you System Customizer or System Administrator for that environment.
”Solution dependency missing”	The solution depends on another solution or component that isn’t in the environment. Import any required solutions first (PCK solutions are typically self-contained).
”Invalid solution file”	Ensure you’re using the correct .zip from your purchase or download. Don’t rename or edit the contents of the zip.
DLP / policy block	Some tenants block custom connectors or code. PCK components are PCF (Power Component Framework) and don’t use custom connectors; if you still see a policy error, contact your tenant admin.

After a successful import, if you don’t see the component in the Insert → Get more components list, try Publish all customizations from the Solutions area.

For IT: Managed solution and multiple environments

• Managed solution — PCK is delivered as a managed solution. Makers and users cannot change or remove the component definition; they can only use and configure the component in their apps. This supports governance and consistent upgrades.
• Deploying to more environments — To use PCK in another environment (e.g. Production), import the same PCK solution .zip into that environment. Repeat for each environment where you want the components available. There is no automatic propagation between environments.
• Updates — When a new version of a PCK component is released, you receive an updated solution package. Import the new version into each environment (or use your usual solution upgrade process) and then Publish all customizations so apps use the updated component.