1.4.3 Initial Settings — Defaults and System Behavior

Initial settings define how Praisma Hub behaves immediately after tenant creation. These defaults provide a safe, predictable starting point while allowing administrators to adjust configuration as needed.

Purpose of Initial Settings

Initial settings are designed to:

Ensure secure default behavior

Reduce configuration complexity

Provide consistent platform behavior

Prevent common misconfigurations

Defaults follow best practices for security, accessibility, and usability.

System Defaults

Upon tenant creation, Praisma Hub applies defaults such as:

Standard content workflows (draft → review → publish)

Conservative permission assignments

Enabled audit logging

Default accessibility-friendly UI settings

These defaults can be adjusted later by authorized administrators.

Module Configuration

Enabled modules and features are determined by:

Subscription or contract scope

Tenant configuration

Compliance requirements

Unused modules remain hidden to reduce complexity.

Notification and Communication Defaults

By default:

Critical system notifications are enabled

Workflow-related notifications are active

Users receive essential onboarding messages

Users can later fine-tune notification preferences within allowed boundaries.

Governance and Change Control

Changes to initial settings:

Require appropriate permissions

Are logged for audit purposes

Take effect immediately or per defined scope

This ensures predictable system behavior.

Summary

Initial settings in Praisma Hub provide a secure and consistent foundation. By applying sensible defaults and controlled configurability, the platform supports smooth onboarding and long-term stability.