Change Details

## Overview Users should be able to create actual draft posts that are visible to the rest of their team. ### Use Case If a #submit.as submission is automatically published to a blog, but an admin wants to remove it, they'll need to put it somewhere accessible to the entire team. In general, we should support this use case of unpublishing a previously-published posts on a team. ## Implementation TODO

## Overview Users should be able to create true **draft** posts that are visible to the rest of their team. ### Use Cases #### Submit.as If a #submit.as submission is automatically published to a blog, but an admin wants to remove it, they'll need to move it somewhere accessible to the entire team, instead of as a personal anonymous post. #### General In general, we should support unpublishing previously-published posts on a team. #### Authors It's clear (after T863) this is also needed for posts with authors attached. Our old "anonymous posts" system won't work, since authors belong to a specific team, and will become detached once a post is moved to a personal, anonymous post. Also, there is probably little need to move posts between a team and personal account. ## Implementation In general: * We need to support posts owned by an organization / team, rather than an individual user * Add a new top-level nav item: Posts (T810?)

## Overview Users should be able to create actual true **draft** posts that are visible to the rest of their team. ### Use Cases If a #submit.as submission is automatically published to a blog, but an admin wants to remove it, they'll need to put it somewhere accessible to the entire team.#### Submit.as If a #submit.as submission is automatically published to a blog, but an admin wants to remove it, they'll need to move it somewhere accessible to the entire team, instead of as a personal anonymous post. #### General In general, we should support unpublishing previously-published posts on a team. #### Authors It's clear (after T863) this is also needed for posts with authors attached. Our old "anonymous posts" system won't work, since authors belong to a specific team, and will become detached once a post is moved to a personal, anonymous post. Also, we should support this use case of unpublishing a previously-published posts on a teamthere is probably little need to move posts between a team and personal account. ## Implementation TODOIn general: * We need to support posts owned by an organization / team, rather than an individual user * Add a new top-level nav item: Posts (T810?)