I was hoping to treat Rocket.Chat as a classic chat room by allowing the channel removal to be fluid. Is it possible to set where if the last user leaves the channel then it gets removed automatically? Currently, the owner of the channel can’t leave the channel so the channel is always going to stay and owner is always the last person in the channel. Can someone explain to me the logic behind not letting the owner leave? Also, why can’t the user delete his/her own public channel? The keyword I’m looking for is to make channels ‘disposable’. Thanks.
Hi renderlogic! Welcome
Before anything, it’d be beneficial for us to know a bit more about your setup.
Please follow our guidelines for reporting issues:
Have you tested this on the latest version?
I just opened one of my test servers running RC 3.16.0, and I can clearly see a
delete button for the channel I created (non-admin). See screenshot below -
I probably am not the best person to answer this question. But one reason I can guess, is that by not letting an owner leave a channel, RC essentially makes sure that no stray channels are left on the server. Think about this, if one were to be allowed to create and leave a channel just like that, you’re going to end up having a bunch of channels that neither you’re a part of, nor can you delete without messing around the internal schema itself.
Unfortunately, I don’t think so. Maybe a feature request? I’ll confirm with one of my colleagues first.
I presume a channel could theoretically have no owner, but that means someone could take ownership that you might not want. I think there is some discussion on this in old github issues so worth a good read there.
Remember that Rocket is used in a corporate environment and channels often need to be preserved for data purposes. So automatic removal would need to be an admin decision.
Potential feature request, though it may have been asked before so needs a good search.
Deleting the channel, yes, I admit I derped on that one. It was pretty hidden but I guess there’s a purpose for that to prevent accidental deletion.
As for the ‘disposable’ room and owner unable to leave the room, it makes sense. I’m now wrapping my head around Rocket.Chat’s corporate model, which is more about collaboration through ‘chat’. I was trying to treat it as an IRC chat service.
No worries - no need to @ us as we read everything
I’m now wrapping my head around Rocket.Chat’s corporate model, which is more about collaboration through ‘chat’. I was trying to treat it as an IRC chat service.
It is collaboration, and a lot more. For sure you can use it pretty well like like IRC, but you can do a lot more too.
But think about Rocket underpinning all communications - see Omnichannel etc. It can be almost a communications bridge.
There is an IRC bridge too - I keep trying to get one setup to my own server but never find enough time!