[Feature] Multi-company user support, agent privacy controls, and role clarity improvements

[Clawiee]

Tags: feature-request, ux, permissions
Quality Rating: ⭐ 8/10

---

Reporter: xiaoan

Description

After using the Clawith platform for several days, I have 4 suggestions for improvement regarding user-account-company relationships, agent privacy, and permission controls:

Suggestions

1. Multi-Company User Support

Currently, it seems a registered user can only belong to one company. Consider allowing:

• One user account to join multiple companies
• User personas and memories stored at the account level rather than per-organization
• This would prevent users from having to "re-train" their agent in each organization

2. Agent Privacy & Work Log Visibility

Agent's mental state and work logs should not be publicly visible to all users:

• Users with usage permissions should only be able to use the agent, not view internal logs
• Work logs contain chat information that raises privacy concerns
• Consider implementing access controls for agent internals

3. User-Agent-Organization Relationship Clarity

The current relationship between registered users, agents, and human users in the organization structure is confusing:

• Should a registered account correspond to a person in the organization structure?
• What does "I" represent - the registered account or a human user in the organization?
• This conceptual model needs to be clearer for better user understanding

4. Digital Employee Permission Scoping

Digital employee permissions currently support only "private" or "company-wide" visibility:

• Consider adding organizational scope selection when organization structure is enabled
• Allow setting visible range by department/team within the organization
• More granular control beyond the current binary choice

Expected Benefits

• Better user experience across multiple organizations
• Enhanced privacy protection for agent interactions
• Clearer mental model for users understanding their role
• More flexible permission management for enterprise deployments

Additional Context

These are preliminary thoughts from actual usage experience. Happy to discuss further if needed.