is it possible to automate the creation of a Retool user with an editor role as Collaborator in Github repo?
Otherwise whenever a user is onboarded and can create workflows/resource/apps can't protect them in the githubrepo, because the PR is managed on the Github Repo itself not within Retool.
Is it something out of the box between the Retool App in Github and Retool? or is something that has to be built manually? The alternative is to add manually all new users as collaborator in Github
If your on the enterprise plan you can use the Retool API users endpoint:
If your using some other OIDC/SAML provider, you can usually find some sort or event/trigger system to use when new users are added. For example, auth0 lets you make Post-User Registration Triggers
you could also manage a mapping of retool ids yourself in the Retool DB. Create a new table named 'my_verified_users' with number columns named 'retool_id' (no default, required) and 'mapped_id' (auto increment default, not required). Next, create a workflow named 'get_or_create_user` that takes a number as input then checks your table to either get the 'mapped_id' given a 'retool_id' or insert a new row then get the 'mapped_id'. after inserting a row you can insert a block to call the Github API and either trigger an Action Workflow or create/manage users with just API calls. on any app you can now trigger this workflow on app load and it will create a Github user for every Retool user (we know the user has created a retool account and logged in at this point, so we just want the first thing done to be a simple upsert that returns the affected row)
Short answer is that the functionality you are describing is not a native feature currently
The longer answer is that the process can be built using Retool as @bobthebear describes.
There are some options for role mapping and using tools from auth providers for enterprise teams. As well as a plethora of options for setting up a workflow automation that can send over user data to the GitHub API to give the user the necessary permissions.
Is your title say that you are on the Teams plan? Let me know if any of @bobthebear's suggestions would work for your use case and we can help answer more questions about setting that up!
ok thank you I will investigate internally the Post-User Registration Trigger, or if we have other processes in place. As last resource, we can try with github api integration.
