| Panel |
|---|
COmanage is a collaboration management platform designed for virtual organizations. With customizable enrollment flows, clear audit trails, and clear APIs that allow for integration with a variety of collaborative applications such as wikis, mailing lists, and more, COmanage provides VOs with an organized yet simple interface for identity and access management. This documentation focuses on the needs of a platform administrator, after the software has been installed. Application developers and advanced administrators will find installation and other more technical information in the COmanage Technical Manual. |
...
- Determining CO Requirements
- Registry Installation
- Registry Platform Configuration
- Creating enrollment flows
- Invitation-based enrollment
- Self-sign-up enrollment
- Administrative enrollment
- Attribute release requirements
Workflow for Common Deployment Models
Scenario 1 - A University with Several Virtual Organizations
Features: A single platform managed by a single, central organization, with multiple, discrete VOs each with their own enrollment processes ; enrollment processes include self-signup, administrative/delegated signup, and conscripted signup; primarily campus IdP with support for federated identities; apps include typical collaboration apps we well as domain specific apps, ssh key management, github access; need to demonstrate audit capabilities for grant reporting
Scenario 2 - A “Citizen Science” Virtual Organization
Features: Single VO, primarily self-registration of users, extensive use of a social-to-SAML gateway, apps limited to typical collaboration apps such as a mailing list service and a wiki, github access; include Terms of Service functionality
Scenario 3 - A Large Virtual Organization with Domain-Specific Requirements
Features: Single VO, enrollment processes include invitation signup, administrative/delegated signup, and conscripted signup; federated identity as well as IdP of Last Resort; apps include typical collaboration apps we well as domain specific apps, ssh key management, github access; need to demonstrate audit capabilities for grant reporting
Scenario 4 - A Large Research Group Managing a Collaboration with Multiple Partner or Subsidiary Virtual Organizations
Features: A hub-and-spoke model for collaboration, with a primary VO setting up the collaborations of smaller VOs; enrollment processes include self-signup, administrative/delegated signup, and conscripted signup; federated identity required; apps limited to typical collaboration apps such as a mailing list service and a wiki
Managing Users and Groups
...