FAQ & troubleshooting

Common questions about how packshell behaves and how to fix the usual snags.

Can the packshell team read my secrets?

No. Your .env is encrypted on your machine before upload, and the project key needed to decrypt it is never sent to the server in the clear. The server stores cipher blobs and wrapped keys it cannot open. See the security model.

Why are push, pull, and share only in the CLI?

They require the project key, which lives on your machine. Doing them in the browser would mean handing the key to a server — exactly what packshell is designed to avoid. The dashboard handles everything that doesn't touch the key: members, invites, plans, version metadata, and audit history.

I switched machines and can't decrypt. What now?

Decryption needs your private key. If you authenticate on a new machine, a teammate re-shares the project key to your new public key with packshell share, after which you can pull normally.

How do I move a company to a paid plan?

Redeem a plan code as a company admin — from the dashboard Billing page or the CLI:

$ packshell redeem PSHL-TEAM-7K2M-9XQ4

“Admin access required” when loading audit logs

Audit logs are visible to company admins on the Team plan or higher. If you're a member, ask an admin; if your plan is below Team, upgrade from the Billing page. See plans & limits.

How do I point the CLI at a self-hosted server?

$ export PACKSHELL_API_URL="https://packshell.your-company.com"$ packshell auth

How do I become a platform super admin?

Super-admin access is granted out-of-band by an operator (it is not self-serve). Once granted, the Super Admin link appears in the dashboard sidebar and the packshell superadmin commands become available.