Workspace System Configuration & Governance
System Configuration allows administrators to define core workspace settings that affect how the platform behaves for all users. These settings ensure consistency across projects, reports, scheduling, and daily usage.
As part of the AXQA Execution Intelligence Platform, system configuration centralizes workspace-level governance, ensuring consistent time alignment, reporting standards, and execution behavior across all projects.
Why it matters
- Ensures all users operate under the same regional and system rules.
- Prevents confusion caused by time or format differences.
- Centralizes workspace-level preferences in one place.
- Maintains consistency across reports and executions.
What can be configured
- Workspace language.
- Time zone settings.
- Default system behavior preferences.
- Core workspace identity information.
Note
These settings apply globally within the workspace and impact how timestamps, scheduling, and reports are displayed.
How it works
- An administrator accesses General Settings.
- System-level configuration options are displayed.
- Changes are saved and applied across the workspace.
- All users experience consistent updated behavior.
Impact on execution & reporting
- Execution timestamps follow the defined time zone.
- Scheduled automation aligns with workspace time settings.
- Reports reflect unified formatting.
Note
Unified configuration prevents discrepancies in timestamps, scheduling logic, and report formatting across distributed teams.
Best practices
- Configure time zone before scheduling automated runs.
- Align workspace language with team preference.
- Review settings after major organizational changes.
Common mistakes
❌ Ignoring time zone configuration
✔ Always confirm correct regional settings before execution cycles.
❌ Allowing frequent system-level changes
✔ Limit configuration edits to authorized administrators.
Security & access
- Only authorized administrators can modify system configuration.
- All changes apply at workspace level.
- Configuration updates do not affect historical execution data.
Related documentation
- License & Plan Visibility
- Server Status & Storage Monitoring
- Security & Execution Permissions