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

# Password Link API

> Send passwords and other secrets to your clients' end users as Password Link secret links, check that they were opened, and ask end users for secrets

The common use is a password reset or a new user. The agent makes the password, sets it with its Microsoft 365 or Active Directory tools, shares it as a Password Link secret link, sends the link to the end user, and later checks that the link was opened.

<Info>
  Automatically enabled when you configure Password Link permissions in your agent workflow.
</Info>

## What it does

* Share a secret as a secret link that stops working at its view limit or expiry. Neo encrypts the secret and returns the link, with the expiry, view limit, one-time code, second password, IP or country limits your instructions ask for
* Attach a file to a link, encrypted the same way (a paid Password Link plan)
* List links with how many times and when each was opened
* Change a link's settings, or delete it to revoke it
* Create, rename and delete folders, and file links in them
* Send an end user a secret request by email or text, so they can send a secret back as a secret link, and list or withdraw requests

## Permission groups

| Group | Covers |
| - | - |
| Secrets & Folders | Secret links and the folders that file them: list them with when each was opened, create, change and delete a link, and create, rename and delete folders |
| Secret Requests | Links that let an end user send you a secret: list, create and delete them |

| Profile | What it does |
| - | - |
| Read Only | Reads both groups, changes nothing |
| Helpdesk | Sends, changes and revokes links on its own. A secret request asks a technician first |
| IT Admin | Sends links and secret requests, and manages links and folders, on its own |
| Full Automation | Makes every change on its own |

## Safety Controls

* Neo never opens a Password Link secret. Opening one through the API deletes it, so the link the end user holds would stop working. To see whether a link was opened, the agent reads the list.
* The agent sends the secret's text in a field Neo masks in run history and in test-mode reports.
* Neo makes the encryption key itself. Password Link receives the half of the key that opens the secret only when an agent asks Password Link to email the link.
* A file upload runs inside link creation. If the file does not upload, Neo deletes the new link, so no link to a secret without its file is sent.

## Setup

See [Connecting Password Link to Neo](/integrations/password-link/connecting-to-neo).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.