One of the main use cases for Orbit as a Community Manager too is to resolve multiple "Identities" to a single individual, aka Member. For example, Orbit will automatically map multiple email addresses, Slack users, GitHub users, etc. to a single person.

This is a critical component to using this data for internal reporting and communication management to ensure we are contacting members of our community via the appropriate channels and to the correct accounts. 

The existing Orbit connector does not include the full set of identities collected for members. Here are details of the proposed change captured in Support Ticket 126207:

What I am going to propose internally, is a change to our member_in_workspace_identity table's schema.
 
The member_in_workspace_identity schema should instead include all of the identity properties based on the identity object returned by Orbit's API.
 
Orbit Identities API for reference.
 
Example object returned by Orbit:
{
  "id": "rMTjX2rz",
  "type": "github_identity",
  "attributes": {
     "uid": string,
     "email": string,
     "username": string,
     "name": string,
     "source": string, (required value)
     "source_host": string
  }
}
 
Current member_in_workspace_identity table columns:

• ID
• TYPE
• MEMBER_ID
• _FIVETRAN_DELETED
• _FIVETRAN_SYNCED

 
Revised member_in_workspace_identity table columns:

• ID
• TYPE
• UID
• EMAIL
• USERNAME
• SOURCE
• SOURCE_HOST
• MEMBER_ID
• _FIVETRAN_DELETED
• _FIVETRAN_SYNCED

 
I think this would be cleaner than trying to incrementally add columns to the member_in_workspace table for each of these properties for every identity.
 
Additionally, it would be much more dynamic for adding new identity types down the road.