Learn how to use Environments for testing and authentication.
Environments are isolated entities and are intended to be a safe place to create and test different configurations. Environments serve as self-contained, secure domains where diverse configurations can be created and tested. By default, a development and a production environment are set up.
The development environment does not count towards your paid credits.
Environments support two types of guest authentication:
magic_link: This method dispatches an email to your guests, which includes a magic link to facilitate login.shared_link: This method transforms the Space URL into a public one, typically used in conjunction with embedded Flatfile.Should the guestAuthentication be left unspecified, both magic_link and shared_link types are enabled by default.
It’s important to note that guestAuthentication settings can be applied at both Environment and Space levels. However, in case of any conflicting settings, the authentication type set at the Space level will take precedence over the Environment level setting. This flexibility enables customization based on specific needs, ensuring the right balance of accessibility and security.
All Accounts have two key types for each environment. Learn when to use each type of key:
The publishable key only has permissions to create a Space.