Teams & Konnect Orgs¶

Upsight tracks the internal team structure of each customer account, the Konnect organizations they run, and the relationships between the two. It also lets you link contacts to a specific Konnect org and team so you always know who works on what.

Where things live¶

Everything described below is account-scoped. With an account selected in the sidebar switcher:

Stack (sidebar) - manage Konnect organizations, owner emails, and which teams are mapped into each org.
People (sidebar) - a three-pill row at the top of the page switches between Org Chart (the visual hierarchy), People (contacts list), and Teams (team tree + collaborations). Contact cards in the People pill also expose the Konnect-org / team mapping editor.

Konnect Organizations¶

The Stack page shows a card list of every Konnect org linked to the account.

Adding a Konnect org¶

Click Add Org in the Konnect Orgs card header. The form asks for:

Org Name - your internal label (e.g. Platform Team Prod).
Org ID - the Kong Konnect organization UUID.
Owner Email (optional) - who at the customer owns this org.

Save and the new card appears in the list.

Editing an org or its owner¶

Each org row has an Edit (pencil) icon. Clicking it opens the same form pre-filled with the current values. Update any field and save.

Opening an org in Konnect admin¶

The arrow icon on each row opens admin-cloud.konghq.com/organizations/{org-id}/overview in your default browser. The clipboard icon copies the org ID.

Mapping teams into an org¶

Expand a Konnect org card using the chevron icon. The expanded view shows:

A Mapped Teams chip row - every team currently mapped into this org. Click the × on a chip to unmap.
An Add a team dropdown - pick any account-level team not yet mapped. A team can be mapped into multiple orgs (many-to-many).

If no teams exist yet, the card prompts you to create some on the Teams page first.

Deleting a Konnect org¶

The red trash icon deletes the org. A snackbar offers Undo for a short window after deletion. All team mappings for the deleted org are cleaned up automatically. Any contacts linked to this org have their Konnect-org assignment cleared (but the contacts themselves are not deleted).

Teams (internal hierarchy)¶

The Teams page is where you capture the customer's internal org structure.

Defining teams¶

Click Add Team in the Teams card header. The form asks for:

Team Identifier - a label you enter. This may mirror a Konnect team ID you've noted, or be an internal name. Upsight treats it as free text.
Friendly Name (optional) - a display name used in chips and the chart where present.
Parent Team (optional) - pick any existing team to make this one a child. Choose No parent to make it a top-level team.

Team hierarchy rules¶

A team can have at most one parent.
The Parent Team dropdown hides any team that would create a cycle (the team itself, plus all of its descendants) so you can't accidentally make a team its own ancestor.
Deleting a team automatically re-parents its children to "no parent" (they become roots). The team's collaborations and Konnect-org mappings are removed.

Editing and deleting¶

Each row has pencil and trash icons. The pencil opens the same form pre-filled; the trash icon deletes and cascades as described above.

Collaborations (lateral links)¶

Teams can also "work with" each other across the hierarchy tree - think a platform team that pairs regularly with a security team that reports into a different parent. These are collaborations and live in the Collaborations sub-section on the Teams page.

Adding a collaboration¶

Click Add Link. The dialog shows:

Team A dropdown - any team on the account.
Team B dropdown - filtered to exclude Team A and any team already linked to Team A (one collaboration per pair, stored once regardless of direction).
Note (optional) - free text explaining the reason (e.g. "shared platform review cadence").

Editing the note¶

Click the pencil on any collaboration row. The edit dialog lets you change just the note.

Removing a collaboration¶

The trash icon on each row removes the link immediately. Deleting either team in the pair also cascades the collaboration away automatically.

Org chart¶

The Org Chart pill (the first pill under the People sidebar item) renders the hierarchy and collaborations visually when the account has at least two teams:

Account apex - a small box at the very top showing the account name with a building icon, connected by solid lines down to every top-level team root.
Solid elbow edges - parent → child hierarchy between team boxes.
Dashed curved edges - lateral collaborations between teams in different branches.
Team boxes - team name (friendly name if set, otherwise identifier) with a group icon. Long names ellipsize.
Contacts inside a team box - up to three contact names with a person icon render under the team name. A +N more line shows when a team has more than three linked contacts. Contacts show up here once their team_id is set on the People pill.
Independent subtrees lay out side by side with extra spacing so they read as separate roots.

Interactions¶

Click a team box - opens the same edit dialog that the pencil icon on the team row opens.
Collapse the card - the card header toggles the chart on and off; the other Teams content stays visible.
Horizontal scroll - very wide charts scroll horizontally within the card. The Teams page itself scrolls vertically.

When you'll see an empty state¶

Zero teams: the card is silent; the Teams list itself shows "No teams defined for this account yet."
One team: the card shows a short message inviting you to add one more team.
Two or more teams: the chart renders.

Linking contacts to teams and Konnect orgs¶

On the People page, contact cards surface the contact's team and every Konnect org that team is mapped into, as chips. Clicking a Konnect chip opens the org in Konnect admin; the team chip is informational.

Model: orgs are inherited from the team¶

A contact belongs to one team. That team is mapped into zero or more Konnect orgs via the Stack page's per-org "Mapped Teams" editor. A contact's Konnect-org membership is the union of their team's mapped orgs - there's no separate per-contact org assignment. Move a team into a new org and every contact on that team inherits it automatically.

Assigning a mapping¶

Click the pencil icon on a contact card. The inline editor shows:

Title - the contact's role / title. For Salesforce-linked contacts, the label reads "Title (syncs to Salesforce)" and saving pushes the change to the contact's Title field on Salesforce via the normal write-back queue. For local-only contacts (no salesforce_id), the title is stored locally only.
Team dropdown - any team on the account, or "No team". Changing the team re-computes the inherited Konnect-org chips on Save.

Add-time mapping¶

The manual Add Contact form has the same two dropdowns as optional fields. Contacts imported from Salesforce are created with no mapping - edit them afterwards to set one.

Side effects of deletion¶

Deleting a Konnect org clears the konnect_org_id on all its linked contacts; contacts remain.
Deleting a team clears the team_id on all its linked contacts; contacts remain.

How these features compose¶

Use them together to answer common Kong CSM questions:

Who owns this Konnect org? → Owner Email on the org card.
Which teams run inside this Konnect org? → Mapped Teams on the expanded org card.
What's this customer's internal org structure? → The Teams tree and the Org Chart view.
Who collaborates across silos? → The Collaborations list and the dashed edges on the chart.
Which team and org is this contact on? → Chips on the contact card.