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.
|Use this default environment, and it’s associated test API keys, as you build with Flatfile.
|When you're ready to launch, create a new environment and swap out your keys.
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.
guestAuthentication be left unspecified, both
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.
Secret and publishable keys
All Accounts have two key types for each environment. Learn when to use each type of key:
|On the server-side: Store this securely in your server-side code. Don’t expose this key in an application.
|On the client-side: Can be publicly-accessible in your application's client-side code. Use when embedding Flatfile.
The publishable key only has permissions to create a Space.