AWS chatbot documentation change
Summary
Updated policy tutorial to use 'Amazon Q Developer in chat channels' terminology consistently
Security assessment
Branding/naming standardization changes only. Policy content about Chime access denial remains unchanged and was pre-existing security documentation.
Diff
diff --git a/chatbot/latest/adminguide/org-policy-tutorial.md b/chatbot/latest/adminguide/org-policy-tutorial.md index 07d498355..8f31a35f1 100644 --- a//chatbot/latest/adminguide/org-policy-tutorial.md +++ b//chatbot/latest/adminguide/org-policy-tutorial.md @@ -9 +9 @@ AWS Chatbot is now Amazon Q Developer. [Learn more](./service-rename.html) -# Tutorial: Creating chat applications policies in Amazon Q Developer +# Tutorial: Creating chat applications policies in Amazon Q Developer in chat channels @@ -24 +24 @@ In this tutorial, you use the Amazon Q Developer in chat applications console to -Subsequently, all Amazon Q Developer configurations in your organization must adhere to these specifications. +Subsequently, all Amazon Q Developer in chat channels configurations in your organization must adhere to these specifications. @@ -81 +81 @@ In **Set Amazon Chime chat client access** , choose **Deny Chime access**. -You can find your workspace ID in the Amazon Q Developer console by choosing the configured client in the left sidebar and looking under **Workspace details**. +You can find your workspace ID in the Amazon Q Developer in chat channels console by choosing the configured client in the left sidebar and looking under **Workspace details**. @@ -102 +102 @@ If you already have an Amazon Q Developer in chat applications configuration, yo - * Create an Amazon Q Developer configuration for Microsoft Teams + * Create an Amazon Q Developer in chat channels configuration for Microsoft Teams @@ -104 +104 @@ If you already have an Amazon Q Developer in chat applications configuration, yo - * Create a Slack Amazon Q Developer configuration for a workspace you didn't specify in your policy + * Create a Slack Amazon Q Developer in chat channels configuration for a workspace you didn't specify in your policy @@ -106 +106 @@ If you already have an Amazon Q Developer in chat applications configuration, yo - * Create a Slack Amazon Q Developer configuration that uses a channel role + * Create a Slack Amazon Q Developer in chat channels configuration that uses a channel role