Discussion of proposed design for careteam work

Available for review, but please don't merge yet.
This is interesting, because when reading through the documentation and working on the mock API, I feel a need for some consensus on terminology, and maybe we should use "group" and "member".

Take this example (I'm userid `123`):

```
DASHBOARD
===========
123 [root]
456 [view, note, upload]
789 [view]

WHO CAN SEE MY DATA
====================
789 [view]
```

For the "dashboard" screen, I'd call `/access/groups/123` and get:

```javascript
{
  "123": {
    "root": {}
  },
  "456": {
    "view": {},
    "note": {},
    "upload": {}
  }
  "789": {
    "view": {}
  }
}
```

The `permissions` are the `{"view": {}}` type objects (the values of this map), but the collection of key/value pairs I tend to call `groups` (i.e. "groups" I belong to).

On the flip side, for the "who can see my data" screen, I'd call `/access/123` and get:

```javascript
{
  "123": {
    "root": {}
  },
  "789": {
    "view": {}
}  
```

The `permissions` are still the `{"view": {}}` type objects, but the collection of key/value pairs here I tend to call `members` (i.e. "members" that belong to my "group").

You kind of see the symmetry/mirror thing here? I know this is just semantics, but it's going to be all over the code as I need to name variables, so it would be nice if we agreed on something :) I'm open to other suggestions!