+1
We chose Auth0 partly because “everything you can do in the UI can be done with an API and more”. This is mostly true, but not for tenant management.
We are running a SaaS product and automate the deployment/update of everything, like most customers I presume. Although we aren’t creating tenants every day, dev/test environments are spun up on-demand and will use a separate Auth0 tenant for isolation. Requiring manual intervention for Auth0 will be a pain.
Can the Deploy CLI tool be used before API support is added to export config, modify the export to add other tenant members and then re-import only the tenant members?
Thanks.