Organization Settings And Config Transfer
Organization settings define the baseline behavior for everything your team does in Incido — the default language for public communication, the languages available for translations, and operational parameters like email sending state and data cleanup scheduling. These settings apply across all status pages, incidents, and maintenances within your organization.
What gets created when you register
When you create a new organization, Incido provisions a complete working environment in a single step. You provide the organization name and a list of your service components, and the system creates everything you need to start communicating:
Default incident statuses and transitions (Triage, Investigating, Active, Monitoring, Resolved, Closed), default maintenance statuses (Draft, Scheduled, In Progress, Post Maintenance, Cancelled, Closed), a set of severity levels (Critical, Major, Minor, Trivial), your components, a default theme with an active version, and a default status page linked to everything.
This means you can create your first incident or maintenance immediately after registration without configuring anything else. The defaults are designed to be practical out of the box, and you can customize them as your needs evolve.
Locale and language settings
The default locale controls the primary language for public-facing content on your status pages and in subscriber emails. It defaults to en_US but can be changed to match your audience. The locale also determines the default language for translatable fields like incident titles, status names, and severity level descriptions.
Additional languages allow you to provide translations alongside the default language. When configured, operators can enter translated content for titles, summaries, and other public-facing text. The default language is always included — additional languages extend the set, they do not replace it.
Language settings affect rendering across all your status pages and email notifications, so changing the default locale is a significant decision that should be coordinated with your team.
Configuration import and export
For organizations that manage multiple environments (staging and production, regional instances, or client-specific tenants), Incido supports exporting and importing configuration as ZIP archives where this capability is available in the workspace.
Exporting creates a snapshot of your organization's configuration for selected domains such as statuses, workflows, severity levels, themes, and components.
Importing applies a configuration archive to a target organization. You can run the import in dry-run mode first, which validates the archive against the target organization without persisting changes. This lets you verify compatibility before committing.
For status pages specifically, import can either update an existing matching page or create a new one, depending on the selected mode. Use dry-run results to confirm the outcome before applying changes.
Be deliberate with configuration transfers. An import can change many workflows simultaneously — statuses, themes, severity levels, and component structures all at once. Always use dry-run mode first, and review the results before applying to a production environment.
What changes on the public frontend
Locale changes affect the language of rendered content on all your public status pages and in subscriber emails. If you change the default locale, previously published content remains in its original language, but new content and system-generated labels will use the new locale.
Configuration imports can alter public status page behavior significantly — component structures, status labels, theme settings, and severity levels can all change in a single operation.
Operational effects
Organization-level defaults influence every downstream communication workflow. Locale and language choices shape how Incidents, Maintenances, and Status pages appear to customers. Configuration transfer can update several of those surfaces at once, so teams should validate in non-production environments before applying broad changes.
Troubleshooting
Content appears in the wrong language. Check the default locale in organization settings. If you recently changed it, new content uses the updated locale while previously published content retains its original language.
Import fails in dry-run. The archive may reference resources that conflict with the target organization's existing configuration. Review the dry-run output for specific conflicts and resolve them before retrying.
Status page keys do not match after import. If you used "create new" mode, the import generates new keys and reports the mapping. Update any external integrations or DNS configurations that reference the old keys.