- Revenus de retraite et stratégie de décaissement
- Fiscalité : Roth/RRSP, récolte de pertes, évolutions réglementaires
- Succession, assurance et planification transfrontalière
- Outils du conseiller : préparation des rendez-vous, pré-contrôle de conformité
21 500+ compétences et agents. Tous gouvernés.
5,814 agents prêts à l'emploi et 15,654 compétences de bibliothèque couvrant 24 secteurs et 12 métiers par secteur — installables depuis le catalogue, connectés à vos systèmes et exécutés à travers la même chaîne de contrôles en échec fermé que tout le reste sur Cortex.
21,511 modèles de bibliothèque dans la matrice du catalogue
Partez d'une collection sélectionnée.
Des suites conçues à la main pour les tâches que les entreprises automatisent en premier — chaque collection est livrée gouvernée, politiques et audit inclus.
- Service, ventes et customer success
- Service desk IT, RH et finance ops
- Réception juridique, achats et opérations terrain
- Risque et conformité
- Tri de la boîte de réception et rédaction d'e-mails
- Préparation de réunions, notes et suivi
- Planification intelligente et briefing quotidien
- Orchestration d'assistant de direction
- Sinistres intelligents, actuariat et AML
- Audit, GRC et reporting ESG
- ITAM / ITSM et opérations de sécurité
- Ateliers data et analytics
Trouvez la compétence dont votre équipe a besoin.
Recherchez parmi 21,500+ compétences et agents gouvernés, ou filtrez par secteur et par type : chaque résultat s'installe depuis le catalogue et franchit les mêmes points de contrôle.
864 résultats · Legal Services
Summarize supplied request context — Privacy Officer, Legal Services
Summarize supplied request context for Privacy Officer teams in Legal Services, delivered by the Intake Review & Triage pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess urgency and risk — Privacy Officer, Legal Services
Assess urgency and risk for Privacy Officer teams in Legal Services, delivered by the Intake Review & Triage pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend a review priority — Privacy Officer, Legal Services
Recommend a review priority for Privacy Officer teams in Legal Services, delivered by the Intake Review & Triage pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Condense supplied content — Privacy Officer, Legal Services
Condense supplied content for Privacy Officer teams in Legal Services, delivered by the Document Summarizer pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Surface key points — Privacy Officer, Legal Services
Surface key points for Privacy Officer teams in Legal Services, delivered by the Document Summarizer pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Produce a concise brief — Privacy Officer, Legal Services
Produce a concise brief for Privacy Officer teams in Legal Services, delivered by the Document Summarizer pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Search approved knowledge — Privacy Officer, Legal Services
Search approved knowledge for Privacy Officer teams in Legal Services, delivered by the Q&A Assistant pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft a grounded response — Privacy Officer, Legal Services
Draft a grounded response for Privacy Officer teams in Legal Services, delivered by the Q&A Assistant pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a review-ready answer — Privacy Officer, Legal Services
Prepare a review-ready answer for Privacy Officer teams in Legal Services, delivered by the Q&A Assistant pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft from supplied context — Privacy Officer, Legal Services
Draft from supplied context for Privacy Officer teams in Legal Services, delivered by the Drafting & Generation pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Follow configured behavior guidance — Privacy Officer, Legal Services
Follow configured behavior guidance for Privacy Officer teams in Legal Services, delivered by the Drafting & Generation pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare copy for revision — Privacy Officer, Legal Services
Prepare copy for revision for Privacy Officer teams in Legal Services, delivered by the Drafting & Generation pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize a supplied record — Privacy Officer, Legal Services
Summarize a supplied record for Privacy Officer teams in Legal Services, delivered by the Record Review pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess possible risk — Privacy Officer, Legal Services
Assess possible risk for Privacy Officer teams in Legal Services, delivered by the Record Review pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Flag items for human review — Privacy Officer, Legal Services
Flag items for human review for Privacy Officer teams in Legal Services, delivered by the Record Review pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Run a parameterized read query — Privacy Officer, Legal Services
Run a parameterized read query for Privacy Officer teams in Legal Services, delivered by the Data Query & Summary pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize returned records — Privacy Officer, Legal Services
Summarize returned records for Privacy Officer teams in Legal Services, delivered by the Data Query & Summary pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a result-set overview — Privacy Officer, Legal Services
Prepare a result-set overview for Privacy Officer teams in Legal Services, delivered by the Data Query & Summary pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Check supplied context against policy — Privacy Officer, Legal Services
Check supplied context against policy for Privacy Officer teams in Legal Services, delivered by the Compliance Checker pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Surface potential policy issues — Privacy Officer, Legal Services
Surface potential policy issues for Privacy Officer teams in Legal Services, delivered by the Compliance Checker pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend review items — Privacy Officer, Legal Services
Recommend review items for Privacy Officer teams in Legal Services, delivered by the Compliance Checker pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess supplied risk context — Privacy Officer, Legal Services
Assess supplied risk context for Privacy Officer teams in Legal Services, delivered by the Risk Assessment pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Explain assessment drivers — Privacy Officer, Legal Services
Explain assessment drivers for Privacy Officer teams in Legal Services, delivered by the Risk Assessment pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend human review — Privacy Officer, Legal Services
Recommend human review for Privacy Officer teams in Legal Services, delivered by the Risk Assessment pattern from supplied context. iManage and Relativity are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
L'installation est la partie facile. La gouvernance vient avec.
Les agents de la bibliothèque ne sont pas des scripts — ce sont des identités gouvernées. En installer un l'enregistre avec un propriétaire, un budget, des modèles et des actions autorisés, et une place dans le registre d'audit.
Choisissez dans le catalogue
Filtrez par secteur et par rôle ; chaque élément indique les systèmes auxquels il se connecte et les compétences qu'il invoque.
Reliez-le à votre stack
Connecteurs, serveurs MCP et imports OpenAPI — cadrés par des listes d'autorisation et le DLP au niveau de la passerelle.
Chaque exécution passe les verrous
Identité, budget, garde-fous, registre, Control Tower, exécution, garde-fou de sortie — puis un reçu signé dans le Trust Ledger. Sur toutes les formules.
Vous ne trouvez pas la compétence qu'il vous faut ?
Le générateur visuel de compétences livre de nouvelles compétences sans code — ou dites-nous ce qui manque et nous vous orienterons vers le modèle gouverné le plus proche.