---
order: 3
summary: Giving a third party access to exactly one application, with an expiry date.
title: Partner access
path: using/partner-access
status: published
---

# Partner access

The common request: a contractor, auditor or integration partner needs one
internal application, and nothing else, for a limited time. This is the case a
VPN handles worst and Proxility handles well.

## The pattern

1. **A realm of their own.** Create `partner-<name>` rather than putting them
   in `prod`. Delegation, logging and teardown all become one object.
2. **Their own connector.** They run it in their network; you never hold their
   credentials and they never hold yours.
3. **One rule, one service, one port.**

```bash
proxility realm create partner-northwind
proxility connector create northwind-dc --realm partner-northwind
proxility policy allow \
  --from prox://acme/partner-northwind/northwind-dc \
  --to reporting.prod.acme \
  --ports 8443 \
  --expires 2027-03-31 \
  --description "Northwind reporting integration, contract ends 31 Mar 2027"
```

## Make it expire

`--expires` is the difference between an access grant and a permanent hole.
Set it to the contract end date. An expired rule stops allowing traffic and
stays visible in policy history, so the next audit can see what was granted and
when it lapsed.

Review what is outstanding:

```bash
proxility policy list --expiring-within 30d
```

## Human access without a connector

For a named individual rather than a partner system, use a ScaiKey-backed
human identity and let them connect from the Proxility client without running
a connector:

```bash
proxility policy allow \
  --from 'prox://acme/partner-northwind/user:auditor@northwind.example' \
  --to reporting.prod.acme \
  --ports 8443 \
  --expires 2026-12-31
```

Their session identity is short-lived and tied to their ScaiKey authentication,
so revoking the person in ScaiKey revokes their Proxility access too.

## Teardown

```bash
proxility realm delete partner-northwind --revoke-connectors
```

This revokes every identity in the realm and removes its rules. The decision
log is retained — you want to be able to answer what they reached, after they
are gone.
