Skip to content

Commit a575cf8

Browse files
committed
merge remote and address feedback.
2 parents 4c641ae + d0ef1dc commit a575cf8

File tree

1 file changed

+41
-35
lines changed
  • blog/2023-09-15-teams-feature-overview

1 file changed

+41
-35
lines changed
Lines changed: 41 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -1,37 +1,40 @@
11
---
2-
title: Make the dream work! An overview of Stately Studio's teams feature
3-
description: Getting the most out of Stately Studio's teams feature
2+
title: Make the dream work! An overview of Stately Studios teams feature
3+
description: Getting the most out of Stately Studios teams feature
44
tags: [stately studio, xstate, teams, machine versions, machine locking]
55
authors: [gavin]
66
slug: using-teams-in-stately-studio
77
image: /blog/2023-09-15-stately-teams-overview.png
88
date: 2023-09-19
99
---
1010

11-
Our team knew early on that users needed the ability to share machines in the Studio and build on each other's 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.
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, weve shared these same pain points, and decided to build a solution directly in the Studio.
1616
Enter [Stately teams](https://stately.ai/docs/teams), our way to provide privacy and safety while allowing effortless collaboration.
1717

1818
<!--truncate-->
1919

20-
## Why would I need this?
21-
Great question, and we're glad you asked!
22-
While we have the [Discover](https://stately.ai/registry/discover) page, which showcases over 20 thousand(!) community-created machines, we know that statecharts can contain critical details about core algorithms or can have processes that give businesses a competitive edge.
20+
## Why would I need a team?
21+
22+
Great question, and we’re glad you asked!
23+
While we have the [Discover](https://stately.ai/registry/discover) page, which showcases over 20 thousand(!) community-created machines, we know that statecharts can contain critical details about core algorithms or can have processes that give businesses a competitive edge.
2324
Many users expressed interest in keeping these types of machines private, and we listened.
2425

2526
### Sharing machine visualizations with teammates
27+
2628
Developing software is collaborative by nature. To get any product launched, bug fixed, or feature shipped, teams need to work together under the same shared context.
27-
As projects grow in scope and complexity, it gets easier for team members to lose track of the bigger picture.
28-
Team members may get lost in the weeds of their own work while the rest of the project changes around them, or they may not have the full context of the project and make decisions that don't align with the team's goals.
29-
This is where the Studio's teams feature comes in.
29+
As projects grow in scope and complexity, it gets easier for team members to lose track of the bigger picture.
30+
Team members may get lost in the weeds of their own work while the rest of the project changes around them, or they may not have the full context of the project and make decisions that dont align with the teams goals.
31+
This is where the Studios teams feature comes in.
3032
Visualizing app logic as statecharts allows teams to see the entire project at a glance, and the ability to share these visualizations empowers each member to make well-informed decisions, regardless of discipline.
31-
Every teammate may not be a dev, but we're confident that every teammate can benefit from a well thought out flowchart!
33+
Every teammate may not be a dev, but were confident that every teammate can benefit from a well-thought-out flowchart!
3234

3335
## Teams 101
34-
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.
36+
37+
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 can assign roles that map closely with their team members’ intended set of responsibilities.
3538

3639
![The Stately Studio Next team members tab. Under Owners/Admin, Kevin is labeled as Owner. David is an admin. Laura, Farzad and Gavin are listed under Editors. Anders, cirephe, and Mateusz are listed under Viewers.](./teamVNext.png)
3740

@@ -45,56 +48,59 @@ Make another teammate an [admin](https://stately.ai/docs/teams#admin-role).
4548
[Checkout all our roles and permissions in our docs](https://stately.ai/docs/teams#team-roles).
4649

4750
### Sharing conveniently and safely
48-
There are ways to share machine visualizations in the Studio without teams, but they're not ideal for many users.
51+
52+
There are ways to share machine visualizations in the Studio without teams, but they’re not ideal for many users.
4953
Users can make their projects and machines public, but that is a no-go for most businesses.
5054
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.
5155
Inviting users to collaborate on the same private team allows them to share without the exporting and copy/paste gymnastics.
5256

5357
### A source of what, now?
54-
Simply put, a "source of truth" is a single place where all the information about a project is stored.
58+
59+
Simply put, a “source of truth” is a single place where all the information about a project is stored.
5560
In our case, we wanted to make sure that teams have a single place to view and collaborate on machine visualizations, and that place is a team-based project in the Studio.
56-
This prevents confusion and allows for a shared context between all members of the team. With a proper source of truth configured, we can avoid situations like this:
61+
This prevents confusion and allows for a shared context between all team members. With a proper source of truth configured, we can avoid situations like this:
5762

5863
![Four files with the filenames: onboardMachine.json, onboardMachine-final.json, onboardMachine-final-final.json, onboardMachine-actual-final-for-real-this-time.json.](/blog/2023-09-15-file-confusion.png)
5964

65+
### But what about source control? Shouldn’t that be the source of truth?
6066

61-
### But what about source control? Shouldn't that be the source of truth?
62-
Ideally, yes, the team's repository is the single source of truth for all application logic, but not every member of the team is a developer, nor should they all have access to source code.
67+
Ideally, yes, the team’s repository is the single source of truth for all application logic, but not every team member is a developer, nor should they all have access to source code.
6368
That said, we know teams need to ensure their machines in the Studio are always in lockstep with the rest of their source, so we added the ability to [import machines directly from GitHub](https://stately.ai/docs/import-from-github).
64-
We're also working on a full-fledged GitHub Sync feature, allowing users to save machines as commits back to their source repos! Check out Anders' demo showing off the feature [here](https://www.youtube.com/watch?v=WelBycMg2eA&t=1293s).
65-
66-
67-
69+
We’re also working on a full-fledged GitHub Sync feature, allowing users to save machines as commits back to their source repos! [Check out Anders’ demo previewing GitHub Sync in our recent office hours live stream](https://www.youtube.com/watch?v=WelBycMg2eA&t=1293s).
6870
### Superpower Pro features
69-
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.
7071

71-
![locked machine](./lockedScreenshot.png)
72+
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.
7273

74+
![A machine with locked status in Stately. Hovering over the status shows the information that the machine was Locked by cirephe on September 8, 2023 at 07:48PM.](./lockedScreenshot.png)
7375

7476
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.
7577

76-
![](./versionScreenshot.png)
77-
78+
![Machine versions panel in Stately. The current version is named Gavin’s ultimate joke machine. The previous version is a generated flow for a “A flow showing someone how to be funny.”](./versionScreenshot.png)
7879

79-
## FAQ's
80+
## FAQs
8081

8182
### Who can join my team?
83+
8284
Anyone with an email address can be invited to a team!
8385
If they are not already members, they will have to [sign up for a Stately account](https://stately.ai/registry/login?).
8486

85-
### How many users can be on a team?
86-
A team can have as many members as there are seats in your Pro or Enterprise plan, except for viewers.
87-
Viewers are free to add.
87+
### How many users can be on a team?
88+
89+
A team can have as many members as there are seats in your Pro or Enterprise plan, except for viewers.
90+
Viewers are free to add.
8891

8992
### Does inviting a user take up a seat on the team?
90-
The seat is only taken once a user accepts the invite and claims the seat.
91-
If the invite was not accepted, the seat remains free.
9293

94+
The seat is only taken once a user accepts the invite and claims the seat.
95+
If the invite was not accepted, the seat remains free.
9396

9497
### Can I swap member roles and reclaim seats?
9598
Yes, but only owners and admins have the ability to reassign roles.
9699
Any role except the owner may choose to leave the team, however.
97100
The owner can instead delete the team.
98101

102+
Yes, but only owners and admins can reassign roles.
103+
Any role except the owner may choose to leave the team, however.
104+
The owner can instead delete the team.
99105

100-
For more detailed information on Stately teams, visit our page in the [docs](https://stately.ai/docs/teams#teams-members-and-pro-plan-seats)!
106+
For more detailed information, visit our [Stately teams page in the docs](https://stately.ai/docs/teams#teams-members-and-pro-plan-seats)!

0 commit comments

Comments
 (0)