# Understand which settings are preferences and which need enforcement

Canonical: https://savrn.com/cloud/settings

SAVRN Cloud · Coming soon. Public documentation and a browser simulation are available; connected services are not yet available.

A workspace setting can express what a team wants without proving that an execution service enforces it. SAVRN Cloud’s preview makes that distinction visible through local naming, retention and placement preferences. It also provides session export and reset. Connected policy enforcement and hosted workspace administration are Coming soon.


## Configure the demonstration workspace

Use Settings to change the workspace name, proposed retention choice and preferred placement, then save the local preferences. These values persist in the browser profile with the rest of the preview state. They are useful for exploring configuration and language, but they do not create an organization account or apply policy to an external service.

## Read retention as a proposed policy

The displayed retention options illustrate a future administrative choice. Selecting one does not schedule deletion of browser data, artifacts or external resources. A connected retention control would need a defined scope, enforcement process and evidence covering relevant storage, logs and backups. Exceptions and deletion failures would also need an appropriate operational response.

## Treat placement as an eligibility decision

A preferred region or infrastructure type is an input to a future decision, not proof of where processing occurs. A qualified placement must account for compute, storage, logs, access and the workload’s approved conditions. If no eligible option is available, the service needs an explicit outcome rather than silently substituting a different destination.

## Export or reset with the scope in view

Export demo session preserves labeled local records for inspection. Reset demonstration restores the starting fixtures after confirmation. This affects the preview workspace, not supplier infrastructure or a hosted account. In a connected release, administrative changes and destructive actions would need appropriate authorization, clear consequences and a durable audit record tied to the resources actually affected.

## What you can explore today

Save browser-local preferences, export a labeled session or reset the demonstration state.

## Before this service launches

Hosted settings require authenticated administration, enforceable policy controls and auditable effects across connected resources.

## The customer outcome

The intended outcome is configuration that clearly distinguishes a team’s requested policy from the observed and enforced behavior of a connected service.

## Related documentation

- [Data and approval policy](https://savrn.com/cloud/docs/platform-data-policy)
- [Changelog and operational status](https://savrn.com/cloud/docs/resources-changelog-status)
- [Deployment and trust matrix](https://savrn.com/cloud/docs/trust-deployment-matrix)
- [Explore workspace settings](https://savrn.com/cloud/console/#/settings): Inspect local preferences, export and reset controls.