When a new employee joins, most companies think onboarding is done once the accounts are set up. Email is ready. Slack is ready. The tools are assigned. On paper, it looks finished.
But there is a more important question that rarely gets asked: can this person actually do their job yet?
Because onboarding almost never breaks at account creation. It breaks at access. The first days in a new role tend to be defined by waiting. Waiting for someone to grant permissions. Waiting for credentials to arrive. Waiting for another team to get back to you. People are showing up, but they are not actually working.
This gap is almost never measured, but everyone who has lived through it knows exactly what it feels like.
Access is still treated as tribal knowledge
In most companies, access still lives in conversations and private messages. It gets passed along informally, usually by whoever happens to know the right person to ask. There is no system for it. There is just institutional memory, and whoever you happen to sit near.
The knock-on effects are real. A new hire cannot reach a client account. A developer cannot deploy. A marketer cannot log into a tool they need to do their job. Each delay feels minor on its own, but together they can push onboarding from a few days into a few weeks.
Beyond the lost time there is something harder to measure: employees who spend their first week navigating blockers instead of making progress take a lot longer to feel like they belong.
The hidden cost of onboarding
Onboarding is already expensive. Research puts the average cost per new hire at around $4,700, and most employees take months to reach full productivity.
But buried inside those numbers is a cost almost nobody measures: time lost to access delays. It just gets absorbed into the general friction of starting somewhere new, and it compounds faster than most people expect.
The strange part: Companies have already solved the harder problem
Identity management is largely figured out. Google Workspace makes it straightforward to create and manage users at scale. Teams and roles are defined. Org structure is clear. But access does not follow any of that structure.
Instead it gets handled separately, manually, and inconsistently. What ends up happening is that onboarding has two layers. The first is creating the user. The second, which almost no one talks about, determines what that user can actually do. And it is the second layer that nobody has built a good process for.
This problem gets even messier when someone leaves. Disabling an account is easy. Making sure that person no longer has access to shared credentials is a completely different story. Access lingers in places that are hard to track and even harder to clean up.
The fix is simpler than it sounds
The answer is not more tooling or stricter policies. It is just about making access reflect the structure that already exists.
If someone joins a team, they should get access to what that team works with. If they switch teams, their access should update. If they leave the company, it should disappear. No tickets. No waiting. No one having to remember to do it.
This is what Passwd was built to do
Passwd is a Czech startup building access and password management for teams that run on Google Workspace. The core idea is straightforward: instead of managing access separately, Passwd syncs directly with the groups and users already defined in Google Workspace and derives access from them automatically.
When someone joins a team in Google Workspace, Passwd gives them access to the credentials and tools that team owns. When they move to a different team, access updates with them. When they leave, it is revoked as part of the same offboarding process. Everything is tied to role and structure, not to whoever remembered to send the right message.
The result is that onboarding stops being a coordination task. New hires do not have to ask for access. Teams do not have to manage it. The system just reflects how the company is already set up.
What actually changes
Companies that take this approach report faster onboarding, cleaner offboarding, and a much smaller surface area for credential exposure. But the change that is hardest to quantify is the one that might matter most: new hires stop spending their first week asking for things and start actually doing their jobs.
For teams already on Google Workspace, Passwd works with the structure that is already there. No rebuilding required. Want to see it in practice? Watch how Passwd handles onboarding.
