Form and Break Organizational Relationships Without Administrator Action

[GoogleCodeExporter]

Although an administrator should be able to form organizational relationships, 
each organization should be able to form and break relationships amongst 
themselves without interference or action by the administrator.

Organizations will inevitably want to share client data with one another.  A 
link/button to "Request access" should appear wherever data is redacted. If 
there is a list of other organizations, there should be an option to "share 
access" with that organization.

If a person clicks on that option, they are asked, "Is this organization an 
()Affiliate, or does your organization ()Share a parent organization with this 
organization, which is in the system?"

If the organization shares a parent organization, they must choose the parent 
organization (or create one). If they create a parent organization, the new 
proposed parent organization is sent to the administrator for approval at the 
same time that an email is sent to all points of contact for the organization 
for confirmation.

Regardless of whether the organization is an affiliate or a parent, an email is 
sent to the point of contact for the other organization to confirm the 
relationship before it becomes active.

Creation of a relationship must be bi-lateral.  Breaking a relationship may be 
unilateral.  The other organization is notified if a relationship is broken.

See Issue 141 and Issue 145

Original issue reported on code.google.com by v...@aarontitus.net on 14 Jan 2013 at 1:16