As of v2.0.0, COmanage Registry supports a concept of CO Services. A CO Service represents a service or application that a CO Person has access to by participating in the collaboration. While access to the service is likely controlled by Registry managed attributes, the service itself is not accessed as part of Registry. Instead, CO Services act as inventory or catalog of available services, rendering a list of available services on a per CO Person basis.
CO Services are registered by a CO Administrator via the Configuration >> Services menu, and are made visible to users via both the Services menu (v2.0.x only; visible only after the first CO Service is registered) and the Service Portal (available in the main menu). CO Service attributes include
Visibility: Who can see this CO Service entry. Note that administrators are not treated specially – they will only see Services in the menu and portal for which they have associated eligibilities. To see the full list of services, administrators can use the configuration menu.
CO Admin: Only CO Administrators within the CO can see this service
CO Group Member: Only members of the associated CO Group can see this service
CO Person: Any CO Person within the CO can see this service
Unauthenticated User: Anyone can see this service
If at least one CO Service is configured with Unauthenticated User visibility, then the Service Portal will be publicly accessible. Otherwise, only members of the CO can see the Service Portal.
As of v3.1.0, it is possible for a CO Person to add or remove themselves from the CO Group associated with a Service directly from the Service Portal, using the Join and Leave buttons. Using Join and Leave is functionally equivalent to navigating to My Groups, finding the appropriate group, and ticking the Member button. This is only available when the CO Group associated with a Service is an open group.
Administrators cannot use this interface on behalf of a CO Person, but must instead use the regular group management interfaces.
As of Registry v3.3.0, CO Services can be provisioned. Currently, no out of the box Provisioner Plugins support provisioning Service, but future updates may introduce such support.
See also: cm_co_services