Projects and users
CleverMaps is a multitenant cloud application, which means that a single instance of the application serves multiple users at the same time. Registered users have access to various projects. There can be more than one user in a project, and one user can have access to one or more projects. In the scope of a project, users can also have different user roles. So, each project consists of data, metadata, and users.
Project page of a Retail Solution Demo project
Project life cycle
In the life cycle of a project, data comes first. When building a project from scratch, the data has to be transformed in a way that allows you to apply various location intelligence concepts. Some of the data must contain a geospatial information, so it can be visualised on a map. Then, datasets corresponding with the data are created. As a next step, metrics are created. Metrics define the actual computations that will be performed on the project's data. Metrics are used in indicators, which represent a phenomena that can be visualised on a map. Indicators can be drilled down on for more detailed analysis, as defined in indicator drills. Indicators and indicator drills are then paired in a dashboard, and displayed as an initial state of the infopanel. A project is usually divided in a set of views. Dashboard is the main content of a view. View essentially is a group of indicators that represent a common business goal (market potential, catchment area analysis, customer intelligence...). There are also physical points, related to the data and which may represent the actual locations related to the business (e.g. stores, warehouses, ATMs...). They are defined in marker objects, and grouped in marker selectors.
There are 6 user roles in CleverMaps - Viewer, View Creator, Metadata Editor, Data Editor, Load Data and Admin and 19 permissions assigned to them:
access a project
get project detail
delete a project
update a project
add project membership
list project membership
update project membership
delete project membership
invite to project
list project invitations
update project invitation
load project data
dump project data
validate project data
delete own view
delete own dashboard
create marker selector
delete own marker selector
create indicator drill
delete own indicator drill
create all metadata (except for data permissions)
update all metadata (except for data permissions)
delete all metadata (except for data permissions)
update data permissions
get audit log
Viewer is the lowest user role available. After accepting an invitation to a project, you become a Viewer. A Viewer can open map views in a project, filter data and create a personal bookmarks.
View Creator role has all the permissions of Viewer role and, in addition, it is able to create/delete own project metadata of following types:
NOTE: After creating
views by View Creator role, these (personal saved views) are visible only to creator and are displayed in alphabetical order at the end of view list in project page in UI. In order for personal saved views to be visible for all users these views must be included in
defaultViews list of
ProjectSettings metadata object. Managing of
ProjectSettings metadata object can be done only by user with Metadata Editor or Admin role. See Project settings for more details on
Metadata Editor has all the permissions of Viewer role and, in addition, it is able to create/update/delete all project metadata (except for
DataPermissions metadata type), and validate the data.
Data Editor has all the permissions of View Creator and Load Data role.
As an Admin, you have all the permissions of the lower user roles, plus you are able to load/dump project data, invite other users into the project, and manage existing memberships. User management interface is available in the application by hovering the Account icon on the bottom left of the Project page, and selecting User management.
Load Data user role is able to load and validate the project data only. Users with this role may be used for automated data upload, as an account used in a Shell script. This role is not part of the role hierarchy described above.