> 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/archive-management/administer-your-organization.md).

# Administer your organization

Add people, choose their roles and keep track of your organization's projects and data.

This page is for organization admins. It covers how people get into LumiDB, how to manage their roles, and where to see your organization's data. For where the data is stored and how access is controlled, see [Security and hosting](https://docs.lumidb.com/archive-management/security-and-hosting.md).

{% hint style="info" %}
You need the **Admin** role for most of this page. Members can open the **People** page with limited functions. Guests can't open it.
{% endhint %}

### Add people

People join your organization when you invite them to a project. Open the project, click **Share**, enter their email addresses and choose a permission. Inviting someone to a project is the only way to invite them to the organization. See [Sharing projects and inviting collaborators](https://docs.lumidb.com/sharing-and-access/sharing-projects-and-inviting-collaborators.md) for the steps.

New people start as **Guest**. They see only the projects they are invited to and can't create projects. To give someone more, change their role on the **People** page.

If everyone with your company email domain should be able to sign in, write to <help@lumidb.com>. The sign-in methods are described in [Account management](https://docs.lumidb.com/get-started/account-management.md).

### Manage people and roles

Open **People** under **Admin** in the sidebar of the home view. The page lists everyone in your organization, in two groups: **Invited** and **People with access**.

| Column        | What it shows                                                                                                                                          |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Email**     | The person's email address.                                                                                                                            |
| **Role**      | **Admin**, **Member** or **Guest**.                                                                                                                    |
| **Status**    | **Invited**, **Active**, **No recent activity** (not seen for 30 days) or **Invitation expired** (invited more than 30 days ago and not yet accepted). |
| **Last seen** | When the person last used LumiDB.                                                                                                                      |
| **Access**    | The number of projects the person has access to.                                                                                                       |

<figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2Fz3qaFbLGKQG0KL4hXVeL%2F01-people-page.png?alt=media" alt="The People page listing everyone in the organization with their role, status, last seen time and number of projects" width="900"><figcaption><p>The People page. Email addresses are blurred in this screenshot.</p></figcaption></figure>

Use the search box to find a person by email or role.

To change a role, click the role of a person who has joined and choose **Admin**, **Member** or **Guest**.

<div align="left"><figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2FQYpplTTr7rtWNIgE7u14%2F02-role-menu.png?alt=media" alt="The role menu with Admin, Member and Guest and a short description of each" width="640"><figcaption><p>Choose a role from the menu.</p></figcaption></figure></div>

To remove someone from the organization, click the **Options** button on their row and choose **Remove member**.

<div align="left"><figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2FkJCFSFPz5T4xgpsQtgjj%2F03-row-options.png?alt=media" alt="The Options menu of a person with the Remove member command" width="640"><figcaption><p>Remove a person from the organization.</p></figcaption></figure></div>

You can't change your own role or remove yourself.

| Role       | What it is for                                                          |
| ---------- | ----------------------------------------------------------------------- |
| **Admin**  | Manages members and all projects. Has **Full access** to every project. |
| **Member** | Creates projects and works in projects they are invited to.             |
| **Guest**  | Works in projects they are invited to. Can't create projects.           |

Admins always have full access to every project, so keep the number of admins small. The full list of what each role can do is in [Sharing projects and inviting collaborators](https://docs.lumidb.com/sharing-and-access/sharing-projects-and-inviting-collaborators.md).

### See your organization's data

Open **Project data** under **Workspace** in the sidebar. The page lists your organization's datasets grouped by project. Each dataset shows its size and import date, each project shows its total size, and the total for the whole list is next to **Size**. Search by name, and switch between the list and the map with the buttons in the top right.

<figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2Fw9hRsXIA6NxVMUHg04Wa%2F04-project-data.png?alt=media" alt="The Project data page with datasets grouped by project, each with its size and import date" width="900"><figcaption><p>The Project data page. Dataset names are blurred in this screenshot.</p></figcaption></figure>

Click **Options** on a row to open the dataset's project, move the dataset, or delete it.

<div align="left"><figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2FCMM9yTSEL9ZfL9yo6EKo%2F05-dataset-options.png?alt=media" alt="The Options menu of a dataset with Open project, Move and Delete" width="640"><figcaption><p>The Options menu of a dataset.</p></figcaption></figure></div>

### Connect tools and automation

People create API keys for ArcGIS, QGIS and other tools on the **API keys** page under **Admin**. See [API keys](https://docs.lumidb.com/archive-management/api-keys.md).

### Storage and plan

How storage is counted and what to do before a very large import is described in [Limits and storage](https://docs.lumidb.com/archive-management/limits-and-storage.md).

### Questions

Write to <help@lumidb.com>. The whole team reads it.


---

# 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/archive-management/administer-your-organization.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.
