Collaborating with other users

How to Share your Jelastic environments with other developers

Sometimes you need to provide a third party with access to your environment – that might be a consultant, a freelance developer, or just another member of your development team. Jelastic now gives you an easy and secure way to handle this requirement – avoiding the risks caused by sharing a single user account between multiple people, and providing a better separation of responsibilities and permissions.


All aspects of account collaboration are managed via the Account settings > Collaboration option. Look for settings at the top-right of the dashboard, to open the Account settings tab as shown below:

User Management allows you to define which users you want to grant access to your account; you can invite users to work with you, edit how they’re displayed in your user list, giving each user a nickname or alias so that you can identify them more easily, and unlink to completely remove them from your account.

You can then select each user to configure which environments from your account are shared with them, and which permissions they’re granted. This enables you to share different environments with different users, and give each a different level of access according to your needs.

Inviting users to collaborate

Simply click invite and enter the user’s email address. It doesn’t matter whether the user has an existing account on Jelastic or not; either way they can still collaborate with you, and any other environments they wish to create on their own account will remain completely separate.

Collaborator accounts have a special status and unlike trial accounts, they do not expire.
However, if you share your environment(s) with a trial user, this collaborator will lose access to the environment(s) once the trial period is over. To continue using the platform, they will need to upgrade to a paid account or contact our billing team to manually convert their user to a collaborator account.

You can optionally allow collaborative users to create new environments on your account. These environments will be owned by you, and therefore the corresponding usage charges will be debited from your account instead of the user who created them.

Jelastic sends an email notification to the person you invite, with a link they must click to accept the invitation and begin collaborating with you.

Specifying shared environments

You will be notified when a user accepts your invitation, at which point they will be added to the user list in your dashboard. No environments are shared by default, and you must configure them (per user) after the invitation is accepted.

Shared Environments

Select a user from your list, and use the Add button to define which environment(s) to share. You can either select an individual environment, or use the ‘all environments’ option to share all existing environments in your account with this user.

Sharing can only be configured for existing environments. To share new environments in future you need to return to this screen at a later time.

The optional ‘change topology / SSH access’ permission available for each environment specifies whether this user is allowed to edit the environment topology (add/remove servers, adjust cloudlet limits), and access the servers via SSH.

If this permission is granted, the environment will be listed in their own SSH gateway (i.e. using their own user) together with any of their other environments, and they can add/remove their own SSH keys for that access – so you should only grant this to a highly trusted person since they will have the ability to impact your usage charges and security.

User permissions

We’ve tried to avoid unnecessary complexity by only offering a small number of permissions options. This should make it easier to decide the most suitable combination for your needs, and in doing so hopefully provides a close match to your workflows. However, we are always eager to receive your feedback so please get in touch with our support team if you need something that’s not currently provided.

Here’s a summary of the permissions permutations, and what actions are available for each user.

Account-level sharing permissions

Action Account holder Collaborating user permission
Default Create new environments
Create environment
(shared account)
Yes No Yes
Create environment
(own account)
Yes Requires own paid account Requires own paid account
Transfer environment
(change env. owner)
Yes No No
Cancel pending environment transfer Yes No No
account balance
Yes No No
account balance
Yes No No
View/download invoices Yes No No
Low balance notifications Yes No No
Manage environment sharing Yes No No

Environment-level sharing permissions

Action Environment owner Collaborating user permission
Default Change topology / SSH access
Adjust cloudlet limits
(vertical scaling)
Yes No Yes
Add/remove servers from an environment Yes No Yes
Configure auto horizontal scaling Yes No Yes
Receive horizontal scaling notifications Yes No Yes
View horizontal scaling history Yes No Yes
Configure load alerts Yes No Yes
Receive load alert notifications Yes No Yes
View load alert history Yes No Yes
Manage add-ons Yes No Yes
Node password reset emails Yes No Yes
Edit server configuration files Yes Yes Yes
View server logs Yes Yes Yes
View server resource usage Yes Yes Yes
View environment billing history Yes No No
Deploy code: own deployment manager Yes Yes Yes
Deploy code: git/svn repo Yes Yes Yes
Deploy code: FTP/FTPS Requires FTP/FTPS add-on (free) Requires free FTP/FTPS add-on Requires free FTP/FTPS add-on
Deploy code: SSH/SFTP Yes No Yes
Manage domain binding Yes Yes Yes
Manage custom SSL Yes Yes Yes
Start environment Yes Yes Yes
Stop environment Yes Yes Yes
Delete environment Yes No No
Clone environment Yes No No
Restart environment nodes Yes Yes Yes


Need More Help?

If you're still having problems, get in touch with our 24/7 support team! We'll be more than happy to help.