---
title: "Editorial policy"
description: "Sources, fact checking, AI use, and corrections for ConnectiveOne documentation."
---

# Editorial policy

This policy explains how the ConnectiveOne Documentation Team creates, verifies, and corrects public content.

## Sources

Product claims must come from a source that can be checked:

1. the current UI and actual behavior of a supported product version;
2. feature specifications and confirmation from the responsible product team;
3. verified support scenarios with customer-specific data removed;
4. official vendor documentation for an external integration;
5. public ConnectiveOne terms for support, privacy, and contractual topics.

Customer-specific materials, private dashboards, temporary files, and internal developer documentation are not public sources and must not appear in an article.

## Verification before publication

Before publication, the author checks:

- button, field, and menu names against the current UI;
- prerequisites, permissions, expected results, and common failures;
- internal and external links;
- parity between English and Ukrainian versions;
- absence of secrets, personal data, and internal customer names.

Content receives a separate editorial review. High-risk changes require confirmation from the feature owner or an engineer.

## AI usage

AI may assist with structure, language editing, finding gaps, and preparing a draft. AI is not a source of truth and does not publish content independently.

A human team member:

- verifies every factual claim against an available source;
- removes invented parameters, links, or promises;
- checks that the text does not reveal secrets or private data;
- approves the final version.

## Corrections

If you find an error, select **Report an issue** on that page. Add the expected result and, when safe, the UI element name. The URL, language, and page revision are included automatically.

The team verifies the report against the current product version. A confirmed documentation error is corrected; if product behavior changed, the team also reviews related instructions and role guides.

See also [About this documentation](./about-documentation.md) and [Security and privacy](./security-and-privacy.md).