+1 for shared stacks. I'm putting article drafts for an emagazine we are creating for a tech audience. I have a stack for the categories of articles in various stages of creation. I want to share everything in this stack with the tech editors and authors, including new notebooks, changed notebook names within the stack, etc. I have other stacks for other purposes (some to do with the emag, others for other purposes). From a design perspective, I think that the simplest form of sharing stacks (with the same permissions for everything in the stack, current and future) meets the needs of the work teams for which this is a great solution. For enterprise docs, we already have Google Docs (the finished articles, the issue .epub and .mobi files), where permissions can be adjusted by user or group. thanks, Hank Fay
