AWS quick documentation change
Summary
Restructured sharing documentation with simplified permissions model, removed detailed sharing scenarios, and added step-by-step sharing instructions
Security assessment
The changes primarily reorganize content about sharing mechanics without introducing new security controls or addressing vulnerabilities. The permission model simplification (Viewer/Co-owner) clarifies access levels but doesn't indicate response to security issues. The approval review mention is carried forward but not new.
Diff
diff --git a/quick/latest/userguide/sharing-flows.md b/quick/latest/userguide/sharing-flows.md index 01f712e49..23627b806 100644 --- a//quick/latest/userguide/sharing-flows.md +++ b//quick/latest/userguide/sharing-flows.md @@ -5 +5 @@ -How sharing worksPrivate sharing with individualsPrivate sharing with groupsShare with everyoneViewer permissionsCo-owner permissionsTips for successSharing and permissions reference +Sharing optionsHow to share a flowPermission levels @@ -9 +9 @@ How sharing worksPrivate sharing with individualsPrivate sharing with groupsShar -Sharing allows you to make your flows available to other people in your organization. When you share a flow, you're giving others permission to view, run, and potentially collaborate on your work. Think of sharing as publishing your flow - it moves from being a private draft that only you can see to being accessible by the people or groups you specify. +When you share a flow, you give others permission to view and run it, or to collaborate on it as co-owners. @@ -11 +11 @@ Sharing allows you to make your flows available to other people in your organiza -Sharing is essential for collaboration, knowledge sharing, and making your flows useful to your broader team or organization. +## Sharing options @@ -13 +13 @@ Sharing is essential for collaboration, knowledge sharing, and making your flows -## How sharing works +You can share a flow in three ways: @@ -15 +15 @@ Sharing is essential for collaboration, knowledge sharing, and making your flows -Amazon Quick Flows offers flexible sharing options that let you control exactly who can access your flows and what they can do with them. Your sharing choices depend on your role and your organization's approval review settings. + * **With individuals** — Share with specific people using their email addresses. @@ -17 +17 @@ Amazon Quick Flows offers flexible sharing options that let you control exactly -### Types of sharing + * **With groups** — Share with pre-defined groups in your organization (for example, departments or project teams). @@ -19 +19 @@ Amazon Quick Flows offers flexible sharing options that let you control exactly -You can share flows in three different ways, each serving different collaboration needs: + * **With everyone** — Make the flow available to all users in your Amazon Quick Flows instance. @@ -21 +20,0 @@ You can share flows in three different ways, each serving different collaboratio -🔒 Private sharing with individuals @@ -24 +22,0 @@ You can share flows in three different ways, each serving different collaboratio -**What it is:** Share your flow with specific people using their email addresses @@ -26 +24 @@ You can share flows in three different ways, each serving different collaboratio -**Best for:** Testing with colleagues, sharing with specific team members, or controlled distribution +Depending on your organization's settings, sharing may require approval review. For more information, see [Approval review](./approval-review.html). @@ -28 +26 @@ You can share flows in three different ways, each serving different collaboratio -**Who can do this:** Author, Admin, Author Pro, and Admin Pro users +## How to share a flow @@ -30 +28 @@ You can share flows in three different ways, each serving different collaboratio -👥 Private sharing with groups + 1. Open your flow. @@ -31,0 +30 @@ You can share flows in three different ways, each serving different collaboratio + 2. Choose **Share**. @@ -33 +32 @@ You can share flows in three different ways, each serving different collaboratio -**What it is:** Share your flow with pre-defined groups in your organization + 3. Select how you want to share: with individuals, groups, or everyone. @@ -35 +34 @@ You can share flows in three different ways, each serving different collaboratio -**Best for:** Department-wide sharing, team collaboration, or role-based access + 4. For individuals, enter email addresses. For groups, search for and select the group. @@ -37 +36 @@ You can share flows in three different ways, each serving different collaboratio -**Who can do this:** Author, Admin, Author Pro, and Admin Pro users + 5. Choose the permission level: **Viewer** or **Co-owner**. @@ -39 +38 @@ You can share flows in three different ways, each serving different collaboratio -🌐 Share with everyone + 6. Choose **Share**. @@ -42 +40,0 @@ You can share flows in three different ways, each serving different collaboratio -**What it is:** Make your flow available to all users in your Amazon Quick Flows instance @@ -44 +41,0 @@ You can share flows in three different ways, each serving different collaboratio -**Best for:** Organization-wide tools, widely useful flows, or public resources @@ -46 +43 @@ You can share flows in three different ways, each serving different collaboratio -**Who can do this:** Author, Admin, Author Pro, and Admin Pro users (may require approval) +## Permission levels @@ -48 +45 @@ You can share flows in three different ways, each serving different collaboratio -## Private sharing with individuals +### Viewer @@ -50 +47 @@ You can share flows in three different ways, each serving different collaboratio -Private sharing with individuals gives you precise control over who can access your flow. This is perfect for collaboration with specific colleagues or when you want to test your flow with a select group before broader distribution. +Viewers can run the flow and view results, but cannot edit, share, or delete it. Viewers only see the published version. @@ -52 +49 @@ Private sharing with individuals gives you precise control over who can access y -### How to share with individuals +### Co-owner @@ -54 +51 @@ Private sharing with individuals gives you precise control over who can access y - * **Complete your flow** \- Ensure it's ready for others to use +Co-owners can edit the flow, share it with others, manage permissions, publish changes, and access draft versions. Co-owners cannot remove the original owner. Only one person can edit at a time. @@ -56,219 +53 @@ Private sharing with individuals gives you precise control over who can access y - * **Click the share button** \- Access sharing options from your flow - - * **Add email addresses** \- Enter the full email addresses of people you want to share with - - * **Choose permissions** \- Select whether they should be viewers or co-owners - - * **Add a message** (optional) - Include context about your flow - - * **Share the flow** \- Send invitations to your selected users - - - - -### What happens when you share - - * **Recipients get notified** \- They'll receive an email notification about the shared flow - - * **Flow appears in their library** \- They can find it in their Amazon Quick Flows library - - * **Access is immediate** \- They can start using the flow right away (unless approval is required) - - * **You maintain control** \- You can modify sharing permissions or remove access at any time - - - - -### Best practices for individual sharing - - * **Use full email addresses** \- Ensure you have the correct email for each person - - * **Include context** \- Add a brief message explaining what the flow does and why you're sharing it - - * **Start small** \- Test with a few people before sharing more broadly - - * **Check permissions** \- Verify that shared users have access to any required data sources - - - - -## Private sharing with groups - -Group sharing allows you to share flows with pre-defined groups in your organization, making it easy to collaborate with entire teams or departments without managing individual email addresses. - -### Understanding groups - -Groups are collections of users that your organization's administrators have set up in your identity system. Common examples include: - - * Department groups (Marketing, Sales, Engineering) - - * Project teams (Project Alpha, Q4 Initiative) - - * Role-based groups (Managers, Analysts, Executives) - - * Location-based groups (Seattle Office, Remote Workers) - - - - -### How to share with groups - - * **Access sharing options** \- Click the share button in your flow - - * **Select group sharing** \- Choose the option to share with groups - - * **Find your group** \- Search for or select the appropriate group from the list - - * **Set permissions** \- Choose viewer or co-owner access for the group - - * **Add context** \- Include a message about the flow's purpose - - * **Share with the group** \- Send the flow to all group members - - - - -## Share with everyone - -Sharing with everyone makes your flow available to all users in your Amazon Quick Flows instance. This is the broadest form of sharing and is ideal for flows that provide value to your entire organization. - -### When to share with everyone - -Consider organization-wide sharing when your flow: - - * **Solves common problems** \- Addresses needs that many people have - - * **Provides general utility** \- Offers broadly useful functionality - - * **Represents best practices** \- Demonstrates good flow design for others to learn from - - * **Supports organizational goals** \- Helps achieve company-wide objectives - - - - -### How to share with everyone - - * **Prepare your flow** \- Ensure it's polished and ready for wide distribution - - * **Access sharing settings** \- Click the share button in your flow - - * **Select "Share with all"** \- Choose the organization-wide sharing option - - * **Add description** \- Provide clear information about what the flow does - - * **Submit for approval** (if required) - Wait for approval if your organization requires it - - * **Monitor and maintain** \- Keep the flow updated and respond to user feedback - - - - -## Viewer permissions - -Viewer permissions give people access to use your flow without the ability to modify it. This is the default permission level and is appropriate for most sharing scenarios. - -### What viewers can do - - * **Run the flow** \- Execute the flow with their own inputs - - * **View results** \- See outputs and generated content - - * **Access the flow** \- Find it in their library and use it anytime - - * **See flow details** \- View descriptions and help information - - - -