@@ -8,7 +8,7 @@ image: /blog/2023-09-15-stately-teams-overview.png
8
8
date : 2023-09-19
9
9
---
10
10
11
- Our team knew early on that users needed the ability to share machines in the Studio and build on each others' work.
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
12
We also needed the Studio to be an effective tool for teams to work together and share context.
13
13
But how do we do that safely, making sure the right eyes were on the right machines?
14
14
And how do we protect against accidental mishaps that have plagued devs since the dawn of the computer?
@@ -33,30 +33,29 @@ Every teammate may not be a dev, but we're confident that every teammate can ben
33
33
## Teams 101
34
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.
35
35
36
- 
36
+ 
37
37
38
38
### Access control
39
39
There are many times when a dev team needs to share their work context with others without granting them full rights to the projects.
40
40
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 workflows.
41
- Having different teams with different roles allows us to keep parties informed without added risk.
41
+ Having different teams with different roles lets us to keep parties informed without added risk.
42
42
Don't trust your PM's trigger finger? Make them a [viewer](https://stately.ai/docs/teams#viewer-role); we promise not to tell.
43
43
Taking a vacation before new members can be onboarded?
44
44
Make another teammate an [admin](https://stately.ai/docs/teams#admin-role).
45
- Checkout all our roles and permissions in our [ docs](https://stately.ai/docs/teams#team-roles).
45
+ [ Checkout all our roles and permissions in our docs](https://stately.ai/docs/teams#team-roles).
46
46
47
47
### Sharing conveniently and safely
48
48
There are ways to share machine visualizations in the Studio without teams, but they're not ideal for many users.
49
49
Users can make their projects and machines public, but that is a no-go for most businesses.
50
50
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.
51
- Inviting users to collaborate on the same private team grants them the ability to share without the exporting and copy/paste gymnastics.
51
+ Inviting users to collaborate on the same private team allows them to share without the exporting and copy/paste gymnastics.
52
52
53
53
### A source of what, now?
54
54
Simply put, a " source of truth" is a single place where all the information about a project is stored.
55
55
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
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:
57
57
58
- 
59
-
58
+ 
60
59
61
60
62
61
### But what about source control? Shouldn't that be the source of truth?
@@ -92,7 +91,7 @@ The seat is only taken once a user accepts the invite and claims the seat.
92
91
If the invite was not accepted, the seat remains free.
93
92
94
93
95
- ### Can I swap member's roles and reclaim seats?
94
+ ### Can I swap member roles and reclaim seats?
96
95
Yes, but only owners and admins have the ability to reassign roles.
97
96
Any role except the owner may choose to leave the team, however.
98
97
The owner can instead delete the team.
0 commit comments