Environment-level access control

You can now lock down specific environments so only designated users can make changes.

Restricted environments let admins control who can modify deployments, autoscaling settings, and other configurations in sensitive environments like production. Users without access retain full read access and can still call inference endpoints.

To get started, head to Settings → Environments and set any environment to Restricted. For more information, see Restricted environments.

Updated terminology

We've also updated some of our terminology:

• Workspace → Organization: What was previously called a "workspace" is now an "organization."

• Creator → Member: The "creator" role is now called "member."

No action required, these changes don’t affect permissions or functionality.