Shared workspaces are great until they're not. The moment a folder holds client work, financials, hiring notes, or anything you don't want every teammate to see, a single permission for the whole workspace stops being enough.
v0.8.0 adds password protection at the level where it actually matters: folders and individual pages. Set a password on a folder and the entire subtree becomes locked. Set a password on a page and that one page is locked. The rest of the workspace keeps behaving the same way it always did.
The flow is short. Open the protected branch's settings, choose a password, save. From then on, anyone who tries to open the folder or page is asked for the password before they can read it. People without the password see the lock — not the content.
This pairs cleanly with the rest of Yoinko's access model. The workspace owner still controls who's a tenant member. Cloud Crew seats still gate who can see the workspace at all. Page sharing still publishes a read-only view. Folder and page passwords sit on top: a per-section curtain inside a workspace people already have access to.
Where this shows up most is in workspaces that mix audiences: a freelancer keeping a client folder password-protected from other clients in the same workspace; a small team sharing one Yoinko instance but wanting payroll out of view; a project lead handing read access to a contractor without exposing the rest of the org's notes.
Password protection isn't a replacement for tenant boundaries or sharing — those still do their jobs. It's the missing middle layer: a way to keep something private inside a workspace without spinning up a new one. Set it once and forget it. The branch stays locked until you decide otherwise.