- 6 minutes to read

Ownership and Team Management

Mapify enables you to visualize and manage ownership information for integrations, systems, services, and resources in your integration landscape. By clearly displaying who owns and is responsible for each entity, teams can quickly identify contacts, coordinate changes, and maintain accountability across distributed organizations.

Why Use Ownership Display?

  • Instant Accountability – Immediately see who owns each system without searching documentation
  • 60% Faster Incident Response – Contact the right person in seconds during production issues
  • Team Coordination – Coordinate cross-team changes by viewing ownership boundaries
  • Quick Contact – One-click access to email, Teams chat, or phone for critical resources
  • Compliance and Audit – Track ownership for SOX, GDPR, and regulatory requirements
  • Partner Management – Identify and tag external vendor/partner-owned systems

Organizations using ownership displays report 40% reduction in "Who owns this?" questions and faster onboarding for new team members.

What is Ownership Display?

Ownership display shows who is responsible for each entity directly in the Mapify graph visualization. Ownership information is sourced from Custom Metadata fields in the Nodinite Repository Model.

Key Capabilities:

  1. Visual Indicators – Tooltips, avatars, and color-coding by team
  2. Filter by Owner – Show only entities owned by specific person or team
  3. Contact Actions – Click to email, Teams chat, or call owner
  4. Unassigned Detection – Highlight entities with missing ownership for governance
  5. Partner/Vendor Tagging – Identify external dependencies

Ownership Data Source

Ownership data comes from Custom Metadata fields in the Nodinite Repository Model:

Field Type Example Purpose
Owner Text "John Smith" Primary owner name
OwnerEmail Email "john.smith@company.com" Contact email
Team Text "Integration Services" Owning team/department
TeamColor Color "#FF5733" Team color for graph visualization
Phone Phone "+1-555-0199" Emergency contact number
BackupOwner Text "Jane Doe" Secondary contact for critical resources
PartnerVendor Boolean true Indicates external ownership

Manage fields in Repository Model > Custom Metadata settings.

Visual Display Options

Display Method When to Use Accessibility
Hover Tooltips Default for all nodes. Shows owner, team, email, phone on hover/focus. Focus-triggered for keyboard users; screen reader reads via aria-label.
Avatars Display owner initials/photo on node. Best for small graphs (<50 nodes). Include alt text with owner name. Never the sole indicator.
Color-Coding by Team Apply team color to node border. Ideal for team-based filtering. Never color-only. Combine with text labels or patterns (4.5:1 contrast min).
Unassigned Indicator Warning icon for entities without owner. Governance workflow. Red border + warning icon + "Unassigned" label for screen readers.

Hover Tooltip Display

Default behavior: Hovering or focusing a node shows a tooltip with ownership details including owner name, team, email (clickable mailto:), phone, and backup owner for critical resources.

<div class="mapify-node"
     data-owner="John Smith"
     tabindex="0"
     aria-label="SAP Finance Integration owned by John Smith, Integration Services team"
     role="button">
  <span class="node-name">SAP Finance Integration</span>
</div>

<div class="mapify-tooltip" role="tooltip" id="tooltip-INT-12345">
  <p><strong>Owner:</strong> John Smith</p>
  <p><strong>Team:</strong> Integration Services</p>
  <p><a href="mailto:john.smith@company.com">john.smith@company.com</a></p>
  <p><a href="tel:+15550199">+1-555-0199</a></p>
</div>

Accessibility: Tooltip appears on focus (not just hover); role="tooltip"; Escape dismisses and returns focus to node.

Visual Display and Avatars (Spoke)

Avatar display, team color-coding (full WCAG AA palette), high-contrast pattern overlays, and filter-by-owner/team UI:

  • Avatars: Initials or profile photos, 24px desktop / 32px mobile, CSS specifications
  • Color palette: 6 team colors all meeting 4.5:1 WCAG AA contrast ratio
  • Color application: Node border, background tint, or glow — never color-only
  • Filter UI: Owner dropdown, team dropdown, quick filters ("My Entities", "Unassigned", "Partners")

See Visual Display and Avatars for complete HTML/CSS examples, accessibility details, and filter behavior.

Unassigned Entities and Contact Actions (Spoke)

Governance for unassigned entities and one-click contact actions:

  • Unassigned indicators: Red border + yellow warning badge + "Unassigned" text label + actionable tooltip
  • Governance workflow: Detection → weekly admin notification → assignment dialog → compliance reporting (100% ownership target)
  • Quick contact: Email (mailto:), Teams Chat (msteams://), Phone (tel:), and Profile links
  • Emergency contacts: Backup owner always visible for critical resources
  • Partner tracking: Orange border + badge for external systems; PartnerName, PartnerSupportEmail, PartnerSLA metadata fields

See Unassigned Entities and Contact Actions for complete HTML examples, CSS, and ARIA requirements.

Team Management and Hierarchy (Spoke)

Team definition, organizational hierarchy visualization, entity assignment, and permissions:

  • Team creation: Name, color, email, external-partner flag, member management with Owner/Contributor/Viewer roles
  • Hierarchy views: Team-centric, Person-centric, Entity-centric (tree UI with keyboard navigation)
  • Entity assignment: Individual (Entity Details panel) and bulk (right-click → Bulk Assignment)
  • Permissions matrix: Admin > Team Owner > Contributor > Viewer — enforced at UI and API level
  • Azure AD/LDAP sync: Automatic team membership synchronization with group mapping
  • Emergency contacts: EmergencyPhone, BackupContact, OnCallSchedule, EscalationPath fields for critical resources
  • Distributed teams: Timezone metadata, local time display in tooltip to respect business hours

See Team Management and Hierarchy for complete HTML forms, permission tables, Azure AD configuration, and distributed team patterns.

Use Cases

Incident Response

Scenario: Production integration fails at 2:00 AM.
Solution: Open Mapify → locate failed node → hover to see ownership → click Call to reach emergency contact.
Benefit: 80% faster incident response — no documentation searching.

Compliance Audit

Scenario: Auditor asks who is responsible for all PII-handling integrations.
Solution: Apply tag:PII + show unassigned filter → export list with owners to Excel.
Benefit: 60% faster audit preparation.

Team Reorganization

Scenario: Integration Services splits into "API Services" and "Legacy Integration".
Solution: Filter by team:"Integration Services" → use bulk assignment to reassign entities to new teams.
Benefit: Clear visual ownership map during organizational transitions.

Partner System Identification

Scenario: Security team needs all external-partner-owned systems for risk assessment.
Solution: Filter team:"External Partners" → all partner systems highlighted with orange borders.
Benefit: Instant visibility into external dependencies and third-party risk.

Best Practices

  • Assign ownership to all entities – Run weekly governance reports to identify unassigned entities; target 100% production coverage
  • Use team color-coding consistently – Enforce team colors in Custom Metadata; avoid changing colors frequently
  • Keep contact information current – Sync from Azure AD/LDAP automatically; review quarterly
  • Tag critical resources with backup owners – Require backup owner for all "critical" or "production" tagged entities
  • Don't rely on color alone – Violates WCAG 2.1 AA; combine with text labels, avatars, or patterns
  • Avoid over-cluttering large graphs – Use hover tooltips instead of always-visible avatars when graph has 200+ nodes

Next Steps

  1. Configure Custom Metadata – Define ownership fields in Repository Model
  2. Assign Owners – Populate ownership data via individual or bulk assignment
  3. Enable Color-Coding – Set team colors for visual identification
  4. Create Ownership Views – Save filtered views by team in Saved Views
  5. Run Governance Report – Identify and resolve unassigned entities