Configuring Default Imagery Product Types for Your Organization
Organization Managers: Learn how to define and manage default imagery product types for your organization’s tasking workflow.
Overview
Org Managers have the ability to configure which imagery product types are included by default when users in their organization submit tasking requests. These settings help ensure consistency across teams while still allowing tasking users the flexibility to tailor requests as needed.
What You Control
As an Org Manager, you can define the following for your organization:
-
Required imagery product types
-
Always included in every tasking request
-
Locked and cannot be removed by users (e.g., GEO is always required)
-
-
Optional imagery product types
-
Pre-selected in tasking requests
-
Users can remove or add other available types as needed
-
-
Unavailable imagery product types
-
Not shown as options for users in the tasking interface
-
Cannot be selected or added by tasking users
-
These settings can be managed via Console or the API.
Setting Defaults in Console
-
Log in to Console as an Org Manager.
-
Navigate to your Organization Settings.
-
Open the Imagery Product Types configuration section.
-
For each product type (e.g., SLC, GEC, SICD, CSI, CSIDD):
-
Mark as Required, Optional, or Unavailable.
-
-
Save changes to apply them to all future tasking requests submitted by users in your organization.
Behavior for Tasking Users
Once you’ve configured the default imagery product types:
-
Required types are automatically included and locked in each request.
-
Optional types are pre-selected, but users can add or remove them as needed.
-
Unavailable types do not appear in the dropdown menu and are not accessible to users.
All tasking requests will always include the GEO product type by default, as it is required for QA and processing integrity.
When Settings Take Effect
-
Your configuration applies immediately to all future tasking requests submitted after saving.
-
Users can adjust optional selections for individual requests until 3 hours before collection.
-
After that, imagery product types can only be changed through archive reprocessing.
Best Practices
-
Include the most commonly used product types as Optional to streamline user workflows.
-
Mark product types as Unavailable only when they are not relevant to your operations or should be restricted for compliance or workflow reasons.
Additional Capabilities
-
When reordering from the archive, users can request additional imagery product types even if they weren’t included in the original collect.
Need Help?
Refer to the Product Type Glossary for details on available imagery product types and their use cases.
For configuration support, contact our Customer Success team.