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 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 users to work with you, how they’re displayed in your user list, giving each user a nickname or alias so that you can identify them more easily, and 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 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.
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.
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.
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
|Account holder||Collaborating user permission|
|Default||Create new environments|
(change env. owner)
|Cancel pending environment transfer|
|Low balance notifications|
|Manage environment sharing|
Environment-level sharing permissions
|Environment owner||Collaborating user permission|
|Default||Change topology / SSH access|
|Adjust cloudlet limits
|Add/remove servers from an environment|
|Configure auto horizontal scaling|
|Receive horizontal scaling notifications|
|View horizontal scaling history|
|Configure load alerts|
|Receive load alert notifications|
|View load alert history|
|Node password reset emails|
|Edit server configuration files|
|View server logs|
|View server resource usage|
|View environment billing history|
|Deploy code: own deployment manager|
|Deploy code: git/svn repo|
|Deploy code: FTP/FTPS|
|Deploy code: SSH/SFTP|
|Manage domain binding|
|Manage custom SSL|
|Restart environment nodes|
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.