Security > Managing Permissions

Managing Permissions

Permissions in JMap are divided into 2 families: permissions for the users of applications (Pro, Web and Mobile) and permissions for the administrators (JMap Admin).

User permissions

User permissions determine what the users can do inside JMap Pro, JMap Web and JMap Mobile applications.

The following table presents the different groups of permissions available for the users.

User permissions
Permissions on projects	See section Project Permissions for more information.
Permissions on layers	See section Layer Permissions for more information.
Permissions on personal layers	Create personal layers This permission gives a user the right to create personal layers in JMap Pro applications. By default, JMap users are not allowed to create personal layers. You can configure this permission in sub section Permissions of section JMap Server.
Permissions on forms	See section Database Forms for more information..

Administrator permissions

Administrator permissions determine what administrators are authorized to do in JMap Admin. Some permissions are global (permissions to do some tasks) while other permissions apply to specific resources.

Most of the global permissions are configured in sub section Permissions of section JMap Server.

The following table describes the global administration permissions.

Global administration permissions
Access JMap Admin	This permission is required for an administrator to access JMap Admin. After the installation of JMap, only the user administrator has this permission. Note that the password is initially left empty for this user. It is strongly recommended to enter a password for user administrator. See section Managing Users for more information on modifying passwords. Also make sure to leave at least one user with this permission and with a known password. Otherwise, it will be impossible to access JMap Admin.
Create databases	This permission is required for an administrator to create new databases in JMap Admin.
Create remote connections	This permission is required for an administrator to create new connections to remote JMap Server instances in JMap Admin.
Create deployments	This permission is required for an administrator to create new application deployments in JMap Admin.
Create metadata templates	This permission is required for an administrator to create new metadata templates in JMap Admin.
Create style templates	This permission is required for an administrator to create new style templates in JMap Admin.
Create projects	This permission is required for an administrator to create new projects in JMap Admin.
Create data sources	This permission is required for an administrator to create new spatial data sources in JMap Admin.

Administration permissions that are specific to resources determine what an administrator can do with each resource. The following table describes those permissions.

Resource specific administration permissions
Access ...	Allows for viewing the detailed information of a resource and for using the resource, but not modifying it. Example: For using a spatial data source to create a layer, the administrator must minimally have the permission Access on the data source.
Administrate ...	Allows for modifying the resource and for managing the user permissions for the resource. Does not allow for deleting the resource, nor for managing its administration permissions. Example: To add a layer in a project, the administrator must have the Administrate permission for the project.
Use SQL console	Applies only to databases. Allows for using the SQL console on the database. The SQL console is used to show the database structure and to execute SQL queries on the database.
Remote access	Allows for accessing the resource from another instance of JMap Server. This permission is generally granted to a generic account used to open communication sessions between different instances of JMap Server. For more information, see sections Sharing Layers and Sharing Spatial Data Sources.

Owners of a resource

Most resources managed in JMap Admin have one or more owners. Owners of a resource are the only ones that are allowed to:

•manage administration permissions for the resource;

•manage the list of owners for the resource;

•delete the resource.

Super administrators

Super administrators are special accounts that can do everything in JMap Admin. They are the only ones who are allowed to:

•manage the list of super administrators;

•manage global administration permissions;

•manage users and groups;

•modify the working parameters of JMap Server;

•display the log files;

•import and export configurations.

You can manage the list of super administrators from sub section Permissions in section JMap Server. Select the Super administrators tab.

The following table presents administration tasks with examples, and indicates which profile or permission is required for each case.

Tasks	Super Administrator	Administrator
Access JMap Admin	YES	If permission Access JMap Admin
Manage the list of Super administrators	YES	NO
Manage global administration permissions •Give an administrator the permission to create projects •Remove an administrator the permission to create spatial data sources •Give an administrator the permission to create metadata templates for data sources	YES	NO
Perform management tasks for JMap Server •Modify JMap Server working parameters (ports, memory, etc.) •Manage users and groups •Import and export JMap Server configurations •View and manage log files	YES	NO
Create a resource •Create a project •Create a database •Create an application deployment	YES	If permission Create ...
Use a resource •Use a database to create a spatial data source •Use a spatial data source to create a layer •Use a connection to JMap Server to create a layer by reference	YES	If permission Access ...
View detailed information about a resource •Click on a database and view all its parameters •Click on a project to view all its parameters	YES	If permission Access ...
Modify a resource •Change the name of a project •Add a layer in a project •Modify the connection parameters for a database •Modify the projection of a spatial data source	YES	If permission Administrate ...
Delete a resource •Delete a project •Delete an application deployment •Delete a style template	YES	If owner of the resource
Manage user permissions of a resource •Give a user the permission to open a project •Give a user the permission to edit the elements of a layer of a project •Remove a user the permission to copy the data of a layer	YES	If permission Administrate ...
Manage the administrator permissions of a resource •Give an administrator the permission to use a spatial data source •Give an administrator the permission to modify a project •Remove an administrator the permission to modify a database	YES	If owner of the resource
Manage the list of owners of a resource	YES	If owner of the resource