Explore an alternative way of explaining states

[plaindocs]

Some quick noodling on #11508 -- this makes more sense to me, but I'm happy to have another bash.

Is there a canonical link for allocating permissions? Or is that all tied in up SSO?

---

📚 Documentation previews 📚

• User's documentation (docs): https://docs--11512.org.readthedocs.build/en/11512/

• Developer's documentation (dev): https://dev--11512.org.readthedocs.build/en/11512/

[plaindocs]

Hmmm, actually we talk about privacy levels and document states, and this change obfuscates that a little.

[ericholscher]

Yea, it's a bit confusing, but I think this PR is definitely a step in the right direction. "Not hidden" is a bit of an odd state, but useful to explicitly note.

I feel like the "How we envision this working" is also weird and something I want to update, and we should probably note a couple different workflows that are enabled, and suggestions for when they are the best option.

I can try to take a swing at the "How we envision this working" section if it makes sense in this PR, or should I open another to not mix things up?

[plaindocs]

@ericholscher I'm just pushing up some changes to that section, but feel free to revert and propose edits in this PR, or build from it.

[ericholscher]

This feels way better than what we had before 👍

[humitos]

This is a great improvement! 💯 . I left a few comments that we can consider.