Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fetch member belongs to an organization #114

Closed
nguyendn opened this issue May 15, 2018 · 2 comments
Closed

Fetch member belongs to an organization #114

nguyendn opened this issue May 15, 2018 · 2 comments

Comments

@nguyendn
Copy link

From what I know, if we want to send 1:1 message to all members of an organization, we need to do so:

  1. Create a team which include all members
  2. Add a bot to that team
  3. The bot will fetch team rooster and start 1:1 dialog

connector.fetchMembers(serviceUrl, conversationId, function (err, result) {}

Is that the only way? Can we just register a personal bot for all members by Team Admin?

@billbliss
Copy link
Contributor

That is currently the only way, yes.

We have been looking at ways to make "proactive messaging" (that's what we call this) simpler but that's not available yet.

When we do, there will need to be controls over the scenario you describe - tenant administrators will want the ability to monitor and disable scenarios such as this because otherwise it's yet another vector for spam.

@nguyendn
Copy link
Author

Thank you!

@ghost ghost locked as resolved and limited conversation to collaborators Sep 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants