Is it possible to create a channel in Slack and set the default notification preferences for (other) new users joining the channel?
I need this in order to automatically join to certain channels users with relatively low technical skills, but to have the notifications automatically muted for that channel so that it doesn't annoy them too much.
I believe you're looking for this:
https://{your_slack_team}.slack.com/account/notifications#channel_specific_settings
Related
I'm a member in a MS Teams channel which sends some notification messages, is there's a way to automatically forward these messages from that channel to another channel of my own.
Thanks.
I would recommend you have a look at Automate with Microsoft
Accept the question if this helps you but please read the docs of Power Automate carefully :)
Is their any event apart from bots to listen to channel deletion in teams.
So that I can perform some actions on channel deletion.
Currently I could see only bots can handle such events.
Bots are one way, but this should also be possible using the Graph - specifically there is a Change Notification capability, as per https://learn.microsoft.com/en-us/graph/teams-changenotifications-team-and-channel . Per this doc:
You can get notified whenever a team or channel is created, updated, or deleted.
Idea is to send notifications to users with direct messages. Because of that notification only bot need to be implemented. Reading documentation of MS Teams leads to information that we have 15000 across all threads in a data center (across multiple tenants).
Didn't find what are consequences when you hit this limits too often. Of course throttling mechanism need to exists, but with this limits I am not sure how to handle a large number of notifications I need to send from one bot across multiple clients(to be considered one bot per client if that is allowed to avoid this limit per data center for all).
Or any other idea how to handle notifications from one producer through bot to multiple consumers of those notifications on different addresses?
Is there any different pricing plan if you want to extend limits?
I'm using spring's imap mechanism in order to recieve emails from my account into my server.
this works like a charm.
Anyhow, a new requirmemnt came up - instead of listening to a single email account i will have to listen on a multiple number of accounts.
Iv'e tried creating a new channel for each of these account. it WORKS!
problem is that each channel i added meaning a new thread running.
since i'm talking about a large number of accounts it is quiet an issue.
My question is:
Since all the email accounts (I would like to listen to) are in the same domain i.e:
acount1#myDomain.com
acount2#myDomain.com
acount3#myDomain.com
....
Is it possible to create a single channel with multiple accounts?
Is there any alternative for me than defining N new channels?
thanks.
Nir
I assume you mean channel adapter, not channel (multiple channel adapters can send messages to the same channel).
No, you can't use a single connection for multiple accounts.
This is a limitation of the underlying internet mail protocols.
If you are using imap idle adapters, yes, this will not scale well because it needs a thread for each. However, if you are only talking about a few 10s of accounts, this is probably not an issue. For a much larger number of accounts, it may be better to use a polled adapter.
But, even so, unless it's a fixed number of accounts, the configuration could be burdensome (but you could programmatically spin up new adapters).
For complex scenarios like this, you may want to consider writing your own "adapter" that uses the JavaMail API directly and manages the connections in a more sophisticated way (but you still need a separate connection for each account). It wouldn't have to be a "real" adapter, just a POJO that interracts with JavaMail. Then, when you receive a message from one of the accounts, send it to a channel using a <gateway/>.
I have a simple messaging system on my site. I would like to implement limits on messages. For basic users, users can have store a maximum of 250 messages in their inbox and supporters can store a maximum of 3000 messages.
My question is about the UI aspects.
If a basic user already has 250 messages:
would you block another user from being able to send them a message until they have deleted some messages?
Or would you put the new message in a queue and not show it until a user has deleted some messages?
Would you tell them they have new messages waiting but they can't read them until they've deleted some messages?
What would be your approach?
I would suggest an automatic delete that the oldest messages are automatically removed when newer messages arrive.
Edit: See comment below.
Also, besides this method, you could make a way to save some messages or make them favorite to prevent auto-deleting them.