How to share a point cloud with clients

Share your survey in three actions

1. Upload your E57 to an ATIS.cloud project and let it finish processing.
2. Share a secure link: enable the useful tools and the protection options available with your subscription.
3. Your client opens the survey in their browser, without installing processing software.

Open ATIS.cloud and upload my survey

The rest of this guide adapts delivery to the task: review, collaboration or source-file handover. The ATIS.cloud sharing feature explains the available settings.

Match the handover to the client's next task

The client only needs to inspect the survey

A browser link suits a project review or a discussion about the site. The client navigates the scene and uses the tools you enable. ATIS.cloud public access keeps source files in the project and does not save the visitor's session actions.

The client will work with the team

Use identified members for ongoing teamwork. ATIS.cloud permissions let you assign annotation management, exports and source-file downloads according to each person's responsibilities.

The client needs files for their own software

Agree the format with the person who will use the data. Identify the target application, its version and the files required by the contract. Prepare a package for that workflow alongside browser review access.

• Ask who will use the survey, not just who receives the email.
• Write down the expected task: inspect, comment, measure or model.
• Confirm whether source files are part of the agreed delivery.

Prepare a reference the client can recognise

Include a short handover note with the survey. The recipient should be able to identify what they are viewing and find the information needed for their work.

• Site, surveyed areas and capture date, with any excluded zones.
• Reference version and the person responsible for confirming it.
• Units and coordinate information required by the recipient's workflow.
• Known gaps, obstructions and limits relevant to the intended use.
• File list, naming rules and any accompanying images or reports.

Distinguish the source point cloud, review access and CAD/BIM deliverables. If plans or a model are required, identify who prepares and checks them. Our point cloud file format guide helps you agree the files with the recipient.

Configure access for the agreed task

In the sharing settings, select the password protection and expiry options available with your subscription. Use identified project members when access must be assigned to named people: a public link and its password can be forwarded to someone else.

1. Confirm the shared project and the scene the recipient will see.
2. Choose the available tools and access protection appropriate to the content.
3. For named collaboration, add the intended members in the project's Access section.
4. Review their roles separately, including download or annotation permissions if required.

For sensitive data, agree the access method with your team and restrict permissions to the people involved.

Test the handover as the recipient

Open the public link in a private browser window to see the project as your client will. For member access, ask an authorised participant to test their role. Check both the actions needed for the job and the intended restrictions.

• Does the link open without relying on your signed-in session?
• Is the right survey version visible, with the expected coverage?
• Are the promised tools available, and are unnecessary rights absent?
• Can the client use the delivery on their intended device and connection?
• For files, has the recipient checked that the package opens and is correctly positioned?

If something fails, identify the issue: link, permissions, data preparation or the recipient's environment. Correct it and repeat the relevant test before confirming delivery.

Send context, then close the delivery properly

Adapt this message template to your project. Complete the relevant fields and send sensitive credentials through your organisation's approved channel.

• Project and reference: [site / survey date / version].
• Access: [link or file location] for [inspection / collaboration / file delivery].
• Scope and limitations: [included areas / known gaps / intended use].
• Expected response: [check to perform / person responsible / agreed date].
• Availability and contact: [access period to confirm / support contact].

Agree the access period and source-data retention with your client. Flag any change to the reference version and retain a record of the package delivered and its receipt.

Product documentation behind this guide

Access checked on 9 September 2026: project members, permissions, sharing protection and public review.

Prepare my handover in ATIS.cloud