[Feature Request] Enterprise Management: Creator Real Name Display & Centralized Relationship Configuration

[Clawiee]

Tags: feature-request, ux, enterprise, admin, user-management
Quality Rating: ⭐ 9/10

---

Reporter: 曾总 (via 尹怡惠 - Customer Feedback)

Summary

Two enhancement suggestions for Clawith digital employee management in enterprise scenarios:

---

Issue 1: Display Real Name of Agent Creators

Current Behavior

When viewing a digital employee/agent, the creator field displays the creator account's nickname (self-chosen display name).

Problem

• Administrators cannot identify the real person behind an agent
• Difficult to manage and track agent ownership in enterprise settings
• When reviewing agents, there's no way to know which employee created them

Proposed Solution

Display the creator's real name (real-name identity) in addition to or instead of the nickname. This could be:

• Show both: "Real Name (@Nickname)"
• Show real name in admin/management views
• Add a toggle for admin view to see real identities

Use Case

"When I want to know who created a certain digital employee, I only see a nickname. I need to know the actual employee's name for management purposes."

---

Issue 2: Enterprise-Wide Relationship Management

Current Behavior

When creating a new agent, administrators must manually search and add each person to the agent's relationship network one by one.

Problem

• In large enterprise groups, this is extremely time-consuming
• Each department creating agents must repeat this process
• No centralized user/relationship management

Proposed Solution

Implement enterprise-level relationship configuration:

1. Admin-level relationship templates:

   • Administrators can pre-configure relationship networks at the organization level
   • Define default relationship sets for different agent types/departments

2. Inherit organization relationships:

   • When a department creates an agent, it can inherit pre-configured relationships
   • No need to add people one by one

3. Department-level relationship pools:

   • Each department can have its own relationship pool
   • Agents created within the department automatically have access to the pool

Use Case

"In a large enterprise group, adding people one by one to relationships is cumbersome. We need a unified setting where administrators can configure agent information once, and departments can use it directly without manually adding each person."

---

Business Impact

These improvements would significantly enhance Clawith's enterprise readiness:

• ✅ Better governance and accountability
• ✅ Faster agent deployment in large organizations
• ✅ Reduced administrative overhead
• ✅ Improved user experience for enterprise customers

Priority

High - These are blockers for enterprise adoption at scale.