# Sharing Gateways

### Overview&#x20;

Keeper Gateways are essential when configuring PAM features such as rotation and connections on PAM resources. Keeper provides KSM Application Sharing from the vault UI and Keeper Commander CLI.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FPhW2rAIIL5ohznpVLT9e%2FScreenshot%202025-07-07%20at%203.32.04%E2%80%AFPM.png?alt=media&#x26;token=8e415562-460a-408f-993f-1dbcfd0b0f3b" alt=""><figcaption></figcaption></figure>

### **Why is Gateway Sharing Needed?**

Gateways are tied to Keeper Secrets Manager (KSM) applications. Only users who have access to a KSM application can view and select its associated Gateway when configuring PAM Record Types. Without sharing, only the owner of the KSM application can use the Gateway for PAM configuration.

Sharing the KSM application (and thus the Gateway) allows other administrators or team members to independently configure and manage PAM resources. This is critical when multiple users in your organization are responsible for managing privileged access.

> **Note:** Gateways are automatically shared when the associated KSM application is shared.

### Sharing KSM applications

When you share the KSM application, you also share access to the associated Gateway.

To share the KSM application:

1. From the vault, open the KSM Application you want to share
2. Edit the Application
3. Navigate to the "Users" tab&#x20;
4. In the search bar, enter the user’s email address
5. Add the user to the application.

For more information, visit this [page](https://docs.keeper.io/en/keeperpam/secrets-manager/about/sharing-secrets-manager-applications).

### User Permissions

When sharing a KSM application with other users, the following permissions can be assigned:

<table><thead><tr><th width="187.421875">Permission</th><th>Description</th></tr></thead><tbody><tr><td>Member</td><td>Can <strong>view</strong> the application and use the <strong>gateways</strong> associated with the application </td></tr></tbody></table>

### Sharing Implications&#x20;

#### Shared Folders&#x20;

Shared folders assigned to a KSM application are accessible by the devices and gateways associated with the application. When sharing a KSM application with another user, if the user does not already have access to the shared folders associated with the application, those folders **will be automatically shared** with the user.

The level of access the user receives to these shared folders depends on their assigned role in the application:

* If the user is added as a "Member":
  * The user receives the "No User Permissions" shared folder permissions

If the user already had access to any of the shared folders before being added to the KSM application, their existing folder permissions remain unchanged and are not overwritten.

#### Records&#x20;

Records can be directly assigned to a KSM application via Keeper Commander `secrets-manager app share` command.

When sharing a KSM application with another user, if the user does not already have access to the records associated with the application, those records **will be automatically shared** with the user. The level of access the user receives to these records is "View Only".&#x20;

**Note**: Adding individual records to a KSM application requires using Keeper Commander. &#x20;

### **Removing a user from the KSM application**&#x20;

Removing a user from the KSM application does not revoke their permissions from the shared folders. Folder access must be manually removed if desired.

### Outcomes

Once the gateway is shared through the KSM application, users who now have access can configure PAM resources using that gateway.
