Multidev environments allow you to seamlessly collaborate on your website development projects, without coordinating local environments or trying to achieve parity with everyone’s local vagrant instance and the production server.
Creating a Multidev environment creates an application container with a database server, and connects them to backing services. It creates a Git branch of your codebase from the Master branch, and checks it out in the Multidev environment's application container. It clones the database from the specified environment into the new database server, and clones the filesystem similarly. The new Multidev environment has a unique URL, and behaves the same as the Development environment, with the ability to receive code changes via Git pushes or SFTP file uploads. Multidev environments cannot have custom domains.
From within the Organization Dashboard, you can assign organization members one of three roles: Administrator, Team Member, and Developer. Developers in an organization can commit code to Multidev and Development environments, but cannot deploy code or clone databases and files into Test or Live environments.
Only sites owned by Enterprise and EDU+ can assign the developer role to specific users. Partner Organizations cannot specify which members have access to specific sites.
The person who creates the site owns it until someone else starts paying for it. The user or Enterprise Organization who pays for the site is the owner thereafter.
See Role-Based Permissions & Change Management for details.
When you or the administrators, team members, or developers in your agency create sites, you have the option of associating it with your organization. Once associated, all members of the organization can access the Site's Dashboard from the Organization Dashboard.
Any large agency that has multiple developers who login frequently via username/password will trigger failed logins for everyone else who works on the site. This occurs despite everyone using the right password and even when one user logins in and out successfully 3 times.
As a workaround, we recommend following development best practice workflows by authenticating via SSH key for password-less access.
Only organizational team members and administrators of a Supporting Organization with Multidev will be able to use this feature. Site team members who are associated with the site but not the agency can access Multidev environments via the unique URL, but will not be able to commit code to them.
Enterprise, Reseller, OEM, and EDU+ organizations own sites. Registered Agencies, Pantheon Partners, Premier Pantheon Partners, Strategic Pantheon Partners, and EDU organizations support sites. This is because an agency's role is to develop, service, and maintain a site on behalf of its owner. Read more about owning and supporting sites in our Organizations doc.
No. Only the owner of the site can add an agency as a Supporting Organization. This action grants all members of the organization access to the site. You should ask site owners to add your agency as a Supporting Organization if you are providing services to the site.
All organization members have access to the site, with permissions determined by their roles at the organization level.
Can the site owner override privileges and access for organizational team members of a Supporting Organization?
Yes, but only for sites owned by Enterprise or EDU+ organizations. Roles designated on the Site Team modal will override any roles assigned within the organization.
If you need to submit a support request and can’t access the Dashboard, send an email to firstname.lastname@example.org.
Your support level increases along with your Partner Program level. Refer to the Pantheon Partner Portal for more information.
Each member of an organization can create up to 10 Sandbox sites. When the limit of 10 is reached, taking a site live or deleting unused sites will free up additional Sandbox slots.
No, we don’t support them.