'Add user email identifier for Trustclaw-like apps' ([DASH-277](https://linear.app/composio/issue/DASH-277/add-user-email-identifier-for-trustclaw-like-apps))
User instruction: @devin follow the spec in the description
Adds a "Pro tip" message to the Users empty state encouraging developers to use email as their userId for easier identification and tracking. This is placed below the main description text, styled as secondary/muted text.
Addresses DASH-277.
text-sm text-muted-foreground)@composio/lib) not resolving — relying on CI for validation'Add user email identifier for Trustclaw-like apps' ([DASH-277](https://linear.app/composio/issue/DASH-277/add-user-email-identifier-for-trustclaw-like-apps))
User instruction: @devin follow the spec in the description
I'll be helping with this pull request! Here's what you should know:
✅ I will automatically:
⚙️ Control Options:
If building Trustclaw, would need one more user identified: user's email.
Source: Slack thread
Goal: Add a pro tip in the Users empty state encouraging developers to use email as userId.
Location: src/app/(project)/[org]/[project]/users/_components/users-empty-state.tsx
Implementation:
text-sm text-muted-foreground)Why: Developers don't pass user email to Composio, so the best practice is to use email AS the userId itself for easier debugging and user identification.
Ready for Devin
The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Actions | Updated (UTC) |
|---|---|---|---|
| dashboard | Mar 13, 2026 3:36am |