Local Help Docs Pro & Teams

What is Local for Teams?

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.

note

Haven’t tried Local by Flywheel yet? Find out why over 150,000 developers use Local for their WordPress workflow and download it now, for free!

Local for Teams features

In addition to all the features you get with Local Community, Local for Teams will give you access to:

  • MagicSync – Forget about FTP. Use MagicSync to push only the files you’ve edited! It’s a faster and more reliable way to push big sites.
  • Staging deployments – Local Pro gives you the power to push to staging before production, so you can be confident in your work before going live.
  • Priority support – Get in-app support on top of the Local Forums. Local Pro gives you access to over 100 WordPress experts ready to help you troubleshoot.
  • User management – Invite new team members, or edit existing members, from Flywheel’s dashboard.
  • User roles – Control which members of your Organization can push to staging or production, right from the Flywheel app.
  • Workspaces – Your personal and professional projects are organized neatly within their own workspaces. 

MagicSync

MagicSync is our one-of-a-kind technology that syncs only the files that have changed since your last push or pull. This gives you visibility into file changes and greatly improves deployment (and is more secure, more reliable, and faster than FTP deployment solutions).

MagicSync works with both pushing and pulling sites, with both staging and production deployment. With MagicSync, you can preview your changes before they go live and benefit from:

  • Cache busting: We’ll clear your site’s cache when you launch changes.
  • Backups: We back up your site every two hours when you’re pushing changes.
  • Security: Unlike FTP (which exposes a direct connection to your site), MagicSync is routed through a separate micro-service before deploying.

MagicSync is included in Local Pro and Local for Teams.


Staging deployments

Users will have the ability to push to/pull from production and staging environments on Flywheel! As a Local for Teams customer, a new staging option appears when you choose to push or pull from a site on Flywheel.

Staging deployments is included in Local Pro and Local for Teams.


Premium support for Local

Don’t worry about leaving Local to find answers to your questions. With Local for Teams, you can submit support tickets directly from the app to Flywheel’s talented team of WordPress experts!

Submitting a ticket from Local will also send along important diagnostic logs/data to help us resolve your issue faster. Need in-depth support? We can remote into your computer and troubleshoot your Local for Pro installation.

Support for Local is included in Local Pro and Local for Teams.


User management

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 Flywheel.

note

Local for Teams gives an Organization five “seats” that can be filled by members of the Org. 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.

Owners of the Organization can control:

  • Whether the user has a Local for Teams seat
  • Whether the user can push to staging and production OR only to staging

User roles

Owners of the Organization can set privileges for each member that is added. You’ll be able to choose whether they can deploy site changes to your staging and/or production environments.

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.


Workspaces

Keeping your websites organized is key to managing multiple sites, which is why we’ve created Workspaces in Local for Teams! When users sign up, it automatically separates their personal and Team sites into Workspaces, keeping private and professional projects organized.

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:

Pro-tip:

  • Personal workspace icons are circular
  • Organization workspaces are rounded squares. 

Personal workspace: 

The Personal workspace is where non-”Local for 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.

note

If you want to push a Personal site to a site hosted in a Local for Teams’ Organization, you have to move the site into the Org’s Workspace. This guide will show you how!

To learn more about Local for Teams and how it compares to Local Community or Local Pro, head to the Local pricing page.