This is the answer I was looking for.
… While there would certainly be overhead involved in managing multiple team accounts, I do feel that it could potentially be useful. Here’s the scenario I had in mind:
I am a private consultant with many clients (I am not, but let’s pretend). I work with other individual consultants under the banner of ‘Company Name’, but really it’s a loose affiliation and each of us individual consultants is bound together by a client/project specific consulting agreement.
Here’s our current working arrangement:
We have ‘Client1/Project1’, with me (‘A’), you (‘B’) and john (‘C’).
…and ‘Client2/Project1’,with me (‘A’) and you (‘B’)
…and ‘Client3/Project1’,with me (‘A’) and john (‘C’).
I would not want B to see anything in ‘Client3/Project1’ or C to see anything in ‘Client2/Project1’, but I would want each person to be in ‘Client1/Project1’, as well as anything associated with ‘Company Name’
Oh, and our clients are all super secretive and scared of anything new, so none of them are willing to allow public URLs, even if un-guessable. So I would create a generic account for the client as a team member of their projects and let them view that way.
The teams pricing is very affordable, so if a client is already paying me for a project of a fixed duration, it wouldn’t be so bad to pay for multiple teams. However, it sounds like I’d be paying for my own seat on each of these teams, so if I am on 4 teams it’d be 4x$9 per month that I’m assigned to each. There again, assuming this cost is put back on the client, no big deal…
I was envisioning having a notebook simultaneously ‘tagged’ as belonging to multiple teams as a convenience for managing teams and notebook view and edit permissions, but I now see that it’s not how the teams feature is designed.
I also appreciated that this isn’t how you were envisioning teams. I continue to struggle with the whole notion if public URL sharing… therefore trying to think through work-arounds.