So perhaps there's room for a smaller feature, where a user selects the people that need to approve this document (in order, or from a pre-saved (by container admin) container-level config) and then those people are notified of the pending approvals.  As the workflow proceeds.  For example, instead of choosing a single moderator for a "container"...being able to setup a moderator chain, where the chain is represented as a list of "groups of users" (perhaps friend-label like functionality)....and the document is published once all Users have given an approval?

Taking a slight step back, if SBS was to be used to allow content to be created in a multi-step approval form...what is the solution Jive would recommend using the SBS vision/paradigm.  I think that might be the better question. For internal use-cases, i'd say this definitely falls within the platform realm of functionality for OOTB behavior...external implementations...it couldn't hurt, but no major use-cases.

Cory,

Some amendments that might be worth noting:

The product already allows "multi-person" approval for documents...what I'm asking for is the ability to have variations.

• For instance, OOTB the multiple approvals "workflow" is setup such that all approvals are attained in a single-step workflow.  There is no order required. 
  
  • In a 3 approver, approver 1 can rejects, approver 2 can approves, and approver 3 approves...now, all 3 of them are made aware 2x over when the document is amended and resubmitted for approval.  Rather than Approver 1, upon approval then Approver 2 is notified, etc...
  • I'm not saying that this has to be THE WAY, because I like the organic approval model; however, it would be ideal if there were options available.
• Once you make options available, it becomes an issue on how to manage them.  What I am asking for may be best summarized, buy the Collaboration options on definition for defining approvers.  Instead of having to list all of the approvals each time; wouldn't it be nice to select a "templated" workflow object...that has a name, description and meaning that the user defines that makes sense to them.
  • They could create a workflow that is just like OOTB, but has 6 names pre-selected
  • They could create a workflow that is multi-stage
  • They could create a workflow that uses "user groupings" instead of users for workflow, where all or some of the approvals are required.
    
    • For example, what if I only want 1 approver for a list of approvers to have to approve it....but it can be any of them.
    • Right now, I do not see a way to achieve this in the product.
  • All of these use-cases would be represented as an option in the UI under Manage Collaboration section, to say
    • Create Ad-Hoc Approval => Current OOTB experience
    • or select from a pre-defined Approval process defined in that container or by the user.

     

So what I'm asking for are options to the Manage Collaboration feature...and providing a recommendation on how to manage/convey those options...as long as the user has options to do the above...and can self manage those options...that is the core of what I am asking.

Having just read this, I'm not sure "multiple approvers" as a core issue will do this request the proper attention I think it needs.  Lastly, could you confirm that the ticket has been updated?  thanks again Cory. =)