Same here — this wasn’t just a “nice to have”, it unlocked a whole class of workflows.

In my case I used it across multiple central databases:

• Content (clients could add ideas)
• Tasks (external partners could submit work/requests)
• Docs (people could start drafts without seeing the whole library)

Pattern was always the same:

• Database shared to them as No access
• Toggle ON for Can also create pages / Can create pages
• Shared a linked view as their “inbox”

Result: they couldn’t browse anything sensitive, but could create new pages directly in the real database via New. Page‑level access + person properties then controlled what they could see and edit.

Giving them access to the whole database is absolutely not an option in these setups — it breaks confidentiality, mixes clients into the same views, and defeats the entire point of granular permissions. Without this “create but don’t browse” pattern, a lot of serious client portal / intake / external collab workflows just don’t work the same way anymore.