For those getting started with Catenda on active construction projects a new organization may be manually created by the contact person at Catenda.
Those with access to creating projects can create their own project in this platform organization while projects may be created by the Catenda contact person in the platform organization for those who do not.
From a structural perspective, projects may be grouped in various ways within the platform to suit different operational needs.
For example, a company might utilize a single platform organization as a container for all its projects, or it might choose to distribute projects across several distinct platform organizations.
This article contains information about the following topics:
The configurations described in this article are provided for illustrative purposes and are subject to the specific technical setup and terms of the account.
The availability and functional limits of these organizational structures are governed by the specific terms of the service agreement.
Individual project allocation
Project allocation
Those who do not have access to creating projects have to ask their Catenda contact person to create the project for them.
To test a new feature or that is not available to everyone a limited time project can often be created so organization owners can evaluate if they want to enable to feature for their project or not.
Project access
When a project agreement is cancelled an expiration date is configured for the project according to the cancellation notice period.
Following the conclusion of the active period of a project or upon the expiration of a project, Catenda does not undertake an obligation to maintain or store project information.
To optimize an organization's configuration for active work, projects that are no longer active may be removed by the owner. Users are encouraged to ensure any vital data is secured in their own storage solutions before a project is deleted.
Following the conclusion of the active period project of a project, there is no obligation to maintain or store information on Catenda servers.
It is the responsibility of the organization or project owner to manage any data exports or backups they deem necessary prior to expiration.
Once a project has reached its expiration date or is deleted, project information is no longer guaranteed to remain on the servers.
Click here to read more about exporting all project information.
Data management
For configurations utilizing individual project allocation, requests to maintain projects that are no longer active on the platform are evaluated on a case-by-case basis.
A Catenda representative may be contacted to review the status of projects that have ended or are on halt but are intended to be retained for reference.
Volume based project allocation
Project allocation
For companies engaging in active collaboration, a platform organization serves as the central container for managing projects.
The primary use of these containers is to facilitate active production and construction workflows.
Depending on the specific configuration of the platform organization, project creation may be managed in two ways:
Self-Service Creation
Users with the appropriate permissions may have the ability to create projects directly within their platform organization to facilitate active workflows.
Assisted Creation
In instances where the platform organization is configured without direct user-creation access, Catenda personnel may assist in establishing projects on behalf of the company.
This ensures that active construction work can proceed even when self-service options are not enabled for that specific container.
Secondary configurations
Additionally, certain configurations may be established for secondary purposes, such as testing new features or internal training.
These spaces are generally distinct from primary construction activities and are subject to the functional boundaries of that specific account setup.
Project access
Depending on the organization's configuration, owners may have the ability to manage project accessibility and transitions between different organization types.
To optimize the active workspace within an organization's configuration, projects that have concluded their primary workflow may be removed.
After a project is deleted we can no longer guarantee that the project information remains on our servers.
Before deleting the project, the data can be backed up to the storage solution of the customer.
Click here to read more about exporting all project information.
Data management
Within authorized volume-based setups, projects may be transitioned to an organization configuration intended for reduced activity levels.
This allows for continued data reference and occasional maintenance tasks, such as specific data retrieval or minor updates, while keeping the primary organization optimized for high-intensity collaboration.
The availability and functional limits of these transitions remain subject to the specific terms of the account setup.