PIX4Dcloud Data Sharing and Project Access: A Practical Control Model

A shared PIX4Dcloud project should have a named owner, an approved audience, a defined review purpose and a retention/export rule. Access to a spatial model is not the same as permission to redistribute the underlying site information, and annotations should not silently become authoritative asset data.

Technical content reviewed against official sources · 16 November 2026
01

Assign responsibilities before sending a link

Identify the dataset owner, processing operator, technical reviewer and person authorised to issue information externally. Separate routine project reviewers from administrators. Enterprise access, SSO, API or custom integration requirements should be scoped separately from the core Starter and Pro plans.

02

Classify the information in the project

Review imagery, coordinates, utility details, building interiors and design overlays for contractual or security sensitivity. Choose who may view, annotate, download or reshare according to the owner’s policy. Where the approved route is unclear, pause external sharing and use the controlled project process.

  • Authorised audience and organisation
  • Permitted actions: view, measure, annotate, download or administer
  • External share-link approval and expiry practice
  • Retention period and archival export responsibility
  • Removal of access when a person leaves the project
03

Keep collaboration separate from authoritative records

Annotations are useful for questions, observations and assigned actions. They should include an author, date and context. Before an annotation becomes a design change, GIS update or acceptance record, it must pass the relevant project verification and approval route.

04

Plan the export and retention route

Decide which files constitute the issued record: source imagery, point cloud, mesh, orthomosaic, annotations, reports or a defined subset. Test the export in the recipient system and retain coordinate, design-revision and QA metadata. Do not rely on indefinite browser access as the only archive.

05

A simple review-state convention

Use explicit states such as Processing, Internal QA, Review, Issued and Superseded. Only the appropriate state should be visible to each audience. When a new capture or corrected model replaces an earlier one, preserve the relationship rather than silently deleting the project’s review history.

What to carry into the project.

Name an owner and approved audience.

Control sensitive infrastructure sharing.

Annotations require verification before authoritative use.

Export and retain the issued record independently of browser access.

Continue the technical review.

Managing GPC in cloudPIX4Dcloud product page
PIX4D · Current cloud plan comparisonPIX4D · Cloud support hub

Features and availability can change. Confirm the exact version, plan, sensor and commercial scope before procurement or project issue.

Specify the working system, not only the licence.

Share your source data, required outputs, users and constraints. Easepect can scope product supply, a technical demonstration, implementation and training.