This question may not belong here, and I’m happy to be redirected.
I set up a DamlHub account for our primary developer, so they could do exploratory dev work. They built out a small project, did some testing, and now we’re looking at setting up a QA environment, Prod, etc., and bringing other developers into the work.
We’d like to set up the account in a way that allows the following:
-
Developers should be able to administrate their general environment. Create a new project, set up ledgers in that project, etc. This is the application management and infrastructure layer.
-
Developers should not be able to manage the corporate credit card on the account, add people who can also create projects, or otherwise manage the top-level account. This is the corporate infrastructure and security layer.
-
Each developer should have their own user account, password, and API tokens.
I don’t see any way to do that, and I wasn’t able to navigate the documentation very well. What I see is that you sign up for an account on DamlHub (with a corporate email in this case), and that email is the only way to manage the account, any projects in it, etc. There appears to be no way to differentiate between the person paying for the service and the person building an application on the service.
For that matter, it does not look like you can have more than one developer on the project without sharing the password.
Am I missing something obvious? Is there a best practices pattern for managing the account and projects in DamlHub?