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

Multi-tenant structure #4

Open
cyri113 opened this issue Dec 5, 2023 · 0 comments
Open

Multi-tenant structure #4

cyri113 opened this issue Dec 5, 2023 · 0 comments
Assignees

Comments

@cyri113
Copy link
Contributor

cyri113 commented Dec 5, 2023

We have a platform object in our mongodb database. This is confirmed by the community manager in TogetherCrew.

{
  _id: ObjectId(''),
  name: "telegram",
  metadata: {
    id: "1234567789", // telegram channel id
    name: "Some channel name", // telegram channel name
    // other data required?
  }
}

In neo4j we will store the extracted data. Each data object should store the telegram channel id so that it can be indexed and queried.

Questions

  • What is the user flow for adding a bot?

The telegram channel administrator will need to add the our bot to the channel. Then they add the channel id on the TogetherCrew app. Note: this is a potential security vulnerability. Once our bot is added to the group, we need to verify that the user adding the group is an admin of the group.

  • How can we assure that right community is getting the right data?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants