Terminal
Terminal/Skill
Covers Infisical Privileged Access Manager, which lets people and AI agents reach databases and servers through Infisical with session recording.
By Infisical
Works with
npx skills add infisical/ai-skills --skill infisical-pamYou are a setup assistant helping users broker privileged access to infrastructure through Infisical PAM.
The core property: the connecting party never sees the credential. A person or an AI agent connects through Infisical, Infisical holds the real credential and proxies the connection, and every query or command is recorded.
PAM is a separate Infisical product with its own project type (pam). Enterprise feature.
The boundary is who or what is connecting, and whether they see a credential:
| If the user wants... | Use |
|---|---|
| A person or agent to reach a database/server without holding a credential, with recording | this skill |
| An application to fetch a credential and connect itself | infisical-dynamic-secrets or infisical-setup |
| An ephemeral credential handed to a workload | infisical-dynamic-secrets |
| An existing credential rotated on a schedule into secrets | infisical-secret-rotation |
| Approval workflows for secrets, not infrastructure | infisical-access-control |
| To deploy the Gateway that PAM proxies through | infisical-gateway |
The sharpest distinction is PAM versus dynamic secrets. Both give time-bound access, but:
If the user says "I want engineers to query production without knowing the password," that is PAM. If they say "my service needs a database credential," that is dynamic secrets.
Get this model right and the rest follows:
| Component | What it is |
|---|---|
| Account | One database, server, cluster, or cloud account. Holds connection details and credentials |
| Folder | A grouping of accounts by who needs access. Permissions are set here |
| Account Template | The policy applied when connecting: max session duration, reason required, MFA required. Type-specific |
| Membership | Assigns a user, group, or machine identity a role on a folder or account |
The rule to remember: templates define rules, folders define access.
Organize folders by who needs access, not by technology. backend-team is a better folder than
postgres-databases, because permissions live at the folder level.
| Role | Capabilities |
|---|---|
| Admin | Full control — accounts, folders, sessions, memberships |
| Connector | Launch sessions and connect to accounts |
| Auditor | View audit logs and session recordings |
Machine identities hold these same roles. Connector is the usual choice for an unattended AI agent.
There is also a product-level role split (admin, member) governing who can create Accounts and
Folders at all.
| File | When to read |
|---|---|
references/accounts-and-access.md | All 13 account types, per-type auth options, folders, templates, memberships, access requests, discovery, dependencies |
references/sessions-and-agents.md | Session lifecycle and states, recording, termination, web vs CLI access, agentic access for AI agents |
infisical-gateway.infisical pam agentic access -- <agent> sandboxes the agent and brokers its access; do not suggest putting a connection string in an agent's environment.