Configuration Folders
Prisma Access configuration can be shared across your
entire environment, or you can create configuration that is specific
to a deployment type (mobile users, remote networks, or service
connection sites).
You can apply Prisma Access policy and
configuration settings globally across your entire environment,
or target policy and configuration settings to certain parts of
your organization.
Configuration folders group settings
that should be shared or are specific to deployment types. When
it applies, you’ll see the configuration folder at the top of a
page, and you can toggle between folders.
The configurations defined under a folder is inherited by all
folders nested under that folder hierarchy. For example, you can
configure settings that are common across GlobalProtect, Explicit
Proxy, Remote Networks, and Service Connections under the
Prisma
Access
folder. Similarly, you can configure settings
that are common across GlobalProtect and Explicit Proxy under the Mobile
User Container
and so on.As often as possible, we recommend that
you work in the global configuration that applies across the Prisma
Access service. Only create local configuration to address use cases
that are unique to that part of your organization.
You can also target policy and configuration settings to the
types of deployments where they make sense.
- Mobile UsersSettings apply across all mobile user connection types: GlobalProtect and Explicit Proxy.
- GlobalProtectSettings apply to GlobalProtect users.
- Explicit ProxySettings apply to mobile users with an explicit proxy connection.
- Remote NetworksSettings apply to remote network sites (branch offices, retail locations, etc.).
- Service ConnectionsSettings apply to service connection sites (HQ and data centers).
Depending on the context you’re working in, you might also see
a Location column displayed for rules or profiles. This column indicates
the rule or profile’s configuration folder.
