Deslicer Enterprise docs
Deslicer

Chapter 8: Post-install configuration

← Back to Index | Previous: Install DAP | Next: Network and firewall →


8.1 Where operators configure the platform

After Deslicer AI is up, most engagement settings are completed in Control:

https://<dai-host>/control

End users use https://<dai-host>/. Keep those roles separate when writing runbooks.

  1. Confirm TLS (Chapter 6)
  2. System settings — SMTP for invites and notifications
  3. AI models and keys — provider credentials for chat / agents
  4. DAP — enroll and verify (Chapter 7)
  5. Registry — platform integration when not already seeded from the provisioning package
  6. Web certificates — revisit ACME/PEM if DNS or certs change
  7. Updates — use Control → Updates for Deslicer AI images, DAP images, and the DAP install package (Chapter 5 §5.7, Chapter 7 §7.5)

8.3 SMTP

Configure your corporate SMTP relay in Control system settings. Until SMTP works:

Use TLS to your relay as required by your security standard. Store credentials only in Control / secret stores—not in ticket text.

8.4 AI models and keys

Add provider API keys (for example OpenAI, Anthropic, Google) in Control under AI models / keys for your engagement. Control and install tooling apply keys so chat completions succeed after save.

Test with a simple chat from the main application after saving keys.

8.5 Registry integration

If the Registry API key was not applied automatically from the provisioning package, configure the Registry platform integration in Control using the key from your handoff. This is separate from the Nexus username/password used for Docker pulls during install.

8.6 DAP backend hygiene

In Platform integrations → DAP:

8.7 Operational backups

Agree a backup plan with Deslicer for:

When retiring a host, reverse install order: uninstall DAP (§7.10), then Deslicer AI (§5.8).


← Back to Index | Previous: Install DAP | Next: Network and firewall →