RocketChat / RocketChat/Rocket.Chat
Group or Channel Exit Permissions Management
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Today we have some standard groups and channels where users can not get out of them.
But we have other groups and channels that are created by ordinary users and that users can leave.
By analyzing the settings of not allowing groups to exit, it is defined globally. Our suggestion that it can still be set a global standard, but that when creating the group there is the option to define whether or not the user can leave that group.
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
The issue names no files, tests, or entry points; start by locating the global group/channel exit setting and the creation flows for user-created groups and channels. Done should mean each group or channel can define whether users may leave, while the global setting remains the default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authorization, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100