Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: workspaces versus resource tags for env separation #548

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/administration/concepts/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -398,3 +398,10 @@ may take a minute or two before the new limits apply.
### Related content

- Tutorial on how to [optimize spend](./tutorials/manage_spend)

## Best Practices

### Environment separation

Use resource tags to organize resources by environment (e.g. `dev`, `staging`, `prod`). We will be releasing attribute based access control (ABAC) in the near future, which will enable fine-grained permissions based on resource tags.
We recommend the use of workspaces when you need strict isolation of resources (e.g. different teams who legally cannot see each other's data).
Loading