If we’re using api tokens, what’s the preferred way to handle different environments like staging and production? I would want to ideally create separate tokens based on what data they can access, but it looks like access control is not that granular. If I create a token with “shared resources” access, it basically gives access to everything that is shared. Should we be creating a different workspace instead?
Hi Kevin,
You’re correct in saying that API tokens have access based on shared/private resources, but we do have workspace-level tokens that can control access to individual workspaces instead of all shared resources. That being said, we also offer developer accounts if testing needs to be done, and that way the API token can be used for separate instances instead of workspaces, ensuring complete separation between staging and production.
Hope this helps!
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.