A Cloud Environment is a collection of templates, images and is used when generating documents using those items. Environments allow users to separate and partition their work into logical groups.
A single Cloud Account can have multiple Environments.
- a "Sandbox" Environment could be used for experimenting with template features and developing new templates
- a second "Live" Environment could be used to store templates that have been tested and are actively being used
Environment and Processing Location
Environments are global and can be used in any Processing Location, either via the API or the Cloud Console.
Any templates and images uploaded to an Environment are stored using the Processing Location used for the upload. When you change Processing Locations you will only see the templates/images stored in that location for that Environment.
An Environment can have multiple API Access Keys. When generating documents via the API you must:
- use the correct Environment (by using an API Key specific to that Environment)
- use the correct Processing Location (by using the correct Base URL for that location).
Environment Quota and Usage
When creating an Environment you will need to allocate an Environment Quota, which is the maximum number of pages that can be generated in a month in that Environment.
All documents generated in an Environment, either via the Cloud Console or the API, create usage statistics for that Environment. From the Usage page in the Cloud Console users can view the number of documents and pages generated in each Environment.
Note: Ensure that the correct Environment is selected (top left) when viewing Environment Usage.
An Administrator can disable an Environment, which prevents any new work being done in that Environment, such as: template uploads or documents being generated.
Templates can still be downloaded when in an Environment is in a disabled state. Before an Environment is permanently deleted, it is recommended to disable an Environment to be certain it is not being used.