# Introduction

This guide describes the main steps involved in publishing data through a JMap Cloud mapping application, whether public or restricted.

Within an organization, each user is assigned one of three roles in JMap Cloud: **Administrator**, **Editor**, or **Viewer**. The [Roles](https://docs.jmapcloud.io/en/jmap-cloud-portal/user-guide-for-jmap-cloud-portal/introduction/roles) section describes the responsibilities associated with each role.

Only **Administrators** and **Editors** can access **JMap Cloud Portal**, the platform’s data management interface. Some management operations, however, are restricted to administrators.

**Viewers**, on the other hand, access only the mapping applications that publish the data, such as **JMap NG Cloud**.

The diagram below illustrates the general workflow and highlights the roles involved at each step.

![](https://3291879974-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9n1KCuTyIKwSpZcPcC6l%2Fuploads%2FTVITVZnsvOgn2o21GCG8%2FFlux%20de%20travail%20JMapCloud-EN.png?alt=media\&token=bd9740bc-30d5-40b4-98d9-c1c794104fd6)

## Integrating Data

In this first step, the **Editor** integrates data into JMap Cloud by creating **data sources**. These sources may originate from GIS files, spatial data servers, satellite imagery, or non-spatial tabular files.

Data can be:

* **Uploaded** and copied into the internal JMap Cloud databases
* **Dynamically connected** through external web services
* **Accessed through data sharing** with other organizations

These sources then become available for project configuration.

For more information, see the [Integrating Data: Data Sources](#connecting-data) section.

## Organizing Data into Projects

Data integrated into JMap Cloud is organized into **projects**. A project includes:

* The definition of map layers
* Security settings (access permissions)
* Measurement units
* Other display settings

When creating a project, the editor defines the map’s appearance, the data it contains, and which users can access it.

For more details, see the [Organizing Data into Projects](https://docs.jmapcloud.io/en/jmap-cloud-portal/user-guide-for-jmap-cloud-portal/organizing-data-into-projects) section.

## Configuring Project Data

The editor then creates **map layers** by selecting data sources.

For each layer, the editor can define:

* Feature display styles
* Labels
* Tooltips
* Visible zoom levels
* And other configuration options

It is also possible to add **non-spatial tabular data** to a project.

For more information, see the [Configuring Project Data](https://docs.jmapcloud.io/en/jmap-cloud-portal/user-guide-for-jmap-cloud-portal/configuring-project-data) section.

## Publishing Data

Once the project is finalized, it can be published to end users through **JMap NG mapping applications**.

Depending on the security settings defined by the editor:

* The application can be **public**
* The application can be **restricted to authenticated users** with the Viewer role

For more information about these applications, see the [JMap NG User Guide](https://docs.jmapcloud.io/en/jmap-ng/jmap-ng-user-guide).

Extensions developed by various software vendors can also be added to projects to provide additional functionality for the applications that publish the data.

The [Extensions](https://docs.jmapcloud.io/en/jmap-cloud-portal/user-guide-for-jmap-cloud-portal/managing-the-organization/extensions) section lists the extensions available for projects.