---
title: "Configure the User Access Settings for Portal appliances."
slug: "user-access-settings-v6-6"
description: "Manage Client Profiles, configure listening ports, and upload PKCS#12 files for secure HTTPS connections in your Portal."
updated: 2026-02-03T01:47:27Z
published: 2026-02-03T01:47:27Z
canonical: "support.appgate.com/user-access-settings-v6-6"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.appgate.com/llms.txt
> Use this file to discover all available pages before exploring further.

# User Access Settings

The **Portal** needs to know which [Client Profiles](/v1/docs/client-profiles-v6-6) are to be used by Portal users, as unlike the full-client, these cannot be pre-configured.

Complete the following fields to configure the user access settings:

- ***Client Profiles.*** Add one or more Client Profiles for the users to choose when they sign-in.
- ***Client Profiles from External Collectives.*** Adding External Client Profiles allows the Portal to be used in front of several different Collectives.
  - *Client Profiles from External Collectives' URL.* Paste one or more Client Profiles from the Client Connections page of the external Collective.
- ***Listening Ports.*** By default, HTTPS (port 443) is open for incoming traffic. You can add additional ports which will also be proxied.
- ***HTTP Redirect.*** By default, HTTP (port 80) will be redirected to port 443. By disabling HTTP Redirect the Portal will not respond on port 80.

The Portal operates as a reverse proxy when handling user traffic. This means that it must terminate any HTTPS connections, decrypt and then re-establish an onward HTTPS connection to the protected hosts. The Portal supports the use of multiple PKCS#12 files containing a certificate signed by a trusted CA (for the protected host) and the private key. An alternative to using multiple certs is a wild-card cert - but this should be limited in scope because of the security implications in the event of its loss.

- ***Proxied Entitlement Certificates - PKCS #12.*** Upload a PKCS #12 file which includes a CA signed wild-card certificate. Individual files can also be used - one for each Entitlement's hostname.
  - *File.* Select the PKCS #12 file to upload.
  - *Password.* The password for the PKCS #12 file.
  - *Verify Upstream.* All upstream servers are checked for valid certificates that match their hostnames by default. See [Adding third party certificates](/v1/docs/adding-3rd-party-certificates-v6-6) for more details