Not every document is meant for everyone. Client handbooks, onboarding notes or internal docs often need a link you can send to specific people. Sentilis Press does this with two fields: visibility and password.
Private, with a password
---
name: Client handbook
visibility: private
password: blue-notebook
---A private entry stays out of your public list. With a password, anyone who opens its URL sees a password form instead of the page. After typing the password once, the entry stays unlocked in that browser for 30 days.
Without a password, a private entry is visible only to you.
What the password protects — and what it doesn’t
- It is a shared secret, not an account system. Anyone you send the link and password to can pass both on.
- It only applies to private entries. On a public entry the field is ignored, and publishing tells you so.
- Changing it locks everyone out again. People who had unlocked the entry are asked for the new password.
- Removing it makes the entry visible only to you again.
Docs with several pages
For a handbook with sections, use a folder with an index.md:
press/
└── client-handbook/
├── index.md ← private, with the password
├── process.md ← inherits both
└── contacts.md ← inherits bothSections inherit status, visibility and password from index.md. A reader unlocks the handbook once, and moving between sections doesn’t ask again.
Mixing open and closed pages
To leave one section open inside a closed entry — a public summary, for example — declare the fields on that page:
---
name: Public summary
visibility: public
password:
---A section can also declare a password of its own, and it will ask for that one instead.
Publish
sentilis sync ./my-contentShare the URL and the password through separate channels when the content is sensitive.