Local for Teams provides simple collaboration for development teams working on WordPress. Developers have access to sites across an Organization and can pull down shared sites right from their Flywheel dashboard to Local.
Teams offers user management, user roles, and priority support on top of what is provided in the community forums.
Haven’t tried Local yet? Find out why over 150,000 developers use Local for their WordPress workflow and download it now, for free!
In addition to all the features you get with Local Community, Local for Teams will give you access to:
Local for Teams integrates directly to our Flywheel hosting dashboard – specifically our Organizations feature. This provides you with the ability to invite users to your Local for Teams account. Each person invited gets the Teams features within Local.
By default, Local for Teams gives an Organization five “seats” that can be filled by members of the Organization. This number can be increased by purchasing additional seats. The owner of the Org is the only one who can manage which members occupy those seats.
As the owner of a Flywheel Organization, you can set privileges for each member of the organization. For example, you can choose whether a team member can deploy site changes to your staging and production environments or just the staging environment.
If you’d like to revoke a user’s access to Local for Teams, simply select the ellipses icon for their user on the organization dashboard members tab. You’ll see an option to remove this user’s access to Local for Teams.
Organization Owners, who want more info about setting up the Organization should see this help doc: How do I set up my Local for Teams account?
Keeping your websites organized is key to managing multiple sites, which is why we’ve created Workspaces in Local for Teams!
You can think of Workspaces as a way of grouping sites within Local. There are two kinds of Workspaces: Personal and Teams. Users can easily switch between their personal and team workspaces from the sidebar.
The Workspace switcher is used to change between multiple workspaces, and is found in the upper left-hand corner of Local:
Only Local sites that are contained within the Organization’s Workspace can push to sites that are owned by a Local for Teams organization.
The Personal workspace is where non-Teams sites are contained. For example, if you own or are a collaborator on a site that is NOT part of a Local for Teams Organization, it will be accessible from the Personal Workspace.
If you want to push a site within the Personal Workspace to a site owned by a Local for Teams’ Organization, you have to move the site into the Organization’s Workspace. For more info, see this guide!
To learn more about Local for Teams and how it compares to Local Community or Local Pro, head to the Local pricing page.
It’s free and always will be.
Thanks! We'll contact you as soon as Local for Windows is available.
Next-level functionality and enhanced local development.
Sign up below and we’ll notify you the minute Local Pro is available for beta! Launching July 2019.
Thanks! We'll contact you as soon as the beta is available.
Local is only available as a desktop application, but no worries! Just enter your email in the box below and we'll send you a little reminder to download it via your desktop.
Thanks! Check your inbox for a link to download Local on your desktop.