Shared SFTP sites for teams, end-to-end encrypted
Give colleagues the same sites and stored passwords, without e-mailing configuration files.
NixSCP Teams share SFTP, SCP, FTP, WebDAV and S3 site folders between colleagues, end-to-end encrypted: everyone gets the same sites with their stored passwords and settings, without passing configuration files around. Owners and admins edit the sites; members use them. The NixSCP cloud never sees the sites, the passwords or the team key. Teams are part of NixSCP Pro, free during the public beta; every person needs a NixSCP account with cloud sync unlocked.
Share sites with your team in four steps
- Create a team: Pro › Teams... › New Team.... You are its owner.
- Add a site folder: put the sites in a folder in the Login dialog, then Add Folder.... They move into
Team: <team name>in your site tree. - Invite: Invite..., pick the role and validity (1 to 30 days), and send the one-time code privately.
- Join: your colleague uses Pro › Teams... › Join with Code..., and the team's sites appear in their NixSCP.
Roles
| Owner | Admin | Member | |
|---|---|---|---|
| Use the team's sites | ✓ | ✓ | ✓ |
| Edit sites, add folders, rename the team | ✓ | ✓ | – |
| Invite members, revoke invites, remove members | ✓ | ✓ | – |
| Invite or remove admins, change roles | ✓ | – | – |
| Delete the team | ✓ | – | – |
| Leave the team | – | ✓ | ✓ |
Members' local changes to team sites are reverted at the next sync, with a notice. Teams sync 20 seconds after NixSCP starts, every 3 minutes, and on Sync Now.
Invite codes the server cannot use
An invite code looks like <id>-<secret>, works once and expires. NixSCP shows it once and does not keep it. The secret part never reaches the server: the team key is encrypted with a key derived from it, and the server only stores a hash of a separate proof. A wrong code does not use up the invite. Only the owner can create admin invites.
Encryption
- Every account has an X25519 key pair; the private key is stored encrypted with your personal sync key.
- Each team has a random 256-bit team key, given to each member as a sealed box bound to the team and key version.
- The team's sites are uploaded as one AES-256-GCM snapshot under the team key, authenticated like cloud sync.
Removing people
When someone is removed or leaves, the server cuts their access at once. The next sync of an owner or admin creates a new team key and uploads the sites again under it, and the removed person's NixSCP deletes the team's sites at its next sync.
Change the passwords that matter. A former member could have copied server passwords while they had access, and an offline computer keeps its copy. NixSCP reminds you of this when you remove someone.
Good to know
- Agent Access stays personal: it is never shared through a team, and each person decides whether agents may use a team site.
- Saved tunnels of a team site are shared with the site.
- Team sites sync with the team, not with your personal settings.
- Limits: 20 owned teams per account, 50 members and 50 pending invites per team.
Questions or problems? See the FAQ, open an issue on GitHub or write to hello@codewizdev.com.