> For the complete documentation index, see [llms.txt](https://docs.lumidb.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumidb.com/sharing-and-access/sharing-projects-and-inviting-collaborators.md).

# Share point clouds with clients and collaborators

Send a client a link to view or download a point cloud in the browser, invite colleagues, and control who can view, download or manage a project.

Share a project to give a client or colleague access to your point clouds and other survey data. They open it in a web browser through a link, with nothing to install, and you choose whether they can only view or also download.

<div data-with-frame="true"><figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2FbZER7BSmjIK9UYD7SXFn%2Fimage.png?alt=media&#x26;token=1084920d-137f-4895-a14a-2d58cbbfc429" alt=""><figcaption></figcaption></figure></div>

### Share a project with a client in a minute

1. Open your project and click **Share** in the top right corner.
2. Choose how your client gets in:
   * **By email:** enter their email address, choose **Can view** or **Can download**, and click **Invite**.
   * **By link:** turn on **Public** and click **Copy project link**. Anyone with the link can view the project without an account.
3. Send the link or let the invitation email do it. Your client opens the project in the browser. There is nothing to install.

You can also forward the [guide for your clients](https://docs.lumidb.com/sharing-and-access/viewing-a-project-shared-with-you.md) with your link. It explains how to move around the project.

{% hint style="info" %}
You need **Full access** to the project to share it. A client with **Can view** or **Can download** can't invite other people.
{% endhint %}

Permissions and access in LumiDB are managed on a two-level structure:

1. [**Organisation roles:**](#organisation-roles) These manage what a user can do in the organisation, outside projects, such as viewing and managing projects and people in the organisation.
2. [**Project permissions:**](#project-permissions) These determine what a user can do in a given project.

### Organisation roles

**Admin:** Full control over the organisation. Can manage all projects, members, and organisation settings.

**Member:** Can view the organisation’s “[People](#managing-organisation-roles-people-page)” page, create new projects. They only see the projects they are explicitly invited to.

**Guest:** The default role for new accounts. Cannot create projects or view the “[People](#managing-organisation-roles-people-page)” page. They only see the projects they are explicitly invited to.

{% hint style="info" %}
New accounts are invited as “Guest” by default. Admins can upgrade users to Member or Admin from the People page.
{% endhint %}

Here is a more detailed look at these different roles:

| **Capability**                                         | **Admin** | **Member**                      | **Guest**                       |
| ------------------------------------------------------ | --------- | ------------------------------- | ------------------------------- |
| View projects explicitly shared with them              | **✓**     | **✓**                           | **✓**                           |
| Create projects                                        | **✓**     | **✓**                           | **–**                           |
| View all organisation projects                         | **✓**     | **–**                           | **–**                           |
| Change organisation settings                           | **✓**     | **–**                           | **–**                           |
| Delete organisation                                    | **✓**     | **–**                           | **–**                           |
| Remove an organisation member                          | **✓**     | **–**                           | **–**                           |
| Change users’ organisation roles                       | **✓**     | **–**                           | **–**                           |
| View People page                                       | **✓**     | Yes, with limited functionality | **–**                           |
| View Settings page                                     | **✓**     | Yes, with limited functionality | Yes, with limited functionality |
| Invite someone to a project (also to the organisation) | **✓**     | Based on project permission     | Based on project permission     |
| Add or import data into project                        | **✓**     | Based on project permission     | Based on project permission     |
| Export project data                                    | **✓**     | Based on project permission     | Based on project permission     |
| Delete project data                                    | **✓**     | Based on project permission     | Based on project permission     |
| Delete projects                                        | **✓**     | Based on project permission     | Based on project permission     |
| Manage project access                                  | **✓**     | Based on project permission     | Based on project permission     |

### Project permissions

**Can view:** View data, stream to QGIS/ArcGIS, use the toolbar (compare, cross-section, measurements). Note: Changes they make do not persist.

**Can download:** Everything in "Can view", plus the ability to export/download data.

**Full access:** They can do everything. Inviting users, removing users, adding/deleting data, and deleting the project. (Note: Organisation admins always have “Full access” to every project).

{% hint style="info" %}
Project permission limitations do not apply to admins. Regardless of permissions given to them, they always have full access to every project in the organisation.
{% endhint %}

{% hint style="info" %}
The Share Panel is only visible/active to users with “Full access”.
{% endhint %}

Here is a more detailed look at the three different project permission categories:

| **Capability**                          | **Can view** | **Can download** | **Full access** |
| --------------------------------------- | ------------ | ---------------- | --------------- |
| Open and navigate project               | **✓**        | **✓**            | **✓**           |
| View project data                       | **✓**        | **✓**            | **✓**           |
| Create measurements                     | **✓**        | **✓**            | **✓**           |
| Can hide layers                         | **✓**        | **✓**            | **✓**           |
| Stream data to ArcGIS, QGIS, etc.       | **✓**        | **✓**            | **✓**           |
| Export or download data                 | **–**        | **✓**            | **✓**           |
| Persisting measurements                 | **–**        | **–**            | **✓**           |
| View who else has access to the project | **–**        | **–**            | **✓**           |
| Invite people to project                | **–**        | **–**            | **✓**           |
| Change other users’ project permissions | **–**        | **–**            | **✓**           |
| Remove people from project              | **–**        | **–**            | **✓**           |
| Can lock or unlock layers               | **–**        | **–**            | **✓**           |
| Add or import data                      | **–**        | **–**            | **✓**           |
| Delete project data                     | **–**        | **–**            | **✓**           |
| Delete project                          | **–**        | **–**            | **✓**           |

### Step by step: How to invite a collaborator

{% hint style="info" %}
People you invite to a project join your organisation as **Guest**. A Guest only has access to the projects they are invited to. To let them create projects and see the [People](#managing-organisation-roles-people-page) page, an organisation admin changes their role to **Member** (or **Admin**) on the People page. Inviting someone to a project is the only way to invite them to your organisation.
{% endhint %}

1. Open your project and click the “Share” button in the top right corner. If this button is disabled, you do not have “Full access” to this project.
2. In the share panel, enter the user's email address in the text box. You can add multiple email addresses by separating them with a comma.
3. Use the dropdown menu next to the email field to select their project permission (Can view, Can download, or Full access).
4. Click Invite.
5. Invited users will receive an email with a link that takes them directly to the project. This link will automatically create their organisation account if they don't already have one. They do not need to set a password. Instead, they can log in at any time using their email address and a secure login link sent to their inbox.
6. When a user is invited, their email addresses will appear under “Invitations”. When they accept the invitation and join you will see them under “Who has access”.

{% hint style="info" %}
You can revoke an unaccepted invitation, resend an invitation and remove users from your project via the permission dropdown next to each email.
{% endhint %}

<div align="left" data-with-frame="true"><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2FjwlA06DyJHkhXcYU00K1%2Funknown.png?alt=media&#x26;token=ae5a1c95-46cc-447a-a5a2-6427ee3eb384" alt="" height="468" width="624"></div>

### Link sharing

The “Copy link” button will copy the project link to your clipboard. When the Public toggle is off, only people who are already invited to this project, and organisation admins can use this link to access the project.\
\
If you turn the “Public” toggle on, anyone with the link can view the project, even without a LumiDB account.

<div align="left" data-with-frame="true"><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2Fhz8TOyllzC67fX1UiQYr%2Funknown.png?alt=media&#x26;token=973ab380-3349-4f95-85aa-91b7084054c9" alt="" width="563"></div>

### What your client sees

* **With a public link:** your client sees the project as **Can view**. They can look around, hide layers and measure. They can't import data, export data or change who has access.
* **With an invitation:** your client sees the project with the permission you chose. **Can download** also lets them export and download data.
* No password is needed. The invitation email contains a link that signs them in.
* Changes your client makes, such as measurements, are not saved to your project.

{% hint style="info" %}
Streaming links for ArcGIS and QGIS need an [API key](https://docs.lumidb.com/archive-management/api-keys.md), and a key is personal. Your client has to sign in to LumiDB to create one. A public link is not enough.
{% endhint %}

### Stop sharing

* **Public link:** turn **Public** off. The link stops working immediately. If you turn it on again, LumiDB creates a new link, and the old one stays dead.
* **A person:** open the dropdown next to their name in the **Share** panel and choose **Remove from project**. A pending invitation can be revoked in the same way.

Removing someone from a project doesn't remove them from your organisation.

### Managing existing users

#### Managing project permissions (Share panel)

1. Changing permissions: In the "Who has access" list, click the dropdown menu next to a user's name. You can upgrade or downgrade their access between Full access, Can download, and Can view.
2. Removing from a project: In that same dropdown menu, select “Remove from project” at the bottom.

{% hint style="info" %}
Removing a user from a project only removes their access to that specific project. It does not remove them from your organisation. Additionally, organisation admins always retain full access to all projects, even if you remove them from this list.
{% endhint %}

<div align="left" data-with-frame="true"><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2FdhfoSDRiZIZDaniA3uvW%2Funknown.png?alt=media&#x26;token=8187b4db-544b-4893-9009-35ee9ce26637" alt="" width="563"></div>

#### Managing organisation roles (People page)

To manage users at the organisation level, navigate to the people page in the left-hand sidebar in your home view.

Only organisation admins can change roles or delete users. Members can view the people page and see who has access, but they cannot make changes.

To change a user’s role, find the user in the "People with access" list. Click the current role to see the dropdown, then select the new role. You can delete a user from your organisation by clicking the ellipsis (…) button on the right end of the user’s row.

<div align="left" data-with-frame="true"><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2FH6ItnHA2ali4sS1xBvB9%2Funknown.png?alt=media&#x26;token=3cd735ac-6631-4e49-a991-7278b349b8a4" alt=""></div>

<br>

### Frequently Asked Questions (FAQs)<br>

1. **How do I send a very large point cloud, such as 100 GB or more, to a client?**

Upload it to a LumiDB project and share the project instead of the file. Your client never downloads the whole dataset: LumiDB streams the part they are looking at, so even a 500 GB point cloud opens in a browser. If they need files, invite them with **Can download**.

2. **Can my client measure the point cloud without point cloud software?**

Yes. Everyone you share with can use **Measure** (distances, paths, areas and points) and **Cross section** in the browser. Their measurements aren't saved to your project.

3. **Do I still need Dropbox, WeTransfer or a hard drive to deliver data?**

Not for viewing. A shared project replaces sending the files. Give **Can download** to clients who also need copies of the data.

4. **Can I invite someone to my organisation without adding them to a project?**

No, currently invitations are initiated from within a project. When you invite someone to a project, they automatically join your organisation as a Guest. You can upgrade the organisation role to Member or Admin in [People](#managing-organisation-roles-people-page) page, once they accepted the invitation and joined your organisation.

5. **What happens if I invite an existing organisation member to a new project?**

They will simply be added to the new project with the permission tier you select during the invite process. They will retain their existing organisation role.

6. **Can a guest have "Full access" to a project?**

Yes. A guest can have “Full access” to a specific project, allowing them to manage that project, even though they have limited permissions at the organisation level (e.g., they cannot see the people page).

7. **What happens to a user's projects if I delete them from the organisation?**

They will be removed from the organisation immediately. Any projects they created remain in the organisation, anyone else who has access to the projects will continue to have access to them.

8. **Do my clients need a LumiDB account?**

No. With the **Public** switch on, anyone with the link can view the project without an account. If you invite someone by email instead, they get a link that signs them in without a password.

9. **Can my client download the data?**

Only if you invite them with **Can download** or **Full access**. A public link gives **Can view**, which doesn't allow exporting or downloading.

10. **How long does a public link work?**

Until you turn **Public** off. The link has no expiry date. When you turn **Public** off and on again, LumiDB creates a new link.

11. **Can I share only part of my data?**

Sharing works for a whole project. To share only some of your data, put it in its own project and share that project.

12. **Can people I share with share the project further?**

No. Only people with **Full access** can see the **Share** panel.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lumidb.com/sharing-and-access/sharing-projects-and-inviting-collaborators.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
