Organization identities and customer imports

Prerequisites and authority

Use an individual staff account with the action permission and required organization module/license. Viewing a menu does not establish permission to mutate records.

Manage identities and CSV imports

Organization Identities and CSV Imports appear only where their modules and permissions allow them. An institutional identity links a person to organizational records; it should not create a second customer merely because the same person also uses Telegram or the website.

Use the exact template supplied by the current import page. Preserve required headers, formats and identifiers. Prepare a small sample before a full import.

1. Define whether the import creates identities, customers or access grants.
2. Check duplicate rules and plan eligibility.
3. Validate the file using the supported preview/validation action, if present.
4. Submit the batch once and retain its identifier.
5. Review accepted, rejected and failed rows individually.
6. Correct failed rows and use the supported retry/re-import rule.
7. Verify representative customer and subscription outcomes.

Do not assume preview, automatic rollback or all-or-nothing import semantics exist. A partially successful batch may have created valid records that must not be duplicated on retry.

Explicit grant dates can differ from ordinary duration-based queued purchases. Check the displayed validity and provisioning outcome. Keep the original source reference and grant reason available for audit.

CSV files can contain personal information. Store and exchange them through authorized channels. Do not publish screenshots containing actual imported identities.

Related guides

Related guides: Staff accounts, roles and permissions, Administrative session and audit investigation, System operations and task controls, Roles and permission matrix.