Squash only requests the absolutely minimum set of permissions on Bitbucket. When you signup you will be prompted to the following screens: Oauth This is the standard Bitbucket authorization page requesting your permission to give Squash access to your account. Squash needs your email address in order to communicate with you in the future for

Squash only requests the absolutely minimum set of permissions on GitHub. When you signup you will be prompted to the following screens: Oauth This is the standard GitHub authorization page requesting your permission to give Squash access to your account. We only request read access to basic information. You may also grant access to any

How many different organizations can I use with each Squash plan? Each Squash plan is tied to only one organization or one individual/personal account (if you are planning to use Squash with your own personal account, outside an organization). There is no limit of users on each organization though. If you are planning to use

Are Squash URLs accessible to users outside my organization? By default yes, and you can also change this to restrict their visibility only to your organization members. How can I reduce the build & startup time of my deployments? Please go to How to reduce the build & startup times of my app. How can

Custom Environment Variables You can define custom environment variables from the Squash admin interface. Go to Settings -> Repositories and then click on “Settings” for a given repository. Each environment variable defined on this page will become available within the deployment host. They can also become available within docker containers with a few configuration steps (see

When you start a new deployment Squash will perform the following steps in this order below. You may also check this quick intro on how Squash works. Finding a Build plan Squash first searches for a Squash YAML file. If the file is not present then it checks if there is a deployment profile defined