[Feature] Automate Instance management & User Onboarding with authenticated access to Appsmith service APIs

[infinitetrooper]

Users would like to automate certain Appsmith tasks by integrating them into their workflows. This can be done by allowing authenticated access to certain Appsmith service APIs.

Use cases

1. Create, update, and delete users and groups.
2. Periodically read audit logs into existing ETL processes.

[infinitetrooper]

User Request

Hi, can I use the REST APIs of appsmith to automate some of my appsmith setups more easily? My use case: I have multiple appsmith instances running in multiple countries. I need to perform these things in every instance:

1. Update user roles, groups, and permissions
2. Update brand color
3. Other admin settings.

I want to have a single script that I can apply to all my instances.

[geekyme-fsmk]

Likewise - I need to create scripts that do this Create, update, and delete users and groups. since I have multiple appsmith instances to manage.

[infinitetrooper]

@geekyme-fsmk - You can use our SCIM API protocols to do this. We will publish the API reference soon but, if you follow the SCIM 2.0 protocol for CRUD on users/groups with the API key generated in the SCIM configuration screen, you should be able to manage users and groups through a script.

[infinitetrooper]

Another user request Slack thread.

[Eudod]

Hi! I am interested in pushing audit logs to external platform, i.e. ELK, Splunk or similar. The reasons for that are:

• Search capabilities in the existing audit logs are quite limited.
• For compliance purposes we may need to store the logs for more than Appsmith allows (1 year)
• Having logs within Appsmith server / environment may have storage & performance impact on the platform

Please consider this in your planning. Thanks!

[holylander]

I also subscribe to all these features, as

• Update user roles, groups, and permissions
• Create workspaces
• Update brand color and other brand settings
• Other admin settings.
• Make an application (linked to GIT) to pull from "main" branch ( and therefore, deploy the changes )

[infinitetrooper]

User Request on exporting Audit Logs | Slack

[dreece-surefire]

Another request here!

[ame-appsmith]

Another user requested this feature.

[mike-gigs]

Hello, our organization is adding on to this as we are looking for a way to programmatically manage users and access to our workspace. Our use case is that we want to control user access in the workspace, and have many users we would like to be able to see data made available through Appsmith. Since some of this data can be sensitive, we need the app to be private, but that means coordinating and managing the access for all of our users manually through the Appsmith front-end, and for some less technical users, walking them through the Appsmith invitation process.

[infinitetrooper]

Another User request from a prospect - DSV

[riteshkew]

Another enterprise user reported for this https://theappsmith.slack.com/archives/C068SJD7G4E/p1720703346128459

[kamal-buqaileh]

Hello there, It would be really great, if you could provide us with a solution that we can use to do the following:

• When creating a Workspace and/or an App

  • Create a set of roles automatically
  • Create a set of groups automatically
  • Add roles to groups automatically

  We would like to have the ability to write some logic somewhere to instruct AppSmith on how to create these roles and groups, this will reduce the time required to deliver an App to our users.

Also, we have multiple workspaces, with different setups, but we would like to have some users which acts as an admin for all workspaces and applications, past and future ones, without having to update the permissions for these users

[M4mu5qu3]

Likewise - we have business license and would like to manage users/groups/roles programmatically. Our use cases are:

• a team must be able to implement a logic from an external service to align users and their rights so that they will follow a centralized flow of authorization keeping all those rights in sync, to do this we should be able to access appsmith users, groups and roles through API or using CLI commands, even accessing directly the DB (having additional documentation)
• the security and compliance team must have access programmatically, in read only mode, to users, groups, roles and applications configured into appsmith, this, as the above one, can be achieved throughout API, CLI, DB access or structured text file export

All of those are urgent and blocking, without having security team to access it we cannot deploy applications in production environment since we would go out of compliance.