Skip to content

Projects

Overview

The Projects page displays a list of projects within the company and allows you to manage these projects. It is accessed via the product's main menu.

Access to project management

Permissions by role

Operation Viewer Analyst Developer Project manager Administrator Super administrator
View the projects list ✅ ✅ ✅ ✅ ✅ ✅
Open a project and work with its content ✅ ✅ ✅ ✅ ✅ ✅
Create and clone projects ❌ ❌ ❌ ✅ ✅ ✅
Edit a project ❌ ❌ ❌ own projects ✅ ✅
Manage project members and transfer ownership ❌ ❌ ❌ own projects ✅ ✅
Delete a project ❌ ❌ ❌ own projects ✅ ✅

✅ = Allowed | ❌ = Not allowed

General restrictions

  • All actions are available only within your own company; a super administrator works across companies
  • The projects list shows only the projects you have access to. What you may do inside a project is defined by your access level in it (see project members and access)
  • The interface automatically hides actions unavailable to a specific role
  • Prohibited operations are blocked at the system level
  • Creating and cloning projects also requires a valid license and an unused project slot in it

Project display

The following information is displayed for each project:

  • Name (color corresponds to the one selected for the project)
  • Description
  • Owner (the user who owns the project)
  • Creation Date
  • Number of Versions (count of existing project versions)
  • My access level (your own access level in the project)

Features:

  • The currently opened project is highlighted in the list
  • Sorting and search across all columns are supported (similar to other lists: companies, users, etc.)

Creating a project

Required parameters

Parameter Requirements
Name - Unique within the company (can be duplicated across companies)
- Case-sensitive
- Length: 1–128 characters
- Allowed characters: Latin letters, Cyrillic letters, digits, space, ., -, _
- Cannot start with a special character
Color Selected from a palette

After creation:

  • The system automatically opens the new project

Project elements:

  • Project versions
  • RMD within each version
  • Fact tables within each version
  • Data marts within each version
  • Connection settings and details of connected databases within each version
  • Column settings in RMD tables within each version

Important:

  • Project elements are unavailable without creating a project
  • Changes are limited to the scope of the project

Cloning a project

What is copied to the new project:

  • Project versions
  • RMD within each version
  • Fact tables within each version
  • Data marts within each version
  • Connection settings and details of connected databases within each version
  • Column settings in RMD tables within each version

What is NOT copied to the new project:

  • Links to created data mart views in connected databases

Required parameters:

  • Name (rules are the same as when creating an empty project)
  • Color

After cloning:

  • The system automatically opens the new project

Editing a project

Modifiable parameters:

  • Name (checked for correctness)
  • Color

Features:

  • Changes are applied instantly throughout the product
  • Only projects within your company can be edited
  • Changes can be cancelled without saving

Opening a project

Conditions:

  • The project must exist in the company

Result:

  • Access to project elements (RMD, fact tables, etc.)
  • The interface displays the name and current version of the opened project

Features:

  • Only one project can be opened at a time
  • When switching projects, the old one closes, and data is saved for the new one
  • If a project is deleted while you are working, the system moves the user to a "no project" state

"No project" state:

  • The user is notified of the need to open/create a project when attempting to access project elements

Auto-opening:

  • Upon system login, the last used project is opened
  • If no project was opened previously, the user remains in the "no project" state

Deleting a project

Conditions:

  • The project must exist in the company

Process:

  1. The system requests confirmation (data is deleted irrevocably)
  2. All related elements are deleted:
    • Project versions
    • RMD within each version
    • Fact tables within each version
    • Data marts within each version
    • Connection settings and details of connected databases within each version
    • Column settings in RMD tables within each version

What is NOT deleted when a project is deleted:

  • Created data mart views in connected databases

Consequences:

  • A new project with the same name can be created (data from the old one is not restored)
  • If the deleted project was open, the system moves the user to the "no project" state