Local Help Docs Pro & Teams

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 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:

  • Link Checker — Scan the links of your site’s content and quickly take steps to fix broken ones.
  • Live Links Pro — Quickly share a Local site’s progress as well as gather feedback from a team or client.
  • 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.

The above features are the same features that are available for a Local Pro users, however, having a Local for Teams subscription unlocks additional features within the Flywheel Dashboard:

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

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.

note

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.

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

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.

note

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?


Workspaces

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:

Pro-tip:

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

Teams Workspace

Only Local sites that are contained within the Organization’s Workspace can push to sites that are owned by a Local for Teams organization.

Personal Workspace

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.

note

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.