AWS quick documentation change
Summary
Updated user persona documentation to simplify terminology and restructure content, changing from 'Creator (Business User)', 'End-User (Business User)', 'Admin (Technical User)' to 'Creator', 'End user', 'Admin' with more concise descriptions and bullet points for admin capabilities.
Security assessment
The change adds explicit documentation about security and governance controls available to Admins, including restricting access to Quick Flows for specific users, requiring approval before sharing flows, and managing flow ownership. While these are security-related features, there's no evidence this change addresses a specific security vulnerability or incident - it appears to be a documentation improvement to clarify existing security controls.
Diff
diff --git a/quick/latest/userguide/user-personas.md b/quick/latest/userguide/user-personas.md index 4e6ed9cf6..ba3e9f487 100644 --- a//quick/latest/userguide/user-personas.md +++ b//quick/latest/userguide/user-personas.md @@ -5 +5 @@ -Creator (Business User)End-User (Business User)Admin (Technical User) +CreatorEnd userAdmin @@ -9 +9 @@ Creator (Business User)End-User (Business User)Admin (Technical User) -Amazon Quick Flows is designed to serve different types of users, each with distinct roles, responsibilities, and skill sets. Understanding these user personas helps you identify how you and your team members can best leverage Quick Flows within your organization. +Amazon Quick Flows serves three types of users: @@ -11 +11 @@ Amazon Quick Flows is designed to serve different types of users, each with dist -## Creator (Business User) +## Creator @@ -13 +13 @@ Amazon Quick Flows is designed to serve different types of users, each with dist -The flow creator is a business user who possesses a deep understanding of process nuances and combines business expertise with the process knowledge needed to translate repetitive tasks into streamlined workflows. +Creators are business users who build flows. They understand the repetitive tasks and processes in their domain and translate them into reusable workflows. @@ -15 +15 @@ The flow creator is a business user who possesses a deep understanding of proces -A critical aspect of the Creator role involves ensuring compliance with industry standards and regulatory requirements while validating business rules and process changes. This responsibility requires them to stay current with both regulatory developments and business process evolution within their organization. +## End user @@ -17 +17 @@ A critical aspect of the Creator role involves ensuring compliance with industry -## End-User (Business User) +End users run flows that creators have built. They interact with flows to complete their daily tasks and provide feedback on how well the automation works. @@ -19 +19 @@ A critical aspect of the Creator role involves ensuring compliance with industry -The End-User is a business user who performs repetitive business processes and benefits directly from the automation that Quick Flows provides. This persona represents the primary consumers of Flows created by Creators and managed by Admins. +## Admin @@ -21 +21 @@ The End-User is a business user who performs repetitive business processes and b -End-Users have experience in their specific business domain with some understanding of end-to-end processes, workflows, and business rules. While they may not create Flows themselves, their domain expertise is valuable for testing and validating automated processes to ensure they meet real-world business needs. +Admins configure and manage governance controls for Amazon Quick Flows within Amazon Quick. They can: @@ -23 +23 @@ End-Users have experience in their specific business domain with some understand -These users act as the primary contact for business teams, providing feedback on Flow performance and identifying areas where automation could be improved or expanded. Their hands-on experience with daily business processes makes them essential contributors to the continuous improvement of automated workflows. + * Enable or disable Quick Flows for the account @@ -25 +25 @@ These users act as the primary contact for business teams, providing feedback on -## Admin (Technical User) + * Restrict access to Quick Flows for specific users @@ -27 +27,5 @@ These users act as the primary contact for business teams, providing feedback on -The Admin is a technical user responsible for configuring and managing governance controls within the Quick. Admins manage which users have access to which capabilities within Quick Flows. + * Enable or disable Bedrock models for output refinement + + * Require approval before users can share flows + + * Unpublish shared flows and transfer ownership between users @@ -29 +32,0 @@ The Admin is a technical user responsible for configuring and managing governanc -Admins have experience configuring AWS services and possess stakeholder management skills for requirement gathering, providing updates, and managing expectations across organizational levels. @@ -31 +33,0 @@ Admins have experience configuring AWS services and possess stakeholder manageme -Key administrative capabilities for Quick Flows include the ability to enable or disable Quick Flows for the entire Quick account, controlling whether users can create and run automated workflows, or restrict access to Quick Flows for select users (through [Using Custom Permissions page](./managing-quick-flows-permissions-and-assets.html#using-custom-permissions-page)). Admins can also manage Bedrock model usage by enabling or disabling specific models for output refinement in Quick Flows, ensuring appropriate AI capabilities are available to users. @@ -33 +34,0 @@ Key administrative capabilities for Quick Flows include the ability to enable or -Additional governance controls allow Admins to enable or disable approval requirements before users can share Flows, maintaining organizational oversight of shared automation. Admins also have the authority to unpublish any shared flows and manage ownership transfer of flows between users. This is especially useful to prevent the problem of orphaned assets (here, flows) when users leave the organization. @@ -43 +44 @@ Getting started -Key concepts +Prerequisites