Skip to content

Commit 4c641ae

Browse files
committed
Pr feedback points.
1 parent bd12dc3 commit 4c641ae

File tree

1 file changed

+7
-8
lines changed
  • blog/2023-09-15-teams-feature-overview

1 file changed

+7
-8
lines changed

blog/2023-09-15-teams-feature-overview/index.mdx

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ 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 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.
1212
We also needed the Studio to be an effective tool for teams to work together and share context.
1313
But how do we do that safely, making sure the right eyes were on the right machines?
1414
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
3333
## Teams 101
3434
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.
3535

36-
![team screenshot](./teamVNext.png)
36+
![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)
3737

3838
### Access control
3939
There are many times when a dev team needs to share their work context with others without granting them full rights to the projects.
4040
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.
4242
Don't trust your PM's trigger finger? Make them a [viewer](https://stately.ai/docs/teams#viewer-role); we promise not to tell.
4343
Taking a vacation before new members can be onboarded?
4444
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).
4646

4747
### Sharing conveniently and safely
4848
There are ways to share machine visualizations in the Studio without teams, but they're not ideal for many users.
4949
Users can make their projects and machines public, but that is a no-go for most businesses.
5050
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.
5252

5353
### A source of what, now?
5454
Simply put, a "source of truth" is a single place where all the information about a project is stored.
5555
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.
5656
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:
5757

58-
![true misery](/blog/2023-09-15-file-confusion.png)
59-
58+
![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)
6059

6160

6261
### 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.
9291
If the invite was not accepted, the seat remains free.
9392

9493

95-
### Can I swap member's roles and reclaim seats?
94+
### Can I swap member roles and reclaim seats?
9695
Yes, but only owners and admins have the ability to reassign roles.
9796
Any role except the owner may choose to leave the team, however.
9897
The owner can instead delete the team.

0 commit comments

Comments
 (0)