# pandadoc document link 403 error expired: how to fix it

A PandaDoc document link 403 usually means the link expired or the document was moved, not that you did something wrong. Ask the sender to generate a fresh link. If you are the sender, check the link expiry settings and re-send, since expired links never come back to life on their own.

```text
pandadoc document link 403 error expired
```

## When to use this skill
- A PandaDoc share link returns 403
- The link worked before and now fails

## When not to use this skill
- The document opens but signing fails (a signing issue)
- You get a login prompt instead (an account issue)

## Tool compatibility
PandaDoc document sharing links. Current web app.
Related area: business SaaS platforms and vendor portals.
Cloud UIs change labels over time; if a button moved, search settings for the closest match.

## Before you start
- Sign in to the tool and keep one tab open so sessions stay clean
- Copy the exact error text and note the time it happened
- Set aside 15 to 20 minutes; most of these resolve in a single pass

## Quick diagnosis
Make sure this is the right skill before you invest the 15 minutes.
- If you are dealing with a PandaDoc share link returns 403, start at step 1 below.
- If instead the document opens but signing fails (a signing issue), stop here; you need a different skill.
- If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

## Fix it in steps
### 1. Try the link in a private window

```
Open the link in a private or incognito window.
```
Expected: still 403 means the link itself is dead, not your session.

### 2. Ask the sender for a fresh link

```
Reply to the sender noting the link expired and ask for a new one.
```
Expected: a new link arrives.

### 3. If you are the sender, check expiry settings

```
Open the document share settings and look at the link expiration.
```
Expected: an expiry date in the past explains the 403.

### 4. Generate and send a new link

```
Create a fresh share link with a longer expiry and send it.
```
Expected: the recipient opens the document successfully.

## Confirm each step worked
Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.
- Step 1 (try the link in a private window): Expected: still 403 means the link itself is dead, not your session.
- Step 2 (ask the sender for a fresh link): Expected: a new link arrives.
- Step 3 (if you are the sender, check expiry settings): Expected: an expiry date in the past explains the 403.
- Step 4 (generate and send a new link): Expected: the recipient opens the document successfully.

## Quick recap
1. Try the link in a private window
2. Ask the sender for a fresh link
3. If you are the sender, check expiry settings
4. Generate and send a new link

## Still stuck?
Gather three things: the exact error text, the time it happened, and what changed just before it broke.
Check the vendor status page for an active incident. Then open a support ticket with those three things;
it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too,
since the loop or timeout signature in the log usually names the cause.

## Variant phrasings
### pandadoc link expired 403
Expired links stay dead, only a fresh link fixes it. If this matches what you saw, the steps above apply as written.

### document link forbidden pandadoc
Private window test separates a dead link from a bad session. If this matches what you saw, the steps above apply as written.

## Why it happens
PandaDoc share links carry an expiry and are tied to the document state. When the link expires or the document is archived or moved, the server returns 403 instead of a friendly expired message.

## Edge cases
- Some links are single-use, opening twice can kill them
- Archiving the document invalidates all its links
- Set expiries generously for slow-moving signers

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_KtLG-ajAeg0J_nhqWnfI_Q