Custom role per user in group conversations
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
[!TIP]
Help move this idea forward
- Use the 👍 reaction to show support for this feature.
- Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers.
- Subscribe to receive notifications about status changes and new comments.
I manage a Nextcloud instance used by a large number of people, and one recurring issue I've noticed is that members of bigger groups often don't know who does what. When a user needs help with a specific topic, they have no easy way to identify who the right person to reach out to is, unless they already know each other personally.
WhatsApp addressed this exact problem with a simple feature: users can set a custom tag for themselves within each group. For example, I could appear as "System Admin" in one group and "Programmer" in another. These tags show up near the user's name in the conversation, making it instantly clear who does what.
Proposed behavior
- Each user can set a short text tag per group ("System Admin", "Designer", "Support")
- The tag is scoped to that group, the same user can have different tags in different groups
- The tag is visible to all group members, displayed near the user's name
- Group admins could optionally restrict or moderate the tags
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by breaking down the proposed per-group tag behavior and its optional admin moderation, then confirm the implementation covers setting, group-specific scoping, visibility to members, and the stated administrative controls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100