Teampass

privacysmall business

Self-hosted team password manager with folder-based organisation, role and group access controls, and an audit trail. Built for teams that need shared credentials without paying per-user fees for a cloud password manager

#password-manager#team#credentials#security#php#self-hosted

Quick Start

docker run -d -p 8088:80 -e MYSQL_HOST=db -e MYSQL_DATABASE=teampass -e MYSQL_USER=teampass nilsteampass/teampass:latest

Overview

Teampass is a self-hosted password manager built for teams that need shared credential storage with access controls and an audit trail. Where individual password managers focus on the personal vault experience, Teampass is organised around team ownership: credentials live in folders, folders are assigned to groups and roles, and every access or change is logged against a user identity.

The access control model follows a straightforward hierarchy. Credentials are stored in folders, folders are assigned to one or more groups, and users belong to groups. An IT team might have a folder for server credentials, a finance team a folder for payment processor accounts, and only members of the relevant group see the contents of each folder. Managers can be given read-only access to folders they do not actively manage, and individual credentials can have additional restrictions applied on top of the folder-level permissions.

The audit trail records every view, copy, and modification event with a timestamp and the identity of the user who performed it. For teams that need to demonstrate credential access governance for compliance purposes, or for incident response where you need to know who accessed a compromised account, this log is the feature that justifies Teampass over a shared spreadsheet.

Teampass uses symmetric encryption to store all credentials on the server, with the encryption key also stored server-side. This is a meaningful security distinction from zero-knowledge password managers like Bitwarden: access to the server or database compromises the entire vault. For most internal team deployments this is an acceptable trade-off; for teams with strict data security requirements, this architecture deserves scrutiny before deployment.

The application runs on any standard PHP and MySQL host and deploys cleanly via Docker for teams that prefer that path. No per-user licensing means the cost of adding a team member is zero.

Use Cases

Specific ways to use Teampass for your workflow.

01
Store shared service credentials and API keys for a team where multiple people need access to the same accounts
02
Organise passwords into folders with per-folder access controls so different teams see only the credentials relevant to them
03
Audit who accessed or modified a shared credential and when, for compliance or incident investigation purposes
04
Replace a shared spreadsheet of passwords with an encrypted, access-controlled store that does not get emailed around

Deployment Strategy

Recommended ways to host Teampass in your own environment.

docker
self-hosted