diff --git a/docs/docs.json b/docs/docs.json index d8a5dc4fb..31a50683b 100644 --- a/docs/docs.json +++ b/docs/docs.json @@ -34616,6 +34616,42 @@ "suggestEdit": true }, "redirects": [ + { + "source": "/enterprise/features/agent-control-plane/rules", + "destination": "/edge/en/enterprise/features/agent-control-plane/policies" + }, + { + "source": "/en/enterprise/features/agent-control-plane/rules", + "destination": "/edge/en/enterprise/features/agent-control-plane/policies" + }, + { + "source": "/edge/en/enterprise/features/agent-control-plane/rules", + "destination": "/edge/en/enterprise/features/agent-control-plane/policies" + }, + { + "source": "/pt-BR/enterprise/features/agent-control-plane/rules", + "destination": "/edge/pt-BR/enterprise/features/agent-control-plane/policies" + }, + { + "source": "/edge/pt-BR/enterprise/features/agent-control-plane/rules", + "destination": "/edge/pt-BR/enterprise/features/agent-control-plane/policies" + }, + { + "source": "/ko/enterprise/features/agent-control-plane/rules", + "destination": "/edge/ko/enterprise/features/agent-control-plane/policies" + }, + { + "source": "/edge/ko/enterprise/features/agent-control-plane/rules", + "destination": "/edge/ko/enterprise/features/agent-control-plane/policies" + }, + { + "source": "/ar/enterprise/features/agent-control-plane/rules", + "destination": "/edge/ar/enterprise/features/agent-control-plane/policies" + }, + { + "source": "/edge/ar/enterprise/features/agent-control-plane/rules", + "destination": "/edge/ar/enterprise/features/agent-control-plane/policies" + }, { "source": "/api-reference", "destination": "/v1.15.1/en/api-reference/introduction" @@ -34740,4 +34776,4 @@ "reddit": "https://www.reddit.com/r/crewAIInc/" } } -} +} \ No newline at end of file diff --git a/docs/edge/ar/enterprise/features/agent-control-plane/monitoring.mdx b/docs/edge/ar/enterprise/features/agent-control-plane/monitoring.mdx index db1b2c712..e053e408e 100644 --- a/docs/edge/ar/enterprise/features/agent-control-plane/monitoring.mdx +++ b/docs/edge/ar/enterprise/features/agent-control-plane/monitoring.mdx @@ -11,7 +11,7 @@ mode: "wide" - [نظرة عامة](/ar/enterprise/features/agent-control-plane/overview) - **المراقبة** *(أنت هنا)* - - [القواعد](/ar/enterprise/features/agent-control-plane/rules) + - [السياسات](/edge/ar/enterprise/features/agent-control-plane/policies) ## نظرة عامة @@ -58,7 +58,7 @@ mode: "wide" | **Last execution** | الوقت المنقضي منذ آخر تنفيذ. | | **Health Status Breakdown** | شريط مكدّس بنسب `Critical` / `Warning` / `Healthy` لعمليات التنفيذ في النافذة. | | **Executions with Errors** | إجمالي عمليات التنفيذ الفاشلة في النافذة. | -| **PII detection applied** | `Yes` إذا كان هناك تكوين PII لكل deployment أو [قاعدة PII](/ar/enterprise/features/agent-control-plane/rules) مطابِقة نشطة. | +| **PII detection applied** | `Yes` إذا كان هناك تكوين PII لكل deployment أو [سياسة PII](/edge/ar/enterprise/features/agent-control-plane/policies) مطابِقة نشطة. | | **Executions** | إجمالي عمليات التنفيذ في النافذة. | | **Last updated** | متى أُعيد نشر الـ deployment آخر مرة. | | **Crew Version** | إصدار `crewai` الذي يُبلِّغ عنه الـ deployment. يشير أيقونة المعلومات بجانب الإصدارات الأقل من `1.13` إلى صفوف لا يمكنها المساهمة بالمقاييس. | @@ -96,8 +96,8 @@ mode: "wide" ما هو ACP، المتطلبات، مستويات الخطط، و RBAC. - - طبّق قواعد PII Redaction على مستوى المؤسسة عبر العديد من الأتمتات. + + طبّق سياسات PII Redaction على مستوى المؤسسة عبر العديد من الأتمتات. تعمّق في تنفيذ واحد لرؤية تفكير الوكيل واستدعاءات الأدوات واستخدام الرموز. diff --git a/docs/edge/ar/enterprise/features/agent-control-plane/overview.mdx b/docs/edge/ar/enterprise/features/agent-control-plane/overview.mdx index 6e9ff1925..54e1bf87e 100644 --- a/docs/edge/ar/enterprise/features/agent-control-plane/overview.mdx +++ b/docs/edge/ar/enterprise/features/agent-control-plane/overview.mdx @@ -10,17 +10,17 @@ icon: "book-open" - **نظرة عامة** *(أنت هنا)* - [المراقبة](/ar/enterprise/features/agent-control-plane/monitoring) - - [القواعد](/ar/enterprise/features/agent-control-plane/rules) + - [السياسات](/edge/ar/enterprise/features/agent-control-plane/policies) ## نظرة عامة -**Agent Control Plane** (ACP) هو مركز العمليات لكل ما يعمل لديك على CrewAI AMP. إنها شاشة واحدة — مقسّمة إلى تبويبَي **Automations** و **Rules** — تمنح فريقك القدرة على: +**Agent Control Plane** (ACP) هو مركز العمليات لكل ما يعمل لديك على CrewAI AMP. إنها شاشة واحدة — مقسّمة إلى تبويبَي **Automations** و **Policies** — تمنح فريقك القدرة على: - مراقبة **حالة (الصحة)** كل أتمتة حيّة (crew أو flow) بتفصيل `Critical` / `Warning` / `Healthy` وعدد عمليات التنفيذ. - تتبع **استهلاك LLM** — الرموز (tokens) والتكلفة — لكل أتمتة ولكل مزود ولكل نموذج، مع الفرق مقابل الفترة السابقة. - التعمّق في أي أتمتة منفردة أو مزود نماذج لرؤية المخططات الزمنية وتفصيل البيانات لكل مزود. -- تطبيق **قواعد (Rules)** على مستوى المؤسسة (اليوم: PII Redaction) عبر العديد من الأتمتات دفعة واحدة بدلاً من تعديل كل deployment على حدة. +- تطبيق **سياسات (Policies)** على مستوى المؤسسة (اليوم: PII Redaction) عبر العديد من الأتمتات دفعة واحدة بدلاً من تعديل كل deployment على حدة. ![نظرة عامة على Agent Control Plane](/images/enterprise/acp-overview-automations-sankey.png) @@ -33,7 +33,7 @@ icon: "book-open" يجيب التبويبان عن سؤالَين مختلفَين: - **Automations** — *"كيف يتصرف أسطولي الآن، وكم يكلّفني؟"* راجع [المراقبة](/ar/enterprise/features/agent-control-plane/monitoring). -- **Rules** — *"كيف أفرض سياسة (مثل PII redaction) عبر العديد من عمليات النشر دون إعادة نشر كل واحدة؟"* راجع [القواعد](/ar/enterprise/features/agent-control-plane/rules). +- **Policies** — *"كيف أفرض سياسة (مثل PII redaction) عبر العديد من عمليات النشر دون إعادة نشر كل واحدة؟"* راجع [السياسات](/edge/ar/enterprise/features/agent-control-plane/policies). ## المتطلبات @@ -42,11 +42,11 @@ icon: "book-open" - يُشترط **خطة Enterprise أو Ultra** لإنشاء أو تعديل [القواعد](/ar/enterprise/features/agent-control-plane/rules). يمكن للمؤسسات على الخطط الأدنى فتح تبويب Rules وعرض القواعد الموجودة، ولكن يُعرض المحرر للقراءة فقط مع شارة قفل "Enterprise" والتنبيه *"PII Redaction rules require an Enterprise plan."*. المراقبة (تبويب Automations) متاحة في جميع الخطط حيث يكون هذا الميزة مفعّلة. + يُشترط **خطة Enterprise أو Ultra** لإنشاء أو تعديل [السياسات](/edge/ar/enterprise/features/agent-control-plane/policies). يمكن للمؤسسات على الخطط الأدنى فتح تبويب Policies وعرض السياسات الموجودة، ولكن يُعرض المحرر للقراءة فقط مع شارة قفل "Enterprise" والتنبيه *"PII Redaction policies require an Enterprise plan."*. المراقبة (تبويب Automations) متاحة في جميع الخطط حيث يكون هذا الميزة مفعّلة. - يجب أن تكون ميزة **Agent Control Plane** مفعّلة لمؤسستك. إن لم ترها في الشريط الجانبي، اطلب من مالك الحساب تفعيلها. -- داخل ACP، يحكم [RBAC](/ar/enterprise/features/rbac) الوصول: `read` للعرض في لوحة المعلومات والقواعد، و`manage` لإنشاء وتعديل وتشغيل/إيقاف وحذف القواعد. +- داخل ACP، يحكم [RBAC](/ar/enterprise/features/rbac) الوصول: `read` للعرض في لوحة المعلومات والسياسات، و`manage` لإنشاء وتعديل وتشغيل/إيقاف وحذف السياسات. - يمكن ضبط نطاق جميع المخططات والجداول إلى **آخر 24 ساعة** أو **الأسبوع الماضي** أو **آخر 30 يوماً** عبر مُحدّد الوقت في أعلى اليمين. تقارن قيم الفرق (`↑ 8 vs yesterday`, `↓ $20.57 vs yesterday` وغيرها) النافذة المختارة بالنافذة السابقة بنفس الطول. ## ما يمكنك فعله هنا @@ -55,7 +55,7 @@ icon: "book-open" راقب صحة الأسطول وإنفاق LLM عبر بطاقات المقاييس و sankey التفاعلي وجداول لكل أتمتة ولوحات جانبية للتعمق في أي أتمتة أو مزود. - + طبّق سياسات PII Redaction على مستوى المؤسسة بنطاق محدد بالأدوات والوسوم. تسري التغييرات في التنفيذ التالي — دون الحاجة لإعادة نشر. @@ -67,10 +67,10 @@ icon: "book-open" تعمّق في تنفيذ واحد لرؤية تفكير الوكيل واستدعاءات الأدوات واستخدام الرموز. - أدِر من يمكنه قراءة Agent Control Plane ومن يمكنه تعديل القواعد. + أدِر من يمكنه قراءة Agent Control Plane ومن يمكنه تعديل السياسات. - كتالوج الكيانات وضبط PII لكل deployment التي تستند إليها القواعد. + كتالوج الكيانات وضبط PII لكل deployment التي تستند إليها السياسات. انشر crew على إصدار crewAI يدعم Agent Control Plane. @@ -78,5 +78,5 @@ icon: "book-open" - تواصل مع فريق الدعم للمساعدة في تفسير المقاييس أو تصميم القواعد. + تواصل مع فريق الدعم للمساعدة في تفسير المقاييس أو تصميم السياسات. diff --git a/docs/edge/ar/enterprise/features/agent-control-plane/rules.mdx b/docs/edge/ar/enterprise/features/agent-control-plane/policies.mdx similarity index 59% rename from docs/edge/ar/enterprise/features/agent-control-plane/rules.mdx rename to docs/edge/ar/enterprise/features/agent-control-plane/policies.mdx index 144ec1003..71388b117 100644 --- a/docs/edge/ar/enterprise/features/agent-control-plane/rules.mdx +++ b/docs/edge/ar/enterprise/features/agent-control-plane/policies.mdx @@ -1,7 +1,7 @@ --- -title: "إعداد القواعد" +title: "إعداد السياسات" description: "طبّق سياسات على مستوى المؤسسة عبر العديد من الأتمتات من مكان واحد." -sidebarTitle: "القواعد" +sidebarTitle: "السياسات" icon: "shield-check" mode: "wide" --- @@ -11,50 +11,50 @@ mode: "wide" - [نظرة عامة](/ar/enterprise/features/agent-control-plane/overview) - [المراقبة](/ar/enterprise/features/agent-control-plane/monitoring) - - **القواعد** *(أنت هنا)* + - **السياسات** *(أنت هنا)* ## نظرة عامة -تتيح لك القواعد تطبيق سياسات — اليوم: **PII Redaction** — عبر العديد من الأتمتات دفعة واحدة، بدلاً من ضبط كل deployment على حدة. افتح تبويب **Rules** في [Agent Control Plane](/ar/enterprise/features/agent-control-plane/overview) لإدارتها. +تتيح لك السياسات تطبيق سياسات — اليوم: **PII Redaction** — عبر العديد من الأتمتات دفعة واحدة، بدلاً من ضبط كل deployment على حدة. افتح تبويب **Policies** في [Agent Control Plane](/ar/enterprise/features/agent-control-plane/overview) لإدارتها. - ![قائمة القواعد](/images/enterprise/acp-rules-list.png) + ![قائمة السياسات](/images/enterprise/acp-policies-list.png) -تعرض كل بطاقة قاعدة الاسم والوصف و**النطاق (scope)** الذي تنطبق عليه القاعدة (الأدوات والوسوم المختارة) وعدد **الأتمتات المُفعَّلة** — عمليات النشر التي تطابق النطاق حالياً. يقوم المُفتاح على اليمين بتشغيل القاعدة أو إيقافها دون حذفها. +تعرض كل بطاقة سياسة الاسم والوصف و**النطاق (scope)** الذي تنطبق عليه السياسة (الأدوات والوسوم المختارة) وعدد **الأتمتات المُفعَّلة** — عمليات النشر التي تطابق النطاق حالياً. يقوم المُفتاح على اليمين بتشغيل السياسة أو إيقافها دون حذفها. ## المتطلبات - يُشترط **خطة Enterprise أو Ultra** لإنشاء أو تعديل قواعد PII Redaction. يمكن للمؤسسات على الخطط الأدنى فتح تبويب Rules وعرض القواعد الموجودة، ولكن يُعرض المحرر للقراءة فقط مع شارة قفل "Enterprise" والتنبيه *"PII Redaction rules require an Enterprise plan."* — تواصل مع مالك حسابك أو المبيعات للترقية. + يُشترط **خطة Enterprise أو Ultra** لإنشاء أو تعديل سياسات PII Redaction. يمكن للمؤسسات على الخطط الأدنى فتح تبويب Policies وعرض السياسات الموجودة، ولكن يُعرض المحرر للقراءة فقط مع شارة قفل "Enterprise" والتنبيه *"PII Redaction policies require an Enterprise plan."* — تواصل مع مالك حسابك أو المبيعات للترقية. - يجب أن تكون ميزة **Agent Control Plane** مفعّلة لمؤسستك. راجع [نظرة عامة — المتطلبات](/ar/enterprise/features/agent-control-plane/overview#المتطلبات). -- تحتاج إلى صلاحية `manage` ضمن [RBAC](/ar/enterprise/features/rbac) على Agent Control Plane لإنشاء وتعديل وتشغيل/إيقاف وحذف القواعد. صلاحية `read` كافية لعرضها. -- تُسجَّل جميع تغييرات القواعد بإصدارات للتدقيق. +- تحتاج إلى صلاحية `manage` ضمن [RBAC](/ar/enterprise/features/rbac) على Agent Control Plane لإنشاء وتعديل وتشغيل/إيقاف وحذف السياسات. صلاحية `read` كافية لعرضها. +- تُسجَّل جميع تغييرات السياسات بإصدارات للتدقيق. -## أنواع القواعد المتاحة +## أنواع السياسات المتاحة | النوع | ما تفعله | |------|---------------| | **PII Redaction** | تطبّق PII redaction على عمليات التنفيذ لكل أتمتة مطابِقة، باستخدام نفس كتالوج الكيانات و recognizers المخصصة الموثَّقة في [PII Redaction للـ Traces](/ar/enterprise/features/pii-trace-redactions). | -سيتم إضافة أنواع قواعد أخرى مع الوقت. +سيتم إضافة أنواع سياسات أخرى مع الوقت. -## إنشاء قاعدة +## إنشاء سياسة - لوحة تعديل قاعدة جانبية بالشروط ونوع قناع PII + لوحة تعديل سياسة جانبية بالشروط ونوع قناع PII - انقر على **+ Create new** في أعلى يمين تبويب Rules، أو على **View Details** في بطاقة قاعدة موجودة. + انقر على **+ Create new** في أعلى يمين تبويب Policies، أو على **View Details** في بطاقة سياسة موجودة. - - أعطِ القاعدة اسماً واضحاً (مثل *Mask PII (CC)*) ووصفاً يشرح متى تنطبق. يظهر كلاهما على بطاقة القاعدة وفي مودال Engaged Automations. + + أعطِ السياسة اسماً واضحاً (مثل *Mask PII (CC)*) ووصفاً يشرح متى تنطبق. يظهر كلاهما على بطاقة السياسة وفي مودال Engaged Automations. @@ -62,12 +62,12 @@ mode: "wide" - تحدد الشروط الأتمتات التي تنخرط معها القاعدة. كلاهما اختياري ويستخدم دلالات **مساواة المجموعات (set-equality)**: + تحدد الشروط الأتمتات التي تنخرط معها السياسة. كلاهما اختياري ويستخدم دلالات **مساواة المجموعات (set-equality)**: - **Tools** — تنخرط فقط الأتمتات التي تتطابق مجموعة أدواتها **تطابقاً تامّاً** مع الأدوات المختارة. اختر من تطبيقات Studio و MCPs والأدوات مفتوحة المصدر وأدوات سجل Tool Repository. - **Automations** — تنخرط فقط الأتمتات التي تتطابق مجموعة وسومها **تطابقاً تامّاً** مع الوسوم المختارة. - ترك مُحدِّد فارغ يعني "بدون تصفية على هذا البعد". ترك كليهما فارغَين يعني أن القاعدة تنطبق على **كل** أتمتة في المؤسسة. + ترك مُحدِّد فارغ يعني "بدون تصفية على هذا البعد". ترك كليهما فارغَين يعني أن السياسة تنطبق على **كل** أتمتة في المؤسسة. @@ -75,30 +75,30 @@ mode: "wide" - تنطبق القاعدة على عمليات التنفيذ **المستقبلية** لكل أتمتة مُفعَّلة بمجرد الحفظ. لا حاجة لإعادة النشر. + تنطبق السياسة على عمليات التنفيذ **المستقبلية** لكل أتمتة مُفعَّلة بمجرد الحفظ. لا حاجة لإعادة النشر. ## الأتمتات المُفعَّلة -انقر على **Engaged N automations** في أي بطاقة قاعدة لرؤية أي عمليات النشر تطابقها القاعدة حالياً بالضبط، إلى جانب آخر تنفيذ لكل منها. +انقر على **Engaged N automations** في أي بطاقة سياسة لرؤية أي عمليات النشر تطابقها السياسة حالياً بالضبط، إلى جانب آخر تنفيذ لكل منها. - ![مودال الأتمتات المُفعَّلة](/images/enterprise/acp-rules-engaged-modal.png) + ![مودال الأتمتات المُفعَّلة](/images/enterprise/acp-policies-engaged-modal.png) -هذه هي أسرع طريقة للتحقق من نطاق قاعدة قبل تمكينها — على سبيل المثال، للتأكد من أن قاعدة محدَّدة بنطاق وسم `production` لا تطابق عن طريق الخطأ deployment تجريبي. +هذه هي أسرع طريقة للتحقق من نطاق سياسة قبل تمكينها — على سبيل المثال، للتأكد من أن سياسة محدَّدة بنطاق وسم `production` لا تطابق عن طريق الخطأ deployment تجريبي. -## قواعد على مستوى المؤسسة مقابل إعدادات لكل deployment +## سياسات على مستوى المؤسسة مقابل إعدادات لكل deployment يمكن ضبط PII Redaction في مكانين: - **لكل deployment** — ضمن **Settings → PII Protection** على كل deployment على حدة ([الدليل](/ar/enterprise/features/pii-trace-redactions)) -- **على مستوى المؤسسة** — كقاعدة في هذه الصفحة +- **على مستوى المؤسسة** — كسياسة في هذه الصفحة -عندما يتطابق نطاق قاعدة مُفعَّلة على مستوى المؤسسة مع deployment، يُجاوز تكوين الكيانات الخاص بالقاعدة **إعدادات PII المملوكة من قبل الـ deployment** لعمليات تنفيذ ذلك الـ deployment — تصبح القاعدة المصدر الوحيد للحقيقة طالما هي مرتبطة. عطّل القاعدة أو فُكَّ ارتباطها (أو غيِّر نطاقها بحيث لا تتطابق بعد الآن) ويعود الـ deployment إلى إعدادات PII Protection الخاصة به. +عندما يتطابق نطاق سياسة مُفعَّلة على مستوى المؤسسة مع deployment، يُجاوز تكوين الكيانات الخاص بالسياسة **إعدادات PII المملوكة من قبل الـ deployment** لعمليات تنفيذ ذلك الـ deployment — تصبح السياسة المصدر الوحيد للحقيقة طالما هي مرتبطة. عطّل السياسة أو فُكَّ ارتباطها (أو غيِّر نطاقها بحيث لا تتطابق بعد الآن) ويعود الـ deployment إلى إعدادات PII Protection الخاصة به. -فضّل القواعد على مستوى المؤسسة عندما تريد فرض سياسة متسقة عبر العديد من عمليات النشر؛ احتفظ بالضبط لكل deployment للاستثناءات الفردية. +فضّل السياسات على مستوى المؤسسة عندما تريد فرض سياسة متسقة عبر العديد من عمليات النشر؛ احتفظ بالضبط لكل deployment للاستثناءات الفردية. ## ذو صلة @@ -113,10 +113,10 @@ mode: "wide" كتالوج الكيانات، recognizers المخصصة، والضبط لكل deployment. - أدِر من يمكنه إنشاء أو تعديل القواعد. + أدِر من يمكنه إنشاء أو تعديل السياسات. - تواصل مع فريق الدعم للمساعدة في تصميم قواعد لمؤسستك. + تواصل مع فريق الدعم للمساعدة في تصميم سياسات لمؤسستك. diff --git a/docs/edge/en/enterprise/features/agent-control-plane/monitoring.mdx b/docs/edge/en/enterprise/features/agent-control-plane/monitoring.mdx index ef94d1895..1165f2855 100644 --- a/docs/edge/en/enterprise/features/agent-control-plane/monitoring.mdx +++ b/docs/edge/en/enterprise/features/agent-control-plane/monitoring.mdx @@ -11,7 +11,7 @@ mode: "wide" - [Overview](/en/enterprise/features/agent-control-plane/overview) - **Monitoring** *(you are here)* - - [Rules](/en/enterprise/features/agent-control-plane/rules) + - [Policies](/edge/en/enterprise/features/agent-control-plane/policies) ## Overview @@ -58,7 +58,7 @@ The **Automations** sub-tab is the per-deployment breakdown of fleet health. Eac | **Last execution** | Time since the most recent run. | | **Health Status Breakdown** | Stacked bar of `Critical` / `Warning` / `Healthy` percentages for executions in the window. | | **Executions with Errors** | Total failed executions in the window. | -| **PII detection applied** | `Yes` if a per-deployment PII config or a matching [PII rule](/en/enterprise/features/agent-control-plane/rules) is active. | +| **PII detection applied** | `Yes` if a per-deployment PII config or a matching [PII policy](/edge/en/enterprise/features/agent-control-plane/policies) is active. | | **Executions** | Total executions in the window. | | **Last updated** | When the deployment was last re-deployed. | | **Crew Version** | The `crewai` version reported by the deployment. An info icon next to versions below `1.13` flags rows that can't contribute metrics. | @@ -96,8 +96,8 @@ Filter by **LLM provider** and sort by `Cost`, `Executions`, or `Last run`. What ACP is, requirements, plan tiers, and RBAC. - - Apply organization-wide PII Redaction rules across many automations. + + Apply organization-wide PII Redaction policies across many automations. Drill into a single execution to see agent reasoning, tool calls, and token usage. diff --git a/docs/edge/en/enterprise/features/agent-control-plane/overview.mdx b/docs/edge/en/enterprise/features/agent-control-plane/overview.mdx index d4a03e02f..687c8f597 100644 --- a/docs/edge/en/enterprise/features/agent-control-plane/overview.mdx +++ b/docs/edge/en/enterprise/features/agent-control-plane/overview.mdx @@ -10,17 +10,17 @@ icon: "book-open" - **Overview** *(you are here)* - [Monitoring](/en/enterprise/features/agent-control-plane/monitoring) - - [Rules](/en/enterprise/features/agent-control-plane/rules) + - [Policies](/edge/en/enterprise/features/agent-control-plane/policies) ## Overview -The **Agent Control Plane** (ACP) is the operations hub for everything you have running on CrewAI AMP. It is a single screen — split into **Automations** and **Rules** tabs — that lets your team: +The **Agent Control Plane** (ACP) is the operations hub for everything you have running on CrewAI AMP. It is a single screen — split into **Automations** and **Policies** tabs — that lets your team: - Monitor the **health** of every live automation (crew or flow), with `Critical` / `Warning` / `Healthy` breakdowns and execution counts. - Track **LLM consumption** — tokens and cost — per automation, per provider, and per model, with a delta vs the previous period. - Drill into any single automation or model provider for time-series charts and per-provider breakdowns. -- Apply organization-wide **Rules** (today: PII Redaction and Cost Limit) across many automations at once instead of editing each deployment individually. +- Apply organization-wide **Policies** (today: PII Redaction and Cost Limit) across many automations at once instead of editing each deployment individually. ![Agent Control Plane overview](/images/enterprise/acp-overview-automations-sankey.png) @@ -33,7 +33,7 @@ The **Agent Control Plane** (ACP) is the operations hub for everything you have The two tabs answer two different questions: - **Automations** — *"How is my fleet behaving right now, and what is it costing me?"* See [Monitoring](/en/enterprise/features/agent-control-plane/monitoring). -- **Rules** — *"How do I enforce a policy (e.g. PII redaction or a spend budget) across many deployments without re-deploying each one?"* See [Rules](/en/enterprise/features/agent-control-plane/rules). +- **Policies** — *"How do I enforce a policy (e.g. PII redaction or a spend budget) across many deployments without re-deploying each one?"* See [Policies](/edge/en/enterprise/features/agent-control-plane/policies). ## Requirements @@ -42,11 +42,11 @@ The two tabs answer two different questions: - **Enterprise Plan or Ultra Plan** is required to create or edit **PII Redaction** [Rules](/en/enterprise/features/agent-control-plane/rules). Lower-tier organizations can open the Rules tab and view existing rules, but the PII editor renders read-only with an "Enterprise" lock pill and the alert *"PII Redaction rules require an Enterprise plan."* **Cost Limit** rules and Monitoring (the Automations tab) are available on all plans where the feature is enabled. + **Enterprise Plan or Ultra Plan** is required to create or edit **PII Redaction** [Policies](/edge/en/enterprise/features/agent-control-plane/policies). Lower-tier organizations can open the Policies tab and view existing policies, but the PII editor renders read-only with an "Enterprise" lock pill and the alert *"PII Redaction policies require an Enterprise plan."* **Cost Limit** policies and Monitoring (the Automations tab) are available on all plans where the feature is enabled. - The **Agent Control Plane** feature must be enabled for your organization. If you don't see it in the sidebar, ask your account owner to request enablement. -- Inside ACP, [RBAC](/en/enterprise/features/rbac) governs access: `read` to view the dashboard and rules, `manage` to create, edit, toggle, or delete rules. +- Inside ACP, [RBAC](/en/enterprise/features/rbac) governs access: `read` to view the dashboard and policies, `manage` to create, edit, toggle, or delete policies. - All charts and tables can be scoped to the **Last 24 hours**, **Last Week**, or **Last 30 days** using the time selector at the top right. Deltas (`↑ 8 vs yesterday`, `↓ $20.57 vs yesterday`, etc.) compare the selected window against the previous one of the same length. ## What you can do here @@ -55,7 +55,7 @@ The two tabs answer two different questions: Watch fleet health and LLM spend with metric cards, an interactive sankey, per-automation tables, and drill-down side panels for any automation or provider. - + Apply organization-wide PII Redaction and Cost Limit policies scoped by tools and tags. Changes take effect on the next execution — no re-deploy required. @@ -67,10 +67,10 @@ The two tabs answer two different questions: Drill into a single execution to see agent reasoning, tool calls, and token usage. - Manage who can read the Agent Control Plane and who can edit rules. + Manage who can read the Agent Control Plane and who can edit policies. - Entity catalog and per-deployment PII configuration referenced by Rules. + Entity catalog and per-deployment PII configuration referenced by Policies. Deploy a crew on a crewAI version that supports the Agent Control Plane. @@ -78,5 +78,5 @@ The two tabs answer two different questions: - Contact our support team for help interpreting metrics or designing rules. + Contact our support team for help interpreting metrics or designing policies. diff --git a/docs/edge/en/enterprise/features/agent-control-plane/rules.mdx b/docs/edge/en/enterprise/features/agent-control-plane/policies.mdx similarity index 54% rename from docs/edge/en/enterprise/features/agent-control-plane/rules.mdx rename to docs/edge/en/enterprise/features/agent-control-plane/policies.mdx index fd7108e3f..b74a92428 100644 --- a/docs/edge/en/enterprise/features/agent-control-plane/rules.mdx +++ b/docs/edge/en/enterprise/features/agent-control-plane/policies.mdx @@ -1,7 +1,7 @@ --- -title: "Set up the Rules" +title: "Set up the Policies" description: "Apply organization-wide policies across many automations from a single place." -sidebarTitle: "Rules" +sidebarTitle: "Policies" icon: "shield-check" mode: "wide" --- @@ -11,39 +11,39 @@ mode: "wide" - [Overview](/en/enterprise/features/agent-control-plane/overview) - [Monitoring](/en/enterprise/features/agent-control-plane/monitoring) - - **Rules** *(you are here)* + - **Policies** *(you are here)* ## Overview -Rules let you apply policies — today **PII Redaction** and **Cost Limit** — across many automations at once, instead of configuring each deployment individually. Open the **Rules** tab in the [Agent Control Plane](/en/enterprise/features/agent-control-plane/overview) to manage them. +Policies let you enforce organization-wide controls — today **PII Redaction** and **Cost Limit** — across many automations at once, instead of configuring each deployment individually. Open the **Policies** tab in the [Agent Control Plane](/en/enterprise/features/agent-control-plane/overview) to manage them. - ![Rules list](/images/enterprise/acp-rules-list.png) + ![Policies list](/images/enterprise/acp-policies-list.png) -Each rule card shows the name, description, the **scope** the rule applies to (selected tools and tags), and a count of **engaged automations** — deployments that currently match the scope. The toggle on the right enables or disables the rule without deleting it. +Each policy card shows the name, description, the **scope** the policy applies to (selected tools and tags), and a count of **engaged automations** — deployments that currently match the scope. The toggle on the right enables or disables the policy without deleting it. ## Requirements - **Enterprise Plan or Ultra Plan** is required to create or edit **PII Redaction** rules. Lower-tier organizations can still open the Rules tab and view existing rules, but the PII editor renders read-only with an "Enterprise" lock pill and the alert *"PII Redaction rules require an Enterprise plan."* — contact your account owner or sales to upgrade. **Cost Limit** rules are **not** plan-gated and can be created on any plan where the Agent Control Plane is enabled. + **Enterprise Plan or Ultra Plan** is required to create or edit **PII Redaction** policies. Lower-tier organizations can still open the Policies tab and view existing policies, but the PII editor renders read-only with an "Enterprise" lock pill and the alert *"PII Redaction policies require an Enterprise plan."* — contact your account owner or sales to upgrade. **Cost Limit** policies are **not** plan-gated and can be created on any plan where the Agent Control Plane is enabled. - The **Agent Control Plane** feature must be enabled for your organization. See [Overview — Requirements](/en/enterprise/features/agent-control-plane/overview#requirements). -- The `manage` [RBAC permission](/en/enterprise/features/rbac) on Agent Control Plane is required to create, edit, toggle, or delete rules. The `read` permission is enough to view them. -- All rule changes are versioned for auditing. +- The `manage` [RBAC permission](/en/enterprise/features/rbac) on Agent Control Plane is required to create, edit, toggle, or delete policies. The `read` permission is enough to view them. +- All policy changes are versioned for auditing. -## Rule types +## Policy types -Every rule is one of the types below. Open the tab for the policy you want to enforce. +Every policy is one of the types below. Open the tab for the policy you want to enforce. Applies PII redaction to executions of every matching automation, using the same entity catalog and custom recognizers documented in [PII Redaction for Traces](/en/enterprise/features/pii-trace-redactions). -Creating or editing PII Redaction rules requires an **Enterprise** or **Ultra** plan. On lower tiers the PII editor renders read-only with an "Enterprise" lock pill. +Creating or editing PII Redaction policies requires an **Enterprise** or **Ultra** plan. On lower tiers the PII editor renders read-only with an "Enterprise" lock pill. **Configuration** — in the **PII Mask Type** table, check each entity type you want covered and choose how to handle it: @@ -58,7 +58,7 @@ See [PII Redaction for Traces](/en/enterprise/features/pii-trace-redactions) for Emails the recipients you choose when a matching automation's LLM spend exceeds a budget threshold in the selected period. Available on **all plans** where the Agent Control Plane is enabled — it is not Enterprise-gated. -Cost Limit rules are **notify-only**. They never pause, throttle, or stop a run — they only send an email so a human can decide what to do. Adjust the budget or remove the rule if you no longer want the alert. +Cost Limit policies are **notify-only**. They never pause, throttle, or stop a run — they only send an email so a human can decide what to do. Adjust the budget or remove the policy if you no longer want the alert. **Configuration** @@ -74,7 +74,7 @@ Cost Limit rules are **notify-only**. They never pause, throttle, or stop a run **How spend is measured and matched** - The threshold is evaluated **per automation**, not summed across the whole scope. Each engaged automation has its own running total for the period. -- A rule can match many automations via its conditions (tools/tags), and a single automation can be covered by **multiple** Cost Limit rules at once. Each rule tracks its own budget and alert state independently — they don't merge. +- A policy can match many automations via its conditions (tools/tags), and a single automation can be covered by **multiple** Cost Limit policies at once. Each policy tracks its own budget and alert state independently — they don't merge. - A background check compares each engaged automation's period-to-date spend against the threshold and sends the email when it's exceeded. Because the check runs periodically, expect a short delay between crossing the threshold and the email arriving. **The alert email** @@ -83,76 +83,76 @@ When an automation goes over budget, recipients get an email summarizing the ove -More rule types will be added over time. +More policy types will be added over time. -## Creating a rule +## Creating a policy - New Rule side panel configured for PII Redaction with the PII mask type table + New Policy side panel configured for PII Redaction with the PII mask type table - New Rule side panel configured for Cost Limit with budget period, threshold, and recipient emails + New Policy side panel configured for Cost Limit with budget period, threshold, and recipient emails - Click **+ Create new** at the top-right of the Rules tab, or **View Details** on an existing rule card. + Click **+ Create new** at the top-right of the Policies tab, or **View Details** on an existing policy card. - - Give the rule a clear name (e.g. *Mask PII (CC)* or *Monthly $100 budget*) and a description explaining when it applies. Both show up on the rule card and in the Engaged Automations modal. + + Give the policy a clear name (e.g. *Mask PII (CC)* or *Monthly $100 budget*) and a description explaining when it applies. Both show up on the policy card and in the Engaged Automations modal. - Choose **PII Redaction** or **Cost Limit**. The type determines which configuration section appears below the conditions. The type is fixed once the rule is created — to switch, create a new rule. + Choose **PII Redaction** or **Cost Limit**. The type determines which configuration section appears below the conditions. The type is fixed once the policy is created — to switch, create a new policy. - Conditions decide which automations the rule engages with. Both are optional and use **set-equality** semantics: + Conditions decide which automations the policy engages with. Both are optional and use **set-equality** semantics: - **Tools** — only automations whose tool set **exactly matches** the selected tools will engage. Picks from Studio apps, MCPs, OSS tools, and Tool Repository registry tools. - **Automations** — only automations whose tag set **exactly matches** the selected tags will engage. - Leaving a picker empty means "no filter on this dimension". Leaving both empty means the rule applies to **every** automation in the organization. + Leaving a picker empty means "no filter on this dimension". Leaving both empty means the policy applies to **every** automation in the organization. - The editor shows the configuration for the type you picked — the **PII Mask Type** table for PII Redaction, or the budget fields for Cost Limit. See [Rule types](#rule-types) for what each field does. + The editor shows the configuration for the type you picked — the **PII Mask Type** table for PII Redaction, or the budget fields for Cost Limit. See [Policy types](#policy-types) for what each field does. - The rule applies to **future** executions of every engaged automation as soon as you save. No re-deploy is needed. + The policy applies to **future** executions of every engaged automation as soon as you save. No re-deploy is needed. ## Engaged automations -Click **Engaged N automations** on any rule card to see exactly which deployments the rule is currently matching, along with each one's last execution. +Click **Engaged N automations** on any policy card to see exactly which deployments the policy is currently matching, along with each one's last execution. - ![Engaged automations modal](/images/enterprise/acp-rules-engaged-modal.png) + ![Engaged automations modal](/images/enterprise/acp-policies-engaged-modal.png) -This is the fastest way to sanity-check a rule's scope before enabling it — for example, to confirm that a rule scoped to the `production` tag isn't accidentally matching a staging deployment. +This is the fastest way to sanity-check a policy's scope before enabling it — for example, to confirm that a policy scoped to the `production` tag isn't accidentally matching a staging deployment. -## Org-wide rules vs per-deployment settings +## Org-wide policies vs per-deployment settings -Both PII Redaction and Cost Limit can be configured in two places: org-wide as a Rule on this page, or per-deployment under that deployment's **Settings**. When an enabled org-wide rule's scope matches a deployment, the rule takes precedence over the deployment-owned setting while it's attached. +Both PII Redaction and Cost Limit can be configured in two places: org-wide as a Policy on this page, or per-deployment under that deployment's **Settings**. When an enabled org-wide policy's scope matches a deployment, the policy takes precedence over the deployment-owned setting while it's attached. -| Policy | Per-deployment setting | What an attached org-wide rule does | +| Policy | Per-deployment setting | What an attached org-wide policy does | |--------|------------------------|-------------------------------------| -| **PII Redaction** | **Settings → PII Protection** ([guide](/en/enterprise/features/pii-trace-redactions)) | The rule's entity configuration **overrides** the deployment's PII settings for that deployment's executions. | -| **Cost Limit** | **Settings → Cost Alerts** | The deployment's manual cost alert is **paused** and the attached cost rule(s) fire instead. The per-deployment form stays editable as a fallback. | +| **PII Redaction** | **Settings → PII Protection** ([guide](/en/enterprise/features/pii-trace-redactions)) | The policy's entity configuration **overrides** the deployment's PII settings for that deployment's executions. | +| **Cost Limit** | **Settings → Cost Alerts** | The deployment's manual cost alert is **paused** and the attached cost policy(s) fire instead. The per-deployment form stays editable as a fallback. | -Disable or detach the rule (or change its scope so it no longer matches) and the deployment falls back to its own per-deployment settings. +Disable or detach the policy (or change its scope so it no longer matches) and the deployment falls back to its own per-deployment settings. -Prefer org-wide rules when you want to enforce a consistent policy across many deployments; reserve per-deployment configuration for one-off exceptions. +Prefer org-wide policies when you want to enforce a consistent policy across many deployments; reserve per-deployment configuration for one-off exceptions. ## Related @@ -167,10 +167,10 @@ Prefer org-wide rules when you want to enforce a consistent policy across many d Entity catalog, custom recognizers, and per-deployment configuration. - Manage who can create or edit rules. + Manage who can create or edit policies. - Contact our support team for help designing rules for your organization. + Contact our support team for help designing policies for your organization. diff --git a/docs/edge/ko/enterprise/features/agent-control-plane/monitoring.mdx b/docs/edge/ko/enterprise/features/agent-control-plane/monitoring.mdx index c8ea48fbb..21a630e19 100644 --- a/docs/edge/ko/enterprise/features/agent-control-plane/monitoring.mdx +++ b/docs/edge/ko/enterprise/features/agent-control-plane/monitoring.mdx @@ -11,7 +11,7 @@ mode: "wide" - [개요](/ko/enterprise/features/agent-control-plane/overview) - **모니터링** *(현재 페이지)* - - [규칙](/ko/enterprise/features/agent-control-plane/rules) + - [정책](/edge/ko/enterprise/features/agent-control-plane/policies) ## 개요 @@ -58,7 +58,7 @@ mode: "wide" | **Last execution** | 가장 최근 실행 이후 경과 시간. | | **Health Status Breakdown** | 윈도우 내 실행에 대한 `Critical` / `Warning` / `Healthy` 비율의 누적 막대. | | **Executions with Errors** | 윈도우 내 총 실패 실행 수. | -| **PII detection applied** | deployment별 PII 설정 또는 일치하는 [PII 규칙](/ko/enterprise/features/agent-control-plane/rules)이 활성화된 경우 `Yes`. | +| **PII detection applied** | deployment별 PII 설정 또는 일치하는 [PII 정책](/edge/ko/enterprise/features/agent-control-plane/policies)이 활성화된 경우 `Yes`. | | **Executions** | 윈도우 내 총 실행 수. | | **Last updated** | deployment의 마지막 재배포 시점. | | **Crew Version** | deployment가 보고한 `crewai` 버전. `1.13` 미만 버전 옆의 정보 아이콘은 메트릭에 기여할 수 없는 행을 표시합니다. | @@ -96,8 +96,8 @@ mode: "wide" ACP란 무엇이며, 요구사항, 플랜 등급, RBAC에 대해. - - 조직 단위 PII Redaction 규칙을 여러 자동화에 적용합니다. + + 조직 단위 PII Redaction 정책을 여러 자동화에 적용합니다. 개별 실행을 드릴다운하여 에이전트의 추론, 도구 호출, 토큰 사용량을 확인합니다. diff --git a/docs/edge/ko/enterprise/features/agent-control-plane/overview.mdx b/docs/edge/ko/enterprise/features/agent-control-plane/overview.mdx index 9af73ac16..fe55b41a2 100644 --- a/docs/edge/ko/enterprise/features/agent-control-plane/overview.mdx +++ b/docs/edge/ko/enterprise/features/agent-control-plane/overview.mdx @@ -10,17 +10,17 @@ icon: "book-open" - **개요** *(현재 페이지)* - [모니터링](/ko/enterprise/features/agent-control-plane/monitoring) - - [규칙](/ko/enterprise/features/agent-control-plane/rules) + - [정책](/edge/ko/enterprise/features/agent-control-plane/policies) ## 개요 -**Agent Control Plane**(ACP)은 CrewAI AMP에서 실행 중인 모든 워크로드를 위한 운영 허브입니다. **Automations**와 **Rules** 두 개의 탭으로 구성된 단일 화면에서 다음 작업을 할 수 있습니다: +**Agent Control Plane**(ACP)은 CrewAI AMP에서 실행 중인 모든 워크로드를 위한 운영 허브입니다. **Automations**와 **Policies** 두 개의 탭으로 구성된 단일 화면에서 다음 작업을 할 수 있습니다: - 모든 라이브 자동화(crew 또는 flow)의 **상태(health)**를 `Critical` / `Warning` / `Healthy` 분포와 실행 횟수로 모니터링합니다. - 자동화별·공급자별·모델별 **LLM 소비**(토큰 및 비용)를 추적하고, 이전 기간 대비 변화량을 확인합니다. - 임의의 자동화 또는 모델 공급자를 드릴다운하여 시계열 차트와 공급자별 분해를 살펴봅니다. -- 조직 전체에 **규칙(Rules)**(현재: PII Redaction)을 적용하여 각 deployment를 개별 편집하지 않고 한 번에 여러 자동화에 정책을 강제합니다. +- 조직 전체에 **정책(Policies)**(현재: PII Redaction)을 적용하여 각 deployment를 개별 편집하지 않고 한 번에 여러 자동화에 정책을 강제합니다. ![Agent Control Plane 개요](/images/enterprise/acp-overview-automations-sankey.png) @@ -33,7 +33,7 @@ icon: "book-open" 두 탭은 서로 다른 두 가지 질문에 답합니다: - **Automations** — *"지금 내 플릿은 어떻게 동작하고 있고, 얼마나 비용이 들고 있는가?"* [모니터링](/ko/enterprise/features/agent-control-plane/monitoring)을 참고하세요. -- **Rules** — *"정책(예: PII redaction)을 매번 재배포하지 않고 여러 deployment에 어떻게 강제할 수 있는가?"* [규칙](/ko/enterprise/features/agent-control-plane/rules)을 참고하세요. +- **Policies** — *"정책(예: PII redaction)을 매번 재배포하지 않고 여러 deployment에 어떻게 강제할 수 있는가?"* [정책](/edge/ko/enterprise/features/agent-control-plane/policies)을 참고하세요. ## 요구사항 @@ -42,11 +42,11 @@ icon: "book-open" - [규칙](/ko/enterprise/features/agent-control-plane/rules)을 생성하거나 편집하려면 **Enterprise 또는 Ultra 플랜**이 필요합니다. 하위 플랜의 조직도 Rules 탭을 열고 기존 규칙을 볼 수 있지만, 편집기는 "Enterprise" 잠금 핀과 *"PII Redaction rules require an Enterprise plan."* 경고와 함께 읽기 전용으로 표시됩니다. 모니터링(Automations 탭)은 기능이 활성화된 모든 플랜에서 사용할 수 있습니다. + [정책](/edge/ko/enterprise/features/agent-control-plane/policies)을 생성하거나 편집하려면 **Enterprise 또는 Ultra 플랜**이 필요합니다. 하위 플랜의 조직도 Policies 탭을 열고 기존 정책을 볼 수 있지만, 편집기는 "Enterprise" 잠금 핀과 *"PII Redaction policies require an Enterprise plan."* 경고와 함께 읽기 전용으로 표시됩니다. 모니터링(Automations 탭)은 기능이 활성화된 모든 플랜에서 사용할 수 있습니다. - **Agent Control Plane** 기능이 조직에 대해 활성화되어 있어야 합니다. 사이드바에 보이지 않으면 계정 오너에게 활성화를 요청하세요. -- ACP 내부에서는 [RBAC](/ko/enterprise/features/rbac)가 접근 권한을 관리합니다: 대시보드 및 규칙을 보려면 `read`, 규칙을 생성·편집·토글·삭제하려면 `manage` 권한이 필요합니다. +- ACP 내부에서는 [RBAC](/ko/enterprise/features/rbac)가 접근 권한을 관리합니다: 대시보드 및 정책을 보려면 `read`, 정책을 생성·편집·토글·삭제하려면 `manage` 권한이 필요합니다. - 모든 차트와 테이블은 오른쪽 상단의 시간 선택기를 통해 **지난 24시간**, **지난 1주**, **지난 30일**로 범위를 조정할 수 있습니다. 변화량(`↑ 8 vs yesterday`, `↓ $20.57 vs yesterday` 등)은 선택한 윈도우를 같은 길이의 이전 윈도우와 비교합니다. ## 여기에서 할 수 있는 일 @@ -55,7 +55,7 @@ icon: "book-open" 메트릭 카드, 인터랙티브 sankey, 자동화별 테이블, 자동화 또는 공급자별 드릴다운 사이드 패널로 플릿 상태와 LLM 지출을 살펴봅니다. - + 도구와 태그로 범위를 지정한 PII Redaction 정책을 조직 단위로 적용합니다. 변경 사항은 다음 실행부터 적용되며 재배포가 필요 없습니다. @@ -67,10 +67,10 @@ icon: "book-open" 개별 실행을 드릴다운하여 에이전트의 추론, 도구 호출, 토큰 사용량을 확인합니다. - 누가 Agent Control Plane을 읽을 수 있고 누가 규칙을 편집할 수 있는지 관리합니다. + 누가 Agent Control Plane을 읽을 수 있고 누가 정책을 편집할 수 있는지 관리합니다. - 규칙이 참조하는 엔티티 카탈로그 및 deployment 단위 PII 설정. + 정책이 참조하는 엔티티 카탈로그 및 deployment 단위 PII 설정. Agent Control Plane을 지원하는 crewAI 버전으로 crew를 배포합니다. @@ -78,5 +78,5 @@ icon: "book-open" - 메트릭 해석 또는 규칙 설계에 도움이 필요하시면 지원 팀에 문의하세요. + 메트릭 해석 또는 정책 설계에 도움이 필요하시면 지원 팀에 문의하세요. diff --git a/docs/edge/ko/enterprise/features/agent-control-plane/rules.mdx b/docs/edge/ko/enterprise/features/agent-control-plane/policies.mdx similarity index 59% rename from docs/edge/ko/enterprise/features/agent-control-plane/rules.mdx rename to docs/edge/ko/enterprise/features/agent-control-plane/policies.mdx index b4e9e6b6a..5b2f20585 100644 --- a/docs/edge/ko/enterprise/features/agent-control-plane/rules.mdx +++ b/docs/edge/ko/enterprise/features/agent-control-plane/policies.mdx @@ -1,7 +1,7 @@ --- -title: "규칙 설정하기" +title: "정책 설정하기" description: "한 곳에서 조직 단위 정책을 여러 자동화에 적용합니다." -sidebarTitle: "규칙" +sidebarTitle: "정책" icon: "shield-check" mode: "wide" --- @@ -11,50 +11,50 @@ mode: "wide" - [개요](/ko/enterprise/features/agent-control-plane/overview) - [모니터링](/ko/enterprise/features/agent-control-plane/monitoring) - - **규칙** *(현재 페이지)* + - **정책** *(현재 페이지)* ## 개요 -규칙(Rules)은 각 deployment를 개별 설정하는 대신, 정책 — 현재: **PII Redaction** — 을 한 번에 여러 자동화에 적용할 수 있게 해줍니다. 관리하려면 [Agent Control Plane](/ko/enterprise/features/agent-control-plane/overview)에서 **Rules** 탭을 엽니다. +정책(Policies)은 각 deployment를 개별 설정하는 대신, 정책 — 현재: **PII Redaction** — 을 한 번에 여러 자동화에 적용할 수 있게 해줍니다. 관리하려면 [Agent Control Plane](/ko/enterprise/features/agent-control-plane/overview)에서 **Policies** 탭을 엽니다. - ![규칙 목록](/images/enterprise/acp-rules-list.png) + ![정책 목록](/images/enterprise/acp-policies-list.png) -각 규칙 카드에는 이름, 설명, 규칙이 적용되는 **범위(scope)**(선택된 도구와 태그), 그리고 현재 범위와 일치하는 deployment의 수인 **engaged automations**가 표시됩니다. 오른쪽 토글로 규칙을 삭제하지 않고 활성/비활성할 수 있습니다. +각 정책 카드에는 이름, 설명, 정책이 적용되는 **범위(scope)**(선택된 도구와 태그), 그리고 현재 범위와 일치하는 deployment의 수인 **engaged automations**가 표시됩니다. 오른쪽 토글로 정책을 삭제하지 않고 활성/비활성할 수 있습니다. ## 요구사항 - PII Redaction 규칙을 생성하거나 편집하려면 **Enterprise 또는 Ultra 플랜**이 필요합니다. 하위 플랜의 조직도 Rules 탭을 열고 기존 규칙을 볼 수는 있지만, 편집기는 "Enterprise" 잠금 핀과 *"PII Redaction rules require an Enterprise plan."* 경고와 함께 읽기 전용으로 렌더링됩니다. 업그레이드하려면 계정 오너 또는 영업팀에 문의하세요. + PII Redaction 정책을 생성하거나 편집하려면 **Enterprise 또는 Ultra 플랜**이 필요합니다. 하위 플랜의 조직도 Policies 탭을 열고 기존 정책을 볼 수는 있지만, 편집기는 "Enterprise" 잠금 핀과 *"PII Redaction policies require an Enterprise plan."* 경고와 함께 읽기 전용으로 렌더링됩니다. 업그레이드하려면 계정 오너 또는 영업팀에 문의하세요. - **Agent Control Plane** 기능이 조직에 대해 활성화되어 있어야 합니다. [개요 — 요구사항](/ko/enterprise/features/agent-control-plane/overview#요구사항)을 참고하세요. -- 규칙을 생성·편집·토글·삭제하려면 Agent Control Plane에 대한 [RBAC](/ko/enterprise/features/rbac)의 `manage` 권한이 필요합니다. 보려면 `read` 권한만으로 충분합니다. -- 모든 규칙 변경은 감사를 위해 버전 관리됩니다. +- 정책을 생성·편집·토글·삭제하려면 Agent Control Plane에 대한 [RBAC](/ko/enterprise/features/rbac)의 `manage` 권한이 필요합니다. 보려면 `read` 권한만으로 충분합니다. +- 모든 정책 변경은 감사를 위해 버전 관리됩니다. -## 사용 가능한 규칙 유형 +## 사용 가능한 정책 유형 | 유형 | 동작 | |------|---------------| | **PII Redaction** | 일치하는 모든 자동화의 실행에 PII redaction을 적용합니다. [Traces용 PII Redaction](/ko/enterprise/features/pii-trace-redactions)에 문서화된 동일한 엔티티 카탈로그와 커스텀 recognizer를 사용합니다. | -향후 더 많은 규칙 유형이 추가될 예정입니다. +향후 더 많은 정책 유형이 추가될 예정입니다. -## 규칙 만들기 +## 정책 만들기 - 조건 및 PII 마스크 유형이 있는 규칙 편집 사이드 패널 + 조건 및 PII 마스크 유형이 있는 정책 편집 사이드 패널 - Rules 탭 오른쪽 상단의 **+ Create new**를 클릭하거나, 기존 규칙 카드의 **View Details**를 클릭합니다. + Policies 탭 오른쪽 상단의 **+ Create new**를 클릭하거나, 기존 정책 카드의 **View Details**를 클릭합니다. - - 규칙에 명확한 이름(예: *Mask PII (CC)*)과 적용 시점을 설명하는 description을 부여합니다. 둘 다 규칙 카드와 Engaged Automations 모달에 표시됩니다. + + 정책에 명확한 이름(예: *Mask PII (CC)*)과 적용 시점을 설명하는 description을 부여합니다. 둘 다 정책 카드와 Engaged Automations 모달에 표시됩니다. @@ -62,12 +62,12 @@ mode: "wide" - 조건은 규칙이 어떤 자동화에 engage 할지 결정합니다. 둘 다 선택 사항이며 **집합 동일성(set-equality)** 의미론을 사용합니다: + 조건은 정책이 어떤 자동화에 engage 할지 결정합니다. 둘 다 선택 사항이며 **집합 동일성(set-equality)** 의미론을 사용합니다: - **Tools** — 도구 집합이 선택된 도구와 **정확히 일치**하는 자동화만 engage 됩니다. Studio 앱, MCP, OSS 도구, Tool Repository registry 도구 중에서 선택합니다. - **Automations** — 태그 집합이 선택된 태그와 **정확히 일치**하는 자동화만 engage 됩니다. - 피커를 비워두면 "이 차원에서 필터링하지 않음"을 의미합니다. 두 피커를 모두 비워두면 규칙이 조직의 **모든** 자동화에 적용됩니다. + 피커를 비워두면 "이 차원에서 필터링하지 않음"을 의미합니다. 두 피커를 모두 비워두면 정책이 조직의 **모든** 자동화에 적용됩니다. @@ -75,30 +75,30 @@ mode: "wide" - 저장하는 즉시 engage 된 모든 자동화의 **향후** 실행에 규칙이 적용됩니다. 재배포는 필요 없습니다. + 저장하는 즉시 engage 된 모든 자동화의 **향후** 실행에 정책이 적용됩니다. 재배포는 필요 없습니다. ## Engaged automations -규칙 카드의 **Engaged N automations**를 클릭하면 현재 규칙이 일치시키고 있는 deployment와 각 deployment의 마지막 실행을 정확히 확인할 수 있습니다. +정책 카드의 **Engaged N automations**를 클릭하면 현재 정책이 일치시키고 있는 deployment와 각 deployment의 마지막 실행을 정확히 확인할 수 있습니다. - ![Engaged automations 모달](/images/enterprise/acp-rules-engaged-modal.png) + ![Engaged automations 모달](/images/enterprise/acp-policies-engaged-modal.png) -규칙을 활성화하기 전에 범위를 빠르게 점검하는 가장 좋은 방법입니다. 예를 들어, `production` 태그로 범위를 지정한 규칙이 의도치 않게 staging deployment를 일치시키지 않는지 확인할 수 있습니다. +정책을 활성화하기 전에 범위를 빠르게 점검하는 가장 좋은 방법입니다. 예를 들어, `production` 태그로 범위를 지정한 정책이 의도치 않게 staging deployment를 일치시키지 않는지 확인할 수 있습니다. -## 조직 단위 규칙 vs deployment 단위 설정 +## 조직 단위 정책 vs deployment 단위 설정 PII Redaction은 두 곳에서 설정할 수 있습니다: - **deployment 단위** — 각 deployment의 **Settings → PII Protection** ([가이드](/ko/enterprise/features/pii-trace-redactions)) -- **조직 단위** — 이 페이지의 규칙 +- **조직 단위** — 이 페이지의 정책 -활성화된 조직 단위 규칙의 범위가 어떤 deployment와 일치하면, 규칙의 엔티티 구성이 그 deployment의 실행에 대해 **deployment가 소유한 PII 설정을 덮어씁니다**. 규칙이 연결된 동안에는 규칙이 단일 진실 공급원이 됩니다. 규칙을 비활성화하거나 분리하면(또는 범위를 변경하여 더 이상 일치하지 않게 만들면) deployment는 자체 PII Protection 설정으로 되돌아갑니다. +활성화된 조직 단위 정책의 범위가 어떤 deployment와 일치하면, 정책의 엔티티 구성이 그 deployment의 실행에 대해 **deployment가 소유한 PII 설정을 덮어씁니다**. 정책이 연결된 동안에는 정책이 단일 진실 공급원이 됩니다. 정책을 비활성화하거나 분리하면(또는 범위를 변경하여 더 이상 일치하지 않게 만들면) deployment는 자체 PII Protection 설정으로 되돌아갑니다. -여러 deployment에 걸쳐 일관된 정책을 강제하고 싶을 때는 조직 단위 규칙을 선호하고, 일회성 예외에 대해서는 deployment 단위 설정을 사용하세요. +여러 deployment에 걸쳐 일관된 정책을 강제하고 싶을 때는 조직 단위 정책을 선호하고, 일회성 예외에 대해서는 deployment 단위 설정을 사용하세요. ## 관련 문서 @@ -113,10 +113,10 @@ PII Redaction은 두 곳에서 설정할 수 있습니다: 엔티티 카탈로그, 커스텀 recognizer, deployment 단위 구성. - 누가 규칙을 만들거나 편집할 수 있는지 관리합니다. + 누가 정책을 만들거나 편집할 수 있는지 관리합니다. - 조직의 규칙을 설계하는 데 도움이 필요하시면 지원 팀에 문의하세요. + 조직의 정책을 설계하는 데 도움이 필요하시면 지원 팀에 문의하세요. diff --git a/docs/edge/pt-BR/enterprise/features/agent-control-plane/monitoring.mdx b/docs/edge/pt-BR/enterprise/features/agent-control-plane/monitoring.mdx index f578423d6..2ab71fdde 100644 --- a/docs/edge/pt-BR/enterprise/features/agent-control-plane/monitoring.mdx +++ b/docs/edge/pt-BR/enterprise/features/agent-control-plane/monitoring.mdx @@ -11,7 +11,7 @@ mode: "wide" - [Visão Geral](/pt-BR/enterprise/features/agent-control-plane/overview) - **Monitoramento** *(você está aqui)* - - [Regras](/pt-BR/enterprise/features/agent-control-plane/rules) + - [Políticas](/edge/pt-BR/enterprise/features/agent-control-plane/policies) ## Visão Geral @@ -58,7 +58,7 @@ A sub-aba **Automações** é o detalhamento por deployment da saúde da frota. | **Última execução** | Tempo decorrido desde a execução mais recente. | | **Health Status Breakdown** | Barra empilhada com percentuais de `Critical` / `Warning` / `Healthy` para as execuções na janela. | | **Executions with Errors** | Total de execuções com falha na janela. | -| **PII detection applied** | `Yes` se houver configuração de PII por deployment ou uma [regra de PII](/pt-BR/enterprise/features/agent-control-plane/rules) correspondente ativa. | +| **PII detection applied** | `Yes` se houver configuração de PII por deployment ou uma [política de PII](/edge/pt-BR/enterprise/features/agent-control-plane/policies) correspondente ativa. | | **Executions** | Total de execuções na janela. | | **Last updated** | Quando o deployment foi re-implantado pela última vez. | | **Crew Version** | A versão do `crewai` reportada pelo deployment. Um ícone de informação ao lado de versões abaixo de `1.13` indica linhas que não conseguem contribuir com métricas. | @@ -96,8 +96,8 @@ Filtre por **LLM provider** e ordene por `Cost`, `Executions` ou `Last run`. O que é o ACP, requisitos, planos suportados e RBAC. - - Aplique regras de PII Redaction em nível de organização em muitas automações. + + Aplique políticas de PII Redaction em nível de organização em muitas automações. Aprofunde em uma única execução para ver o raciocínio do agente, chamadas de ferramentas e uso de tokens. diff --git a/docs/edge/pt-BR/enterprise/features/agent-control-plane/overview.mdx b/docs/edge/pt-BR/enterprise/features/agent-control-plane/overview.mdx index 750309bac..a36ae2ab2 100644 --- a/docs/edge/pt-BR/enterprise/features/agent-control-plane/overview.mdx +++ b/docs/edge/pt-BR/enterprise/features/agent-control-plane/overview.mdx @@ -10,17 +10,17 @@ icon: "book-open" - **Visão Geral** *(você está aqui)* - [Monitoramento](/pt-BR/enterprise/features/agent-control-plane/monitoring) - - [Regras](/pt-BR/enterprise/features/agent-control-plane/rules) + - [Políticas](/edge/pt-BR/enterprise/features/agent-control-plane/policies) ## Visão Geral -O **Agent Control Plane** (ACP) é o hub de operações para tudo que você tem rodando no CrewAI AMP. É uma tela única — dividida nas abas **Automações** e **Regras** — que permite à sua equipe: +O **Agent Control Plane** (ACP) é o hub de operações para tudo que você tem rodando no CrewAI AMP. É uma tela única — dividida nas abas **Automações** e **Políticas** — que permite à sua equipe: - Monitorar a **saúde** de cada automação ao vivo (crew ou flow), com detalhamentos `Critical` / `Warning` / `Healthy` e contagem de execuções. - Acompanhar o **consumo de LLM** — tokens e custo — por automação, por provedor e por modelo, com a variação em relação ao período anterior. - Aprofundar em qualquer automação ou provedor de modelo para ver gráficos de série temporal e detalhamentos por provedor. -- Aplicar **Regras** em nível de organização (hoje: PII Redaction) em muitas automações de uma só vez, em vez de editar cada deployment individualmente. +- Aplicar **Políticas** em nível de organização (hoje: PII Redaction) em muitas automações de uma só vez, em vez de editar cada deployment individualmente. ![Visão geral do Agent Control Plane](/images/enterprise/acp-overview-automations-sankey.png) @@ -33,7 +33,7 @@ O **Agent Control Plane** (ACP) é o hub de operações para tudo que você tem As duas abas respondem a duas perguntas distintas: - **Automações** — *"Como minha frota está se comportando agora e quanto está me custando?"* Veja [Monitoramento](/pt-BR/enterprise/features/agent-control-plane/monitoring). -- **Regras** — *"Como aplico uma política (por exemplo, PII redaction) em muitos deployments sem precisar reimplantar cada um?"* Veja [Regras](/pt-BR/enterprise/features/agent-control-plane/rules). +- **Políticas** — *"Como aplico uma política (por exemplo, PII redaction) em muitos deployments sem precisar reimplantar cada um?"* Veja [Políticas](/edge/pt-BR/enterprise/features/agent-control-plane/policies). ## Requisitos @@ -42,11 +42,11 @@ As duas abas respondem a duas perguntas distintas: - **Plano Enterprise ou Ultra** é necessário para criar ou editar [Regras](/pt-BR/enterprise/features/agent-control-plane/rules). Organizações em planos inferiores ainda podem abrir a aba Regras e visualizar regras existentes, mas o editor é renderizado em modo somente leitura, com um selo "Enterprise" de bloqueio e o alerta *"PII Redaction rules require an Enterprise plan."* O Monitoramento (a aba Automações) está disponível em todos os planos em que o recurso esteja habilitado. + **Plano Enterprise ou Ultra** é necessário para criar ou editar [Políticas](/edge/pt-BR/enterprise/features/agent-control-plane/policies). Organizações em planos inferiores ainda podem abrir a aba Políticas e visualizar políticas existentes, mas o editor é renderizado em modo somente leitura, com um selo "Enterprise" de bloqueio e o alerta *"PII Redaction policies require an Enterprise plan."* O Monitoramento (a aba Automações) está disponível em todos os planos em que o recurso esteja habilitado. - O recurso **Agent Control Plane** precisa estar habilitado para sua organização. Se você não o vê na barra lateral, peça ao owner da conta para solicitar a habilitação. -- Dentro do ACP, o [RBAC](/pt-BR/enterprise/features/rbac) controla o acesso: `read` para visualizar o dashboard e as regras, `manage` para criar, editar, ligar/desligar ou excluir regras. +- Dentro do ACP, o [RBAC](/pt-BR/enterprise/features/rbac) controla o acesso: `read` para visualizar o dashboard e as políticas, `manage` para criar, editar, ligar/desligar ou excluir políticas. - Todos os gráficos e tabelas podem ser ajustados para **Últimas 24 horas**, **Última Semana** ou **Últimos 30 dias** usando o seletor de tempo no canto superior direito. As variações (`↑ 8 vs ontem`, `↓ $20.57 vs ontem`, etc.) comparam a janela selecionada com a janela anterior de mesma duração. ## O que você pode fazer aqui @@ -55,7 +55,7 @@ As duas abas respondem a duas perguntas distintas: Acompanhe a saúde da frota e o gasto com LLM com cards de métricas, um sankey interativo, tabelas por automação e painéis laterais de detalhamento para qualquer automação ou provedor. - + Aplique políticas de PII Redaction em nível de organização, com escopo por ferramentas e tags. As mudanças entram em vigor na próxima execução — sem necessidade de re-implantação. @@ -67,10 +67,10 @@ As duas abas respondem a duas perguntas distintas: Aprofunde em uma única execução para ver o raciocínio do agente, chamadas de ferramentas e uso de tokens. - Gerencie quem pode ler o Agent Control Plane e quem pode editar regras. + Gerencie quem pode ler o Agent Control Plane e quem pode editar políticas. - Catálogo de entidades e configuração de PII por deployment, referenciados pelas Regras. + Catálogo de entidades e configuração de PII por deployment, referenciados pelas Políticas. Implante uma crew em uma versão do crewAI que suporta o Agent Control Plane. @@ -78,5 +78,5 @@ As duas abas respondem a duas perguntas distintas: - Entre em contato com nosso time de suporte para interpretar métricas ou desenhar regras. + Entre em contato com nosso time de suporte para interpretar métricas ou desenhar políticas. diff --git a/docs/edge/pt-BR/enterprise/features/agent-control-plane/policies.mdx b/docs/edge/pt-BR/enterprise/features/agent-control-plane/policies.mdx new file mode 100644 index 000000000..bede4e360 --- /dev/null +++ b/docs/edge/pt-BR/enterprise/features/agent-control-plane/policies.mdx @@ -0,0 +1,122 @@ +--- +title: "Configure as Políticas" +description: "Aplique políticas em nível de organização em muitas automações a partir de um único lugar." +sidebarTitle: "Políticas" +icon: "shield-check" +mode: "wide" +--- + + + **Navegação da Documentação do ACP (Beta)** + + - [Visão Geral](/pt-BR/enterprise/features/agent-control-plane/overview) + - [Monitoramento](/pt-BR/enterprise/features/agent-control-plane/monitoring) + - **Políticas** *(você está aqui)* + + +## Visão Geral + +As Políticas permitem aplicar políticas — hoje: **PII Redaction** — em muitas automações de uma só vez, em vez de configurar cada deployment individualmente. Abra a aba **Políticas** no [Agent Control Plane](/pt-BR/enterprise/features/agent-control-plane/overview) para gerenciá-las. + + + ![Lista de políticas](/images/enterprise/acp-policies-list.png) + + +Cada card de política mostra o nome, a descrição, o **escopo** ao qual a política se aplica (ferramentas e tags selecionadas) e a contagem de **automações engajadas** — deployments que atualmente correspondem ao escopo. O toggle à direita ativa ou desativa a política sem excluí-la. + +## Requisitos + + + **Plano Enterprise ou Ultra** é necessário para criar ou editar políticas de PII Redaction. Organizações em planos inferiores ainda podem abrir a aba Políticas e visualizar políticas existentes, mas o editor é renderizado em modo somente leitura, com um selo "Enterprise" de bloqueio e o alerta *"PII Redaction policies require an Enterprise plan."* — entre em contato com o owner da sua conta ou com vendas para fazer upgrade. + + +- O recurso **Agent Control Plane** precisa estar habilitado para sua organização. Veja [Visão Geral — Requisitos](/pt-BR/enterprise/features/agent-control-plane/overview#requisitos). +- A permissão `manage` no [RBAC](/pt-BR/enterprise/features/rbac) sobre o Agent Control Plane é necessária para criar, editar, ligar/desligar ou excluir políticas. A permissão `read` é suficiente para visualizá-las. +- Todas as mudanças de políticas são versionadas para auditoria. + +## Tipos de política disponíveis + +| Tipo | O que faz | +|------|---------------| +| **PII Redaction** | Aplica PII redaction às execuções de cada automação correspondente, usando o mesmo catálogo de entidades e recognizers customizados documentados em [PII Redaction para Traces](/pt-BR/enterprise/features/pii-trace-redactions). | + +Mais tipos de políticas serão adicionados ao longo do tempo. + +## Criando uma política + + + Painel lateral de edição de política com condições e tipo de máscara de PII + + + + + Clique em **+ Create new** no canto superior direito da aba Políticas, ou em **View Details** em um card de política existente. + + + + Dê à política um nome claro (ex.: *Mask PII (CC)*) e uma descrição explicando quando ela se aplica. Ambos aparecem no card da política e no modal de Automações Engajadas. + + + + Hoje só **PII Redaction** está disponível. + + + + As condições decidem quais automações a política engaja. Ambas são opcionais e usam a semântica de **igualdade de conjuntos**: + + - **Tools** — apenas automações cujo conjunto de ferramentas **corresponde exatamente** às ferramentas selecionadas serão engajadas. Selecione entre apps do Studio, MCPs, ferramentas OSS e ferramentas do Tool Repository. + - **Automations** — apenas automações cujo conjunto de tags **corresponde exatamente** às tags selecionadas serão engajadas. + + Deixar um seletor vazio significa "sem filtro nesta dimensão". Deixar ambos vazios significa que a política se aplica a **todas** as automações da organização. + + + + Marque cada tipo de entidade que deseja cobrir e escolha **Mask** (substitui pelo rótulo da entidade, ex.: ``) ou **Redact** (remove o texto correspondente por completo). Veja [PII Redaction para Traces](/pt-BR/enterprise/features/pii-trace-redactions) para o catálogo completo de entidades e como adicionar recognizers customizados em nível de organização. + + + + A política se aplica a **futuras** execuções de cada automação engajada assim que você salva. Nenhuma re-implantação é necessária. + + + +## Automações engajadas + +Clique em **Engaged N automations** em qualquer card de política para ver exatamente quais deployments a política está correspondendo no momento, junto com a última execução de cada um. + + + ![Modal de automações engajadas](/images/enterprise/acp-policies-engaged-modal.png) + + +Esta é a forma mais rápida de validar o escopo de uma política antes de habilitá-la — por exemplo, para confirmar que uma política com escopo na tag `production` não está acidentalmente correspondendo a um deployment de staging. + +## Políticas em nível de organização vs configurações por deployment + +A PII Redaction pode ser configurada em dois lugares: + +- **Por deployment** — em **Settings → PII Protection** em cada deployment individual ([guia](/pt-BR/enterprise/features/pii-trace-redactions)) +- **Em nível de organização** — como uma Política nesta página + +Quando o escopo de uma política habilitada em nível de organização corresponde a um deployment, a configuração de entidades da política **sobrescreve** as configurações de PII pertencentes ao deployment para as execuções daquele deployment — a política se torna a fonte única da verdade enquanto está vinculada. Desabilite ou desvincule a política (ou altere o escopo para que ela não corresponda mais) e o deployment volta às suas próprias configurações de PII Protection. + +Prefira políticas em nível de organização quando quiser impor uma política consistente em muitos deployments; reserve a configuração por deployment para exceções pontuais. + +## Relacionados + + + + O que é o ACP, requisitos, planos suportados e RBAC. + + + Acompanhe automações e consumo de LLM em toda a sua frota. + + + Catálogo de entidades, recognizers customizados e configuração por deployment. + + + Gerencie quem pode criar ou editar políticas. + + + + + Entre em contato com nosso time de suporte para ajudar a desenhar políticas para a sua organização. + diff --git a/docs/edge/pt-BR/enterprise/features/agent-control-plane/rules.mdx b/docs/edge/pt-BR/enterprise/features/agent-control-plane/rules.mdx deleted file mode 100644 index 7d00fec86..000000000 --- a/docs/edge/pt-BR/enterprise/features/agent-control-plane/rules.mdx +++ /dev/null @@ -1,122 +0,0 @@ ---- -title: "Configure as Regras" -description: "Aplique políticas em nível de organização em muitas automações a partir de um único lugar." -sidebarTitle: "Regras" -icon: "shield-check" -mode: "wide" ---- - - - **Navegação da Documentação do ACP (Beta)** - - - [Visão Geral](/pt-BR/enterprise/features/agent-control-plane/overview) - - [Monitoramento](/pt-BR/enterprise/features/agent-control-plane/monitoring) - - **Regras** *(você está aqui)* - - -## Visão Geral - -As Regras permitem aplicar políticas — hoje: **PII Redaction** — em muitas automações de uma só vez, em vez de configurar cada deployment individualmente. Abra a aba **Regras** no [Agent Control Plane](/pt-BR/enterprise/features/agent-control-plane/overview) para gerenciá-las. - - - ![Lista de regras](/images/enterprise/acp-rules-list.png) - - -Cada card de regra mostra o nome, a descrição, o **escopo** ao qual a regra se aplica (ferramentas e tags selecionadas) e a contagem de **automações engajadas** — deployments que atualmente correspondem ao escopo. O toggle à direita ativa ou desativa a regra sem excluí-la. - -## Requisitos - - - **Plano Enterprise ou Ultra** é necessário para criar ou editar regras de PII Redaction. Organizações em planos inferiores ainda podem abrir a aba Regras e visualizar regras existentes, mas o editor é renderizado em modo somente leitura, com um selo "Enterprise" de bloqueio e o alerta *"PII Redaction rules require an Enterprise plan."* — entre em contato com o owner da sua conta ou com vendas para fazer upgrade. - - -- O recurso **Agent Control Plane** precisa estar habilitado para sua organização. Veja [Visão Geral — Requisitos](/pt-BR/enterprise/features/agent-control-plane/overview#requisitos). -- A permissão `manage` no [RBAC](/pt-BR/enterprise/features/rbac) sobre o Agent Control Plane é necessária para criar, editar, ligar/desligar ou excluir regras. A permissão `read` é suficiente para visualizá-las. -- Todas as mudanças de regras são versionadas para auditoria. - -## Tipos de regra disponíveis - -| Tipo | O que faz | -|------|---------------| -| **PII Redaction** | Aplica PII redaction às execuções de cada automação correspondente, usando o mesmo catálogo de entidades e recognizers customizados documentados em [PII Redaction para Traces](/pt-BR/enterprise/features/pii-trace-redactions). | - -Mais tipos de regras serão adicionados ao longo do tempo. - -## Criando uma regra - - - Painel lateral de edição de regra com condições e tipo de máscara de PII - - - - - Clique em **+ Create new** no canto superior direito da aba Regras, ou em **View Details** em um card de regra existente. - - - - Dê à regra um nome claro (ex.: *Mask PII (CC)*) e uma descrição explicando quando ela se aplica. Ambos aparecem no card da regra e no modal de Automações Engajadas. - - - - Hoje só **PII Redaction** está disponível. - - - - As condições decidem quais automações a regra engaja. Ambas são opcionais e usam a semântica de **igualdade de conjuntos**: - - - **Tools** — apenas automações cujo conjunto de ferramentas **corresponde exatamente** às ferramentas selecionadas serão engajadas. Selecione entre apps do Studio, MCPs, ferramentas OSS e ferramentas do Tool Repository. - - **Automations** — apenas automações cujo conjunto de tags **corresponde exatamente** às tags selecionadas serão engajadas. - - Deixar um seletor vazio significa "sem filtro nesta dimensão". Deixar ambos vazios significa que a regra se aplica a **todas** as automações da organização. - - - - Marque cada tipo de entidade que deseja cobrir e escolha **Mask** (substitui pelo rótulo da entidade, ex.: ``) ou **Redact** (remove o texto correspondente por completo). Veja [PII Redaction para Traces](/pt-BR/enterprise/features/pii-trace-redactions) para o catálogo completo de entidades e como adicionar recognizers customizados em nível de organização. - - - - A regra se aplica a **futuras** execuções de cada automação engajada assim que você salva. Nenhuma re-implantação é necessária. - - - -## Automações engajadas - -Clique em **Engaged N automations** em qualquer card de regra para ver exatamente quais deployments a regra está correspondendo no momento, junto com a última execução de cada um. - - - ![Modal de automações engajadas](/images/enterprise/acp-rules-engaged-modal.png) - - -Esta é a forma mais rápida de validar o escopo de uma regra antes de habilitá-la — por exemplo, para confirmar que uma regra com escopo na tag `production` não está acidentalmente correspondendo a um deployment de staging. - -## Regras em nível de organização vs configurações por deployment - -A PII Redaction pode ser configurada em dois lugares: - -- **Por deployment** — em **Settings → PII Protection** em cada deployment individual ([guia](/pt-BR/enterprise/features/pii-trace-redactions)) -- **Em nível de organização** — como uma Regra nesta página - -Quando o escopo de uma regra habilitada em nível de organização corresponde a um deployment, a configuração de entidades da regra **sobrescreve** as configurações de PII pertencentes ao deployment para as execuções daquele deployment — a regra se torna a fonte única da verdade enquanto está vinculada. Desabilite ou desvincule a regra (ou altere o escopo para que ela não corresponda mais) e o deployment volta às suas próprias configurações de PII Protection. - -Prefira regras em nível de organização quando quiser impor uma política consistente em muitos deployments; reserve a configuração por deployment para exceções pontuais. - -## Relacionados - - - - O que é o ACP, requisitos, planos suportados e RBAC. - - - Acompanhe automações e consumo de LLM em toda a sua frota. - - - Catálogo de entidades, recognizers customizados e configuração por deployment. - - - Gerencie quem pode criar ou editar regras. - - - - - Entre em contato com nosso time de suporte para ajudar a desenhar regras para a sua organização. - diff --git a/docs/images/enterprise/acp-automations-table.png b/docs/images/enterprise/acp-automations-table.png index a4a935e91..b584f2a81 100644 Binary files a/docs/images/enterprise/acp-automations-table.png and b/docs/images/enterprise/acp-automations-table.png differ diff --git a/docs/images/enterprise/acp-consumption-table.png b/docs/images/enterprise/acp-consumption-table.png index 3ce838349..2b20f2dd6 100644 Binary files a/docs/images/enterprise/acp-consumption-table.png and b/docs/images/enterprise/acp-consumption-table.png differ diff --git a/docs/images/enterprise/acp-policies-edit-cost-limit.png b/docs/images/enterprise/acp-policies-edit-cost-limit.png new file mode 100644 index 000000000..e44f69815 Binary files /dev/null and b/docs/images/enterprise/acp-policies-edit-cost-limit.png differ diff --git a/docs/images/enterprise/acp-policies-engaged-modal.png b/docs/images/enterprise/acp-policies-engaged-modal.png new file mode 100644 index 000000000..48a89ad25 Binary files /dev/null and b/docs/images/enterprise/acp-policies-engaged-modal.png differ diff --git a/docs/images/enterprise/acp-policies-list.png b/docs/images/enterprise/acp-policies-list.png new file mode 100644 index 000000000..2db77e1ae Binary files /dev/null and b/docs/images/enterprise/acp-policies-list.png differ diff --git a/docs/images/enterprise/acp-policies-new-side-panel.png b/docs/images/enterprise/acp-policies-new-side-panel.png new file mode 100644 index 000000000..a2491756c Binary files /dev/null and b/docs/images/enterprise/acp-policies-new-side-panel.png differ