|
| 1 | +--- |
| 2 | +title: Make the Dream Work: Use the Teams Feature in Stately Studio |
| 3 | +description: Getting the most out of Stately Studio's teams feature |
| 4 | +tags: [stately studio, xstate, teams, machine versions, machine locking] |
| 5 | +authors: [gavin] |
| 6 | +slug: using-teams-in-stately-studio |
| 7 | +image: |
| 8 | +date: 2023-09-15 |
| 9 | +--- |
| 10 | + |
| 11 | +Our team knew early on that users needed the ability to share machines in the Studio and build on each others' work. |
| 12 | +We also needed the Studio to be an effective tool for teams to work together and share context. |
| 13 | +But how do we do that safely, making sure the right eyes were on the right machines? |
| 14 | +And how do we protect against accidental mishaps that have plagued devs since the dawn of the computer? |
| 15 | +Being a distributed dev team ourselves, we've shared these same pain points, and decided to build a solution directly in the Studio. |
| 16 | +Enter [Stately teams](https://stately.ai/docs/teams), our way to provide privacy and safety while allowing effortless collaboration. |
| 17 | + |
| 18 | +## Why would I need this? |
| 19 | +Great question, and we're glad you asked! |
| 20 | +While we have the [Discover](https://stately.ai/registry/discover) page, which showcases over 20 thousand(!) community-created machines, we know that statcharts can contain critical details about core algorithms or can have processes that give businesses a competitive edge. |
| 21 | +Many users expressed interest in keeping these types of machines private, and we listened. |
| 22 | + |
| 23 | + |
| 24 | +## Teams 101 |
| 25 | + |
| 26 | +Teams is an exclusive feature for [**Pro** and Enterprise users](https://stately.ai/pricing) that allows them to collaborate on different projects without needing to make them publicly visible. Team owners have the ability to assign roles that map closely with their team members' intended set of responsibilities. |
| 27 | + |
| 28 | + |
| 29 | + |
| 30 | +### Access control |
| 31 | +There are many times when a dev team needs to share their work context with others without granting them full rights to the projects. |
| 32 | +For example, Lenny in accounting probably shouldn't have access to the company repo, but he could benefit from visually understanding the steps involved in processes and workfows. |
| 33 | +Having different teams with different roles allows us to keep parties informed without added risk. |
| 34 | +Don't trust your PM's trigger finger? Make them a [viewer](https://stately.ai/docs/teams#viewer-role); we promise not to tell. |
| 35 | +Taking a vacation before new members can be onboared? |
| 36 | +Make another teammate an [admin](https://stately.ai/docs/teams#admin-role). |
| 37 | +Checkout all our roles and permissions in our [docs](https://stately.ai/docs/teams#team-roles). |
| 38 | + |
| 39 | +### Sharing conveniently and safely |
| 40 | +There are ways to share machine visualizations in the Studio without teams, but they're not ideal for many users. |
| 41 | +Users can make their projects and machines public, but that is a no-go for most businesses. |
| 42 | +Alternatively, Pro users could keep their projects private and only share with people they trust by exporting and re-importing. However, that invites potentially different sources of truth, adds potential confusion, and lacks a truly shared context. |
| 43 | +Inviting users to collaborate on the same private team grants them the ability to share without the exporting and copy/paste gymnastics. |
| 44 | + |
| 45 | +### Superpower Pro features |
| 46 | +Having teams allows other features to shine. For example, we all know the value of collaboration, but more users naturally add more potential for mistakes to happen, even with proper roles assigned. To protect against mistakes, we've added the ability to [lock machines](https://stately.ai/docs/lock-machines), preventing teammates from accidentally overwriting or deleting machines. |
| 47 | + |
| 48 | + |
| 49 | + |
| 50 | + |
| 51 | +Team members often need to manage and track variants of the same machine, so we added the ability to create [machine versions](https://stately.ai/docs/versions). Members can edit and save specific checkpoints of their machines and can even see the last person to and save a specific version. Team roles come into play here again by allowing only owners and admins to actually delete versions. |
| 52 | + |
| 53 | + |
| 54 | + |
| 55 | + |
| 56 | +## FAQ's |
| 57 | + |
| 58 | +### Who can join my team? |
| 59 | +Anyone with an email address can be invited to a team! |
| 60 | +If they are not already members, they will have to [sign up for a Stately account](https://stately.ai/registry/login?). |
| 61 | + |
| 62 | +### How many users can be on a team? |
| 63 | +A team can have as many members as there are seats in your Pro or Enterprise plan, except for viewers. |
| 64 | +Viewers are free to add. |
| 65 | + |
| 66 | +### Does inviting a user take up a seat on the team? |
| 67 | +The seat is only taken once a user accepts the invite and claims the seat. |
| 68 | +If the invite was not accepted, the seat remains free. |
| 69 | + |
| 70 | + |
| 71 | +### Can I swap member's roles and reclaim seats? |
| 72 | +Yes, but only owners and admins have the ability to reassign roles. |
| 73 | +Any role except the owner may choose to leave the team, however. |
| 74 | +The owner can instead delete the team. |
| 75 | + |
| 76 | + |
| 77 | +For more detailed information on Stately teams, visit our page in the [docs](https://stately.ai/docs/teams#teams-members-and-pro-plan-seats)! |
0 commit comments