Environments

What an Environment is

An Environment groups the resources and configuration for a set of Elyxis work. It owns Settings and Keystores and provides the scope for managing and running Apps. Each beta tester has a separate tenant with isolated databases and configuration, containing two Environments:

• Beta Testing: supplied sample data, configured connections, and prepared capabilities. Start here to try the scenarios without database setup.
• Sandbox: an empty Environment for preparing configuration and building capabilities from scratch.

An Environment is an Elyxis resource, separate from your laptop's operating-system environment variables.

Why the selection matters

Two Environments can use different service endpoints, model configuration, secret values, and access grants. The selected Environment determines which resources a request can inspect or change.

Requests use the Environment selected in your session unless you explicitly name another one. You do not need to include its name in ordinary requests.

At startup or after login, the CLI selects your only accessible Environment or asks you to choose from several. Confirm the selection at any time:

/context

To inspect the choices through the Assistant:

List the environments I can access.

To change the working selection, make the request explicit:

Use the Beta Testing environment for this session.

Review any confirmation, then run /context again. Use the exact displayed name or ID if names are ambiguous. /new starts a new Assistant session and repeats Environment selection; it does not create another Environment.

Access and permissions

Your administrator determines which Environments and actions you can use. Being able to see an Environment does not necessarily mean you can change its Settings, create Apps, or execute every capability in it.

Your role defines the actions available to you. Access to a particular Environment is managed separately, and can allow only some of those actions. Selecting an Environment does not grant access to it.

Permissions use plain-English action names. For example:

These are examples; your account may have a different set of permissions. Viewing, running, and changing a resource are separate actions.

If an action is denied, ask your administrator for the particular permission you need and name the intended Environment. Choosing a name in conversation or signing in again cannot add permissions.

Before a change

Check the Environment name, the affected resource, and whether the action creates, updates, starts, or runs something. Use Beta Testing for the prepared scenarios and Sandbox for a fresh setup. Changes to Beta Testing’s configuration may interrupt its scenarios. Ask the beta team for help restoring the supplied setup if needed.