Security & governancePractical controls around shared prompt work

Protect accounts, workspace boundaries, and machine access

Prompt Manager combines account security, workspace authorization, scoped API keys, request protections, webhook safeguards, and audit records. These controls protect everyday product workflows without implying third-party security certifications that are not listed.

Account protection

Passwords are hashed, reset and verification links use one-time tokens, sessions are server-managed, and users can enable two-factor authentication.

Workspace authorization

Browser and API operations validate workspace membership and role before allowing protected reads or changes.

API key safety

Modern API keys are stored as hashes, shown only at creation, scoped to capabilities, and checked against active workspace membership.

Webhook safeguards

Outbound webhook targets are validated, private and local destinations are blocked by default, delivery timeouts are enforced, and payloads are signed when a secret is configured.

Web request protections

The application uses CSRF protection for browser forms, rate limits sensitive endpoints, secure cookie options in production, and common security response headers.

Auditability

Key workspace and platform actions can create audit records so administrators can investigate operational changes.

Security still depends on deployment choices

Security still depends on deployment choices

Before production launch, use HTTPS, rotate all development credentials, use a strong session secret, restrict database/network access, configure trusted mail and payment credentials, and keep dependencies patched.

  • Rotate every credential included in development or migration packages before launch.
  • Use Node.js 24 LTS and keep the supported dependency line patched.
  • Keep APP_DOMAIN fixed to the production HTTPS origin.
  • Use a shared production session store when running more than one application instance.
  • Review API scopes, workspace roles, and webhook endpoints regularly.

Planning a multi-team rollout?

Tell us how many teams, users, workspaces, and integrations you expect so the rollout can match your operational requirements.