Skip to main content
All CollectionsGetting StartedManaging Users & Teams
SwipeGuide: Team Structure Best Practices πŸ‘₯
SwipeGuide: Team Structure Best Practices πŸ‘₯

Choose who can create, share, and publish Guides across Workspaces

Updated today

A team is a group of users in the Platform. You can create teams based on their location, departments, machines, etc. The members of a team can be assigned to a Role:

Platform Admin

Goal: Manage the platform and administer workspaces and teams.

Platform Admins can perform the following actions:​

  • Create Workspaces

  • Create Teams

  • Add new users to any Team

  • Resend user invitations

  • Create a branding theme for any Workspace

  • Create new guides

  • Edit existing Guides owned by any Team

  • Create and apply sign-offs

  • Publish Guides owned by any team in any Workspaces on their Platform

  • Share content with end-users through QR Codes or Share Links

  • See and export all checklist & sign-off results

  • See adoption & usage analytics

Admin

Goal: Manage Teams and Content

Admins can perform the following actions:

  • Add new users to their team

  • Resend user invitations

  • Edit their Team(s)

  • Create a branding theme for their Workspace

  • Set a Management Team for their Workspace

  • Create new guides

  • Edit existing guides owned by their Team

  • Create and apply sign-offs

  • Publish guides owned by their Team in the Workspaces assigned to their Team

  • Share content with end-users through QR Codes or Share links

  • See and export checklist & sign-off results on Guides belonging to my Team

  • See adoption & usage analytics for my Workspaces

Editor

Goal: Creating Guides & Editing Content

Editors can perform the following actions:

  • Create new guides for their Team

  • Edit existing guides owned by their Team

  • Publish guides owned by their Team in the Workspaces assigned to their Team

  • Share content with end-users through QR codes or links

  • See and export all checklist results on Guides belonging to my Team

  • See adoption & usage analytics for my Workspaces

Viewer

Goal: View Content & Share Feedback

Viewers can perform the following actions:

  • Log in on their Team(s) Workspaces

  • View Published Guides on their Team(s) Workspaces

  • Give Feedback on Guides, Instructions, and Steps

You can find below some examples of Team structure to help you define yours.

One Team β†’ Several Workspaces

Beer company Z has a Platform with the URL beercompanyz.swipeguide.com

This company has four breweries, called Brewery A, Brewery B, Brewery C, and Brewery D. Each brewery has its own dedicated Workspace where all of their published guides and instructions are located, under the Beer Company Z platform:

  • Brewery A: brewerya-beercompanyz.swipeguide.com

  • Brewery B: breweryb-beercompanyz.swipeguide.com

  • Brewery C: breweryc-beercompanyz.swipeguide.com

  • Brewery D: breweryd-beercompanyz.swipeguide.com

These breweries want to share best practices, since they have similar processes and equipment. Beer Company Z appoints one Team of experts, with users from all three breweries, to publish and share work instructions across all Workspaces in the Platform.

Several Teams β†’ One Workspace

Beer company Z has a Platform with the URL beercompanyz.swipeguide.com.

This company has one brewery, called Brewery A. This brewery has its own dedicated Workspace where all of their published guides and instructions are located.

Beer company Z appoints three expert Teams, each team consisting of people from different production lines. These Teams provide their expert knowledge about their lines to the shared workspace.

Several Teams β†’ Several Workspaces

Beer company Z has a Platform with the URL beercompanyz.swipeguide.com.

This company has four breweries, called Brewery A, Brewery B, Brewery C, and Brewery D. Each brewery has its own dedicated Workspace where all of their published guides and instructions are located, under the Beer Company Z platform:

  • Brewery A: brewerya-beercompanyz.swipeguide.com

  • Brewery B: breweryb-beercompanyz.swipeguide.com

  • Brewery C: breweryc-beercompanyz.swipeguide.com

  • Brewery D: breweryd-beercompanyz.swipeguide.com

Beer Company Z appoints three expert Teams, each team consisting of people from different production areas (production, bottling, cleaning, maintenance, etc.). These Teams provide their expert knowledge about their lines to all four shared workspaces.

Several Teams β†’ Specific Workspaces

Beer company Z has a Platform with the URL beercompanyz.swipeguide.com.

This company has four breweries, called Brewery A, Brewery B, Brewery C, and Brewery D. Each brewery has its own dedicated Workspace where all of their published guides and instructions are located, under the Beer Company Z platform:

  • Brewery A: brewerya-beercompanyz.swipeguide.com

  • Brewery B: breweryb-beercompanyz.swipeguide.com

  • Brewery C: breweryc-beercompanyz.swipeguide.com

  • Brewery D: breweryd-beercompanyz.swipeguide.com

Beer company Z appoints three expert Teams, each team consisting of people from different production areas (production, bottling, cleaning, maintenance, etc.).

These Teams provide their expert knowledge about their lines to all four shared workspaces:

Team 1 only has access to publish content to the Workspace of Brewery A.

Team 2 can publish content to all four Workspaces.

Team 3 can publish to the Workspaces of Brewery B and D, but not A and C.

Did this answer your question?