Single CO | Probably a command-line oriented CO with an equal focus on person identity and tool availability
* Pay particular attention to the REST API that are published for COmanage; these will make integration with existing tools simpler and more powerful
| Probably a CO with a more app-focused collaboration
* Pay particular attention to the Domestication Wiki for possible tools that are already domesticated and may serve your collaborations' needs
|
|---|
Multiple CO within the CMP | Probably a CO that is acting more as a service provider to various groups than one focused on a single collaboration effort, where absolute control over branding is important
* Educational institutions at all levels may find themselves in this area. If this is the path you are taking, you may want to use the CO Requirements Assessment document, or something derived from it, to determine what your partner CO will need out of the environment you are creating.
* In particular, you are going to want to make sure you have the roles and responsibilities that will exist in this environment well documented.
| Probably a CO that is acting as a service provider to a variety of collaborations that cannot share resources fully, but where the apps and services are still the focus of the collaboration |
|---|