Organization and sites

An organization is the tenant containing your users and business data. A site identifies a factory or location. An environment is a workspace within that site, such as Production or Test. Operational scope is the combination of organization, site, and environment.

Prerequisites

Open Admin → Organization with organization management permission to make changes. Reading and managing are different permissions. Confirm the organization before editing shared settings.

Edit organization details

1. Open the organization profile section.
2. Review name, website, address, telephone, and email.
3. Edit the relevant fields and save.
4. Reopen the section to confirm the saved values.

These details are used in administration and invitations. Personal profile settings belong to your account, not the organization profile.

Create or edit a site

1. Open Sites and environments and choose Add site, or edit an existing site.
2. Enter the site name, stable key, and description. A key can be derived from the name when omitted.
3. Review regional settings: timezone, language/region, unit system, currency, start of week, date format, and time format.
4. Save. A new site and its managed Production and Test environments are created together. Your current workspace stays selected; choose the new site explicitly when ready.
5. Assign the appropriate people, groups, work centers, and connections before using the site operationally.

Changing regional settings does not translate record names or convert already stored quantities and currencies. Use explicit units and unambiguous dates in imports and integrations.

Environments and removal

Use the site's environment controls to edit workspace details and safety policies. Physical site and environment removal is unavailable: activity can start while an empty workspace is being checked, so removing its container could strand records. Existing data and access remain available. Do not remove operational records simply to retry this action.

The Options section currently describes planned controls. Those cards are not editable retention, governance, or integration policies. Use the dedicated configuration pages for settings that are actually available.

Use Release → Between environments… to choose a source and target within the selected site, including custom environments. Permissions are checked for both exact environments. Review changes, dependencies and target conflicts before transferring. The managed Test/Production shortcuts and Test reset remain available. Transfers between different sites are not supported. All these workspaces use the same deployed Ennea software; validating a new Ennea software release requires a separate deployment environment.

You can also ask Konnie to compare or transfer configuration, for example “Prepare this routing for Production from Engineering.” She resolves the named environments and shows Review transfer in the conversation. The review loads current changes and permissions; use its transfer button to apply them. The workspace selected in the global site menu stays unchanged, and orders, stock, conversations and memories stay in their own environments.

External actions in Test and other non-Production environments

Integration requests and physical printing are disabled by default in non-Production environments. Configuration previews remain available. Production continues to use its configured live bindings.

An organization manager can edit the environment and choose External actions → Approve bindings. Saving approves the Integration and printer bindings currently configured in that exact environment. These actions can reach real external systems and printers. Review the approval version and binding counts; new or changed destinations, credentials, printer configurations, or publications require renewed approval through Approve current bindings on save. Saving an unrelated environment detail does not renew approval.

Choose Disabled and save to block further dispatch, including work prepared earlier. A print attempt already sent can have an uncertain outcome; disabling does not undo completed effects. Configuration promotion never copies this approval, credentials, endpoints, printer assignments, or bridge identity into the target environment.

Work in the correct scope

Search for a site or environment in the header; the results are grouped by site and show whether external actions are disabled, explicitly approved, or live. A successful switch reloads the workspace, so save any work you want to keep before switching. Failed selections stay visible and can be retried. Each tab retains its confirmed context, so check every tab before changing records or approving work. Switching scope changes what you can access; it does not move data or promote configuration.

For transferring configuration see Publishing and governance. For permissions see Roles and permissions. For reusable physical resources see Work centers and sites.