From Sticky Notes to Zero-Knowledge: A Step-by-Step Guide to Team Passwords

If you asked five people at your company right now where the Wi-Fi password, the online banking login, or the social media credentials are stored, you'd probably get five different answers. A sticky note on a monitor. A shared Excel file called "passwords_FINAL_v2.xlsx". A WhatsApp message from three years ago. This is how most Swiss SMEs actually manage credentials — and it's a quiet but serious risk.

The good news is that fixing this doesn't require a big IT project or a steep learning curve. Below is a practical, numbered path from "we wing it" to a properly encrypted team vault — using the Passwords module built into Flitz.

Step 1: Audit what you actually have (15 minutes)

Before moving anything, get a rough list of where credentials currently live: shared drives, notes apps, browser autofill, printed lists in a drawer. You don't need a perfect inventory — just enough to know what you're migrating. Most teams are surprised to find logins for accounting portals, MWST filings, domain registrars, and social media accounts scattered across three or four places.

Step 2: Log into your existing workspace — no new master password needed

This is the step that usually stalls password manager rollouts: yet another master password to create, remember, and inevitably forget. Flitz's vault skips this entirely. Your vault access is derived from your existing Flitz login, so there's no second password to set up, write down, or reset three months from now. If you're already in your workspace, you're already one step from being in your vault.

Step 3: Create your first folders

Organize credentials into folders that match how your team actually works — for example "Banking," "Marketing & Social," "Suppliers," or "IT & Domains." Inside each folder, add items: username, password, URL, and notes. There's a built-in password generator for creating strong, unique passwords instead of the recycled ones probably in use today. Onboarding is designed to take under a minute per person, so this step is more about deciding on folder structure than fighting with software.

Step 4: Move your 2FA codes in too

If your team currently relies on Google Authenticator on someone's personal phone — which becomes a problem the moment that person is on holiday or leaves the company — this is the step that fixes it. Flitz includes built-in 2FA/TOTP support, generating the same rotating 6-digit codes, but stored alongside the password itself. No more asking "can you read me the code from your phone" during a login.

Step 5: Share folders with teammates — in two clicks

This is where a team vault earns its keep. Instead of forwarding a password by email or chat, the folder creator shares the whole folder directly with a colleague in two clicks. Everyone with access sees the same up-to-date credentials, and when a password changes, it changes for everyone at once — no more "wait, which version is current?" Only the person who created the folder can grant access to it, keeping control clear and avoiding accidental oversharing.

Step 6: Understand what "encrypted" really means here

It's worth pausing on this point because it's the core of the feature: passwords are encrypted in your browser before they ever leave your device. This is zero-knowledge encryption — meaning that even a Tenant Owner or admin inside your own company cannot read the stored passwords. Compare that to a shared spreadsheet, which anyone with file access can open and read in plain text. Encryption happening client-side, rather than trusting a server to keep things safe, is the meaningful upgrade over sticky notes, chat messages, or generic documents.

Step 7: Plan for the day someone leaves

Every SME eventually deals with an employee departure, and credential access is often the messiest part of offboarding. Because of the zero-knowledge design, an admin can't simply peek into a departed employee's personal vault items. Instead, the Tenant Owner has an emergency access path built specifically for this situation — with mandatory user notification, so emergency access is never used silently or without a trace. This gives you a clear, accountable process instead of scrambling to reset every login the company might have touched.

Step 8: Make it a habit, not a one-time cleanup

Once folders are set up, the ongoing work is light: add new logins as they're created, use the generator instead of typing "Company2024!" again, and share folders as roles change. Because it's built into the same workspace as your accounting, invoicing, and HR tools, there's no separate login, no separate subscription to manage, and no context-switching between apps.

Why this matters more than it seems

Password mismanagement rarely causes visible damage until the day it does — a locked-out admin account, a leaked banking login, a former employee who still has access months later. Moving from ad hoc sharing to a structured, encrypted vault isn't about paranoia; it's about closing a gap that most growing teams don't get around to fixing until it's forced on them.

You can see the full capability breakdown on the Flitz Passwords feature page, including how folder sharing and emergency access work in more detail.

A password vault only works if people actually use it. Removing the second master password and making sharing a two-click action is what makes adoption realistic for a small team — not just possible in theory.

Total time to get a small team fully migrated: usually under an hour, spread across the steps above. Compare that to the hours lost every year to "can someone send me the Wi-Fi password again" — and the much bigger cost if a leaked spreadsheet ever gets forwarded to the wrong person.