For developers

Roles & Permissions

4min

The hosting configuration supports creation of user accounts for developers with the following roles:

  • Developer
  • Lead Developer
  • Release Manager

Developer permissions

  • Can create, update and delete development environments
  • Can log into (aka "ssh") development environments
  • Can execute commands on development environments
  • Can copy files between local and development environments
  • Can access development environment logs
  • Can download partial database backups (without personal identifiable information)
  • Can download backups with file assets (user generated content)
  • Can NOT access anything related to production environments
  • Can NOT trigger backups from the production environment
  • Can NOT download full database backups

Lead Developer permissions

  • Can create, update and delete development environments
  • Can create and update production environments
  • Can log into (aka "ssh") development and production environments
  • Can execute commands on development and production environments
  • Can copy files between local, development and production environments
  • Can access development and production environment logs
  • Can download partial (without personal identifiable information) and full database backups
  • Can download backups with file assets (user generated content)
  • Can trigger manual backups from the production environment
  • Can NOT delete production environment

Release Manager permissions

This role is designed for CI/CD tools like CircleCI, TravisCI, Github Actions or similar to manage automated code deployments without human involvement.

  • Can create, update and delete development environments
  • Can create and update production environments
  • Can log into (aka "ssh") development and production environments
  • Can execute commands on development and production environments
  • Can copy files between local, development and production environments
  • Can access development and production environment logs
  • Can NOT access database backups
  • Can NOT access backups with file assets (user generated content)
  • Can trigger manual backups from the production environment
  • Can NOT delete production environment