feat: Best practices guide (#551)

section that describes best practices around environment separation

docs/administration/concepts/index.mdx

@@ -176,6 +176,14 @@ Roles can be managed in organization settings under the `Roles` tab:
 
 For more details on assigning and creating roles, see the [access control setup guide](../how_to_guides/organization_management/set_up_access_control.mdx).
 
+## Best Practices
+
+### Environment Separation
+
+Use [resource tags](#resource-tags) to organize resources by environment using the default tag key `Environment` and different values for the environment (e.g. `dev`, `staging`, `prod`). This tagging structure will allow you to organize your tracing projects today and easily enforce
+permissions when we release attribute based access control (ABAC). ABAC on the resource tag will provide a fine-grained way to restrict access to production tracing projects, for example. We do not recommend that you use Workspaces for environment separation as you cannot share resources
+across Workspaces. If you would like to promote a prompt from `staging` to `prod`, we recommend you use prompt tags instead. See [docs](../prompt_engineering/concepts#tags) for more information.
+
 ## Usage and Billing
 
 ### Data Retention