- 6 minutes to read
Unassigned Entities and Contact Actions
New .7.x
This page documents unassigned entity governance, quick contact action UI, emergency contacts, and partner/vendor system tracking for Mapify Ownership and Team Management.
Back to Ownership and Team Management
Behavior When Owner is Unassigned
Entities without ownership information are flagged for governance review.
Visual Indicators
| Indicator | Visual Style | Purpose |
|---|---|---|
| Warning icon | Yellow triangle on node corner | Draw attention to missing ownership |
| Red border | 2px red border around node | High visibility for governance workflows |
| "Unassigned" label | Text in node footer | Clear text for screen readers and colorblind users |
| Actionable tooltip | "No owner assigned. Click to assign." | Guides users to resolution |
HTML Example
<div class="mapify-node unassigned"
data-entity-id="SRV-99999"
aria-label="Legacy FTP Service - No owner assigned - Warning"
role="button" tabindex="0">
<div class="status-badge warning"
aria-label="Warning: No owner assigned" role="img">
<i class="fas fa-exclamation-triangle" aria-hidden="true"></i>
</div>
<span class="node-name">Legacy FTP Service</span>
<div class="node-footer">
<span class="owner-status unassigned">
<i class="fas fa-user-slash" aria-hidden="true"></i> Unassigned
</span>
<button class="btn-assign" aria-label="Assign owner to Legacy FTP Service">
Assign Owner
</button>
</div>
</div>
CSS
.mapify-node.unassigned { border: 2px solid #dc3545; background: #fff5f5; }
.status-badge.warning {
position: absolute; top: -8px; right: -8px;
width: 24px; height: 24px;
background: #ffc107; border: 2px solid #ffffff; border-radius: 50%;
display: flex; align-items: center; justify-content: center;
color: #000000; font-size: 14px;
}
.owner-status.unassigned { color: #dc3545; font-weight: bold; }
.btn-assign {
padding: 4px 8px; font-size: 12px;
background: #0056b3; color: #ffffff;
border: none; border-radius: 3px; cursor: pointer;
}
.btn-assign:focus { outline: 2px solid #0056b3; outline-offset: 2px; }
Governance Workflow
- Detection – Unassigned entities flagged automatically in real time
- Notification – Weekly email to administrators listing all unassigned entities
- Assignment – Click "Assign Owner" to open assignment dialog
- Compliance reporting – Track ownership coverage % (target: 100% production, 95%+ non-production)
Quick Contact Actions
Ownership display enables one-click communication with entity owners.
Supported Actions
| Action | Icon | Behavior | Requires |
|---|---|---|---|
| Send Email | Opens default email client with owner's address pre-filled | OwnerEmail custom metadata field |
|
| Start Teams Chat | Opens Microsoft Teams chat with owner (msteams:// deep link) |
Azure AD integration + OwnerEmail |
|
| Call Owner | Initiates phone call on mobile or displays number on desktop | Phone custom metadata field |
|
| View Profile | Opens owner's Azure AD/LDAP directory profile page | Directory integration |
HTML Example — Contact Actions Menu
<div class="mapify-tooltip owner-tooltip" role="tooltip" id="tooltip-INT-12345">
<div class="tooltip-header">
<img src="/api/users/avatar/john.smith" alt="John Smith" class="avatar-small">
<div class="owner-info">
<strong>John Smith</strong>
<span class="team-name">Integration Services</span>
</div>
</div>
<div class="contact-actions">
<a href="mailto:john.smith@company.com" class="action-button"
aria-label="Send email to John Smith">
<i class="fas fa-envelope" aria-hidden="true"></i>
<span>Email</span>
</a>
<a href="msteams://teams.microsoft.com/l/chat/0/0?users=john.smith@company.com"
class="action-button"
aria-label="Start Teams chat with John Smith">
<i class="fas fa-comment" aria-hidden="true"></i>
<span>Teams Chat</span>
</a>
<a href="tel:+15550199" class="action-button"
aria-label="Call John Smith at +1-555-0199">
<i class="fas fa-phone" aria-hidden="true"></i>
<span>Call</span>
</a>
<a href="/directory/users/john.smith" class="action-button"
aria-label="View John Smith's profile">
<i class="fas fa-id-card" aria-hidden="true"></i>
<span>Profile</span>
</a>
</div>
<!-- Emergency backup contact (critical resources) -->
<div class="emergency-contact" role="alert">
<i class="fas fa-shield-alt" aria-hidden="true"></i>
<strong>Backup Contact:</strong> Jane Doe (jane.doe@company.com)
</div>
</div>
Accessibility Requirements
- Keyboard navigation: Tab to cycle through action buttons; Enter/Space to activate
- ARIA labels: Include owner name and action (e.g., "Send email to John Smith")
- Focus indicators: Visible 2px outline on all focused buttons
- Touch targets: Minimum 44×44px on mobile
Emergency Contact Display
For critical resources (production databases, payment gateways, security services):
- Show badge with "Backup Contact" label always visible in tooltip
- Link to on-call rotation or incident response runbook
- Require backup owner for all entities tagged "critical"
- Audit critical systems monthly for missing backup contacts
Partner and Vendor Tracking
External systems owned by partners or vendors require special identification.
Visual Indicators
| Indicator | Visual Style | Accessibility |
|---|---|---|
| Partner badge | Orange badge on node corner | aria-label="External partner system" |
| Orange left border | 4px orange border (#e65100) |
Combined with "External Partner" text label in tooltip |
| External icon | Small icon next to entity name | aria-hidden="true"; ownership label in node aria-label |
HTML & CSS Example
<div class="mapify-node partner-system"
style="border-left: 4px solid #e65100;"
aria-label="SAP ERP System owned by SAP Support Team - External partner system"
role="button" tabindex="0">
<div class="partner-badge" aria-label="External partner system" role="img">
<i class="fas fa-handshake" aria-hidden="true"></i>
</div>
<span class="node-name">
SAP ERP System
<i class="fas fa-external-link-alt" aria-hidden="true"></i>
</span>
<span class="owner-label">
<i class="fas fa-building" aria-hidden="true"></i> SAP Support Team
</span>
</div>
.mapify-node.partner-system { border-left: 4px solid #e65100; background: #fff8f0; }
.partner-badge {
position: absolute; top: 4px; right: 4px;
width: 24px; height: 24px;
background: #e65100; border: 2px solid #ffffff; border-radius: 50%;
display: flex; align-items: center; justify-content: center;
color: #ffffff; font-size: 12px;
}
Partner Contact Management
Track the following custom metadata fields for external systems:
| Field | Type | Purpose |
|---|---|---|
PartnerVendor |
Boolean | Marks entity as externally owned |
PartnerName |
Text | Vendor company name |
PartnerSupportEmail |
Vendor support contact | |
PartnerSLA |
URL | Link to SLA document or contract |
Related Topics
- Ownership and Team Management – Feature overview
- Visual Display and Avatars – Avatars, color-coding, filters
- Team Management and Hierarchy – Team definition, org hierarchy, permissions
- Repository Model