> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/upgrade-from-prisma-cloud-to-cortex-cloud/copy-content/copy-global-configurations.md).

# Copy Global configurations

### Roles and user groups

When you copy **Roles and User Groups** in the Upgrade Helper, the Prisma Cloud Custom Permission Groups and Roles are copied to Cortex Cloud as corresponding roles and user groups.

#### Assign roles and user groups

Users created through the customer support portal are assigned to the relevant user groups. If your organization uses single sign-on (SSO) for authentication, user roles and groups won't be assigned based on Prisma Cloud mappings. In this case, you will need to handle role assignment by SAML group mapping. Learn more about [authenticating users](/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/set-up-authentication.md).

#### Verify copied roles and user groups

After you follow the steps listed in **Copy configurations**, navigate to Settings → Configurations → Access Management to view the copied items.

{% hint style="info" %}

### Note

Keep the following caveats in mind:

* Scope-Based Access Control (SBAC) configurations, such as resources or account lists are not copied. You can manually assign scope-based access to the relevant users or groups.
* When migrating permission groups and roles, the total count of items successfully copied may be lower than the initial number selected. This is expected behavior. The discrepancy in counts can occur for the following reasons:

  **Default Entities**: System-default items that are already mapped in the Cortex environment are automatically excluded from the operation, as migration is not required. The initial total count shown for processing will reflect this exclusion.

  **Validation Failures**: Entities that fail validation checks, such as those with duplicate names, will be skipped and not copied.

  **Empty Mappings**: Items that result in an empty configuration after the permission mapping process (e.g., a group that contains no valid permissions in the target system) will be skipped, as no corresponding entity can be created.

  Reference the migration logs for specific details on any skipped entities.
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/upgrade-from-prisma-cloud-to-cortex-cloud/copy-content/copy-global-configurations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.