This is confusing/misleading:
> Unpublished : "For team notebooks, the visibility is determined by the sharing permissions." ...
And yet I don't see anywhere any sort of 'sharing permissions' within a Team notebook that differ from any other notebook. That is, all notebooks created within teams appear to be visible to all team members. I recall reading somewhere that you were planning to make is so that a user can create a private notebook within a team before exposing it to team members... but this hasn't happened yet?
Aaron, the section just above this section describes that in detail. You can indeed specify individual permissions for team members on team notebooks. If you are not seeing that, then there is definitely something wrong... please email me at support@observablehq.com if you still don't see the 'Share' button at the top right of your team notebooks.
Hi Cobus, and thanks for the quick reply. I see that text but it wasn't clear to me, especially given the issues I recently flagged to the forum:
https://talk.observablehq.com/t/conflicting-messages-teams/3784
Although it might not be much different than the passage above, I found this, more clear explanation when I was searching around trying to find the information I was recalling in my first post:
https://observablehq.com/@observablehq/permissions-for-teams-notebooks
> No access - is the default for all newly created notebooks. Other Team members will not see your notebook in their List view for Team's notebooks, in collections, the recent activity list, or in search results. Until a notebook is Link Shared or Published it will not be accessible, even if they have the link. However, because it was created in your team, it still has access to the team's secrets and databases. This allows you to use your team data while working on a notebook in private, until you are ready to share your work.
... I haven't created another team account for myself to test, so I was also working on an assumption that my teammate could see all notebooks (he suggested so, but I didn't check). Sorry for that! He probably could see a subset when he started b/c I had already linked shared them.
I'd encourage you to review and possibly revise the language here on permissions and/or cross-reference Wiltse's other notebook.
Thank you for the hand-holding and for this platform!
..Sorry, I see that you cross-referenced Wiltse... not sure how I missed that initially. Thanks again!
Thanks - you're fast. I was writing up a revision request but sidetracked by the Community Meetup. Proposing a stray fix to an un-closed parenthesis. Please otherwise consider this resolved (I can't self-resolve a comment).