# Environments get their own allowances, and enterprise SSO too

25 October 2026. Each development or staging environment has its own monthly allowances and is never billed past them. Enterprise single sign-on (SSO), directory sync and company keys, which already work in production, now also work in development and staging environments.

## Added

- **Authentication:** Your team can now try a company's setup in a development or staging environment before changing it in production. Enterprise single sign-on (SSO), directory sync and company keys already work in production. Now they also work inside a development or staging environment, set up against your own WorkOS account.

## Improved

- **Billing:** A development or staging environment never adds overage to your bill. Each one has its own monthly allowances, and usage past an allowance is refused rather than billed. You can see them, read-only, under Limits in this environment.
- **Console:** Inside an environment, you can now see the sign-in apps BuildBase lends it and the platform sender. A Shared sign-in for testing card lists the lent Google and GitHub apps, and can add one back. The Senders page shows the platform sender, whether it is in use or standing by behind the environment's own sender.

Source: https://www.buildbase.app/changelog/environment-allowances-and-enterprise-sso-in-environments
