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

[Feature Request] Share bots with users without sending a link #291

Open
1 of 2 tasks
DTheunis opened this issue May 3, 2024 · 4 comments
Open
1 of 2 tasks

[Feature Request] Share bots with users without sending a link #291

DTheunis opened this issue May 3, 2024 · 4 comments
Labels
needs-info Need more information such as reproduction step stale Issue labeled as stale will be closed automatically

Comments

@DTheunis
Copy link
Contributor

DTheunis commented May 3, 2024

Describe the solution you'd like

We'd like to create accounts and have them access to default bots, without having the need to send links and make them chat with the bots. It's a tedious process that we would like to take away from endusers.

Why the solution needed

Easier way of using public bots for our users.

Additional context

I created a PR with the necessary code already, this makes it possible to use an API call to share a public bot (owned by the user executing the api call) with any other user.

This suffices for us - we can create Lambdas that utilize this API call - I don't plan on creating a frontend for this.

Implementation feasibility

Are you willing to discuss the solution with us, decide on the approach, and assist with the implementation?

  • Yes
  • No
@statefb
Copy link
Contributor

statefb commented May 7, 2024

Thank you for considering this request. Regarding the public link click feature, I don't find it overly inconvenient. Could you please elaborate on the specific scenarios you have in mind where this feature might pose challenges?

Additionally, frontend should be implemented on this case. We can support implementing frontend, but please let you know about our policy. Our approach is to ensure that both the backend and frontend implementations are completed for any new functionality. We believe that all features should be driven by clear user stories, and leaving code in an incomplete state can compromise maintainability. With this context in mind, I would appreciate if you could explain why implementing this feature would be more convenient compared to the public link click feature.

@statefb statefb added the needs-info Need more information such as reproduction step label May 7, 2024
@DTheunis
Copy link
Contributor Author

DTheunis commented May 7, 2024

For our use case it's simply because we think it's a bit tedious for users now.
We have some bots that we want to make available by default for users
Because currently: A user has to log in with a new user, click a few links of shared bots, talk to each of them to make them show up in the shared list.

What we can do with the api call I made now is:
Create a user in Cognito - Add bots to that user so that when the user logs in, he has a list of bots ready and prepared.
This makes it possible to (as I've set it up now), run a lambda for a user to give that user instant access to about 5 public bots that we have prepared for them to use.

So the user can just login and start using bots made available to him - compared to the current situation where he has to log in and use links first.

As for frontend:
It could be possible to use this when clicking the share button - that you can also provide specific users. Or in the Admin Dashboard so that the admin can assign bots to users.

@statefb
Copy link
Contributor

statefb commented May 8, 2024

Thank you for explanation. Actually our team is considering to add GPT store like feature, which might be what you want. The things we should take care should be:

  • Be searchable (by category, keywords, etc...)
  • Rating feature (It enables to bot creators to improve their bots)
  • Access control (Not only for access permission to the bot, we also need to care the permission to the document, which might requires meta data handling for the data source)

If you have any additinoal requirements, please let me know.

@github-actions github-actions bot added the stale Issue labeled as stale will be closed automatically label Jun 7, 2024
Copy link

github-actions bot commented Jun 7, 2024

This issue has been labeled as "stale" due to no response by the reporter within 1 month (and 14 days after last commented by someone). And it will be closed automatically 14 days later if not responded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-info Need more information such as reproduction step stale Issue labeled as stale will be closed automatically
Projects
None yet
Development

No branches or pull requests

2 participants