How can I collaborate with other users for my account and environment?

Account Collaboration:

Developing and releasing superior products in large companies always depends on efficient collaboration, i.e. properly organized interaction between all members of the team. In order to greatly facilitate the process of joint development, Gigality provides an account sharing feature.

The main idea is to let organizations create one primary account, where all necessary environments are running, and to share certain or all activities with other accounts (e.g. members of the development team).

All accounts of an organization are interconnected in such a way, to enable collaboration. Any user (regardless if they are registered at Gigality), can join (i.e. should be invited by a primary user) or leave an organization’s collaboration.

Within this concept, we define two types of accounts:

1. Primary
   
2. User 
   

The primary one is the main billing organization’s account. The primary account owner can manage the list of all other collaboration users, specify their rights for performing certain activities, decide on the access to the shared within collaboration environments, etc. All of the charges for using shared environments are applied to this account.

A collaboration user can work with shared environments of the primary billing account, being able to deploy applications, change configurations, read log files, view statistics and so on. The only exception is that this user cannot clone environments. A user’s ability to change an environment’s topology, access this environment via SSH and delete it, is regulated by the primary account owner, when the particular environment is shared.

A user can also be allowed to create new environments on the primary collaboration account. In this case, there will not be any restrictions for a trial user while setting up the environment (e.g., number of cloudlets available). All of the charges for such environment usage will be applied to the primary account.
Note: After leaving the collaboration, the user will no longer have access to this environment.

• Related Articles

• How to access using SSH?

  Let’s see how you can access your Gigality account with all of its environments and containers or just a separate container via SSH. SSH Access to a Gigality Account Direct Access to the Container Note: SSH access is provided to the whole account but ...

• What type of load balancing options are available with Gigality PaaS?

  Load balancing is a process of traffic navigation and workload distribution across multiple components, which is performed by the dedicated type of nodes called load balancers. In Gigality PaaS such instance(s) can be manually added into the ...

• How to install a traffic distributor on a Gigality environment?

  The process of Traffic Distributor installation is fairly simple with Gigality - being specially packed for the Marketplace, it can be created in a few clicks and start working in just a matter of minutes. Herewith, the configuration of the solution ...

• How do I Create Groups under my environment?

  Setting new environment groups involves creation of a special tag, that subsequently can be attached to the required environment to logically mark it within the dashboard. You can use any naming paradigm that would be convenient for me - for example, ...

• How to assign, edit & remove environment groups?

  How do I assign, edit & remove groups from my environment This information consists of the basic management options that Gigality Platform provides for operating with environment groups. The following classification gives you proper understanding of ...