Users
- Communication
  - Work with mail
- Finance
  - Configure OSS and IOSS for direct sales
- CRM
  - Use case context
  - Report a problem from the backend
  - Sync Workspace contacts with CardDAV
- Operational workflows
  - Inventory and shipping
    - Plan a warehouse structure graphically
- PIM
  - Maintain a product variant's customs and origin record
- Collaboration
  - Use the groupware calendar
- Knowledge management
  - Knowledge management boards
- Online stores and Commerce
  - Manage delivery dates and delivery notices
Administrators
- Deployment
  - Server installation
  - From the Docker demo to the first live site
  - Start the Docker demo
  - Set up a local storefront domain
- Operations
  - Run product updates without manual repair
  - Recover from critical runtime failures safely
  - Understand the EULA and commercial host status
  - Control sources for Workspace Sites
  - Find slow requests with performance diagnostics
- Operations and security
  - Rotate the root key safely
  - Blob v2 key inventory
  - System artifact releases
  - Workflow recovery
  - Workflow retention and archives
  - Taskstream history and retention
  - Taskstream job capabilities
  - Monitor Taskstream and filter jobs
  - Prepare the Taskstream runner safely
- Security and access
  - Tenants, user accounts, and the System view
  - Create a tenant
- Communication
  - Provide mail through an SMTP gateway
- PIM
  - Use price-list logic code
  - Deliver product cards as ready HTML
- Commerce
  - Configure EU VAT for B2C and B2B
- Collaboration
  - Manage the groupware calendar
- CRM
  - Control case creation and workflow access
- Tools and diagnostics
  - numin
  - Diagnose order placement
  - Understand system domains
- Compliance
  - Manage packaging compliance
- Integrations and communication
  - Review and publish a CMS site
  - Set up an EDIFACT trading partner
  - Operate B2B Exchange
- Workflows
  - Upgrade Opportunity workflow instances safely
- App Platform
  - Manage app subscriptions and entitlements
Developers
- Integrations
  - Develop and publish Sites
  - Integrate the mail API and gateway handoff
  - Integrate the groupware calendar
  - Connect sync and domain services to app entitlements
  - Request workflow transitions idempotently
- API and CLI
  - Set up the Workspace Android SDK
  - Set up a Workspace machine SDK
  - Discovery and resources
  - Understand and introduce EDI/EDIFACT
  - Work with EDIFACT as a developer
  - Integrate the B2B Exchange Partner API
- Websites
  - Publish product sitemaps
- Commerce
  - Use the Sitegenerator standard cart

Understand system domains

This reference explains the System Domains (CSV) field shown during server setup. Use it for administration hosts, not for public sites or Storefronts.

In this label, CSV means a comma-separated list of hostnames. The field is not a CSV file upload.

Enter system domains

Enter every hostname that should open the administration interface before a tenant is selected:

text

localhost,workspace.example

Use hostnames only. Omit the scheme, port, path, and trailing slash.

Incorrect	Correct
`https://workspace.example/`	`workspace.example`
`workspace.example/docs`	`workspace.example`
`https://workspace.example:443`	`workspace.example`

Keep tenant domains separate

A system domain identifies the global administration entry point. A tenant domain belongs to one tenant, is verified through DNS, and can bind to a public site with the cms_public surface.

Host type	Purpose	Configuration
System domain	Administration interface before tenant selection	`System Domains (CSV)` during setup; comma-separated hostnames, no file upload
Tenant domain	Public site or Storefront for one tenant	Tenant-domain registration, DNS TXT verification, and site domain binding

Do not add a Storefront host to System Domains (CSV) as a workaround. For the local Docker path, follow Set up a local storefront domain.

The Docker demo preconfigures its administration URL through NUCLEUS_PUBLIC_URL. You normally do not enter another system-domain list for localhost.alvine.dev during that guided setup.

Verify the result

The configuration is correct when the administration host resolves, its TLS certificate covers the hostname, and Workspace recognizes it as the global administration entry point. Public site hosts remain registered in their business tenants.

For production TLS and proxy configuration, continue with Server installation.