AI 模型和平台
Anthropic 新增智能报告,调查,集合预算给Claude企业
在 Google 上的首选来源中添加 Unite.AI
Anthropic使三个Claude Entertainment功能在2026年10月28日普遍开放:智能报告分析团队用Claude完成什么以及什么工作成本,收集员工反馈的应用中调查,集合组预算让管理员每个团队设置一个共享的月支出池。
智能报告:工作流程、成本和隐私护栏
管理员通过选择团队开始智能报告,日期范围覆盖到过去28天,产品包括(聊天,Claude Code,Claude Cowork,或综合聊天和Cowork体验). 根据Claude帮助中心的设置指南,Claude随后读取了该范围内的笔录样本,将其组合成工作流程和产出类型,按列表价格将支出附加到每个组,并写出调查结果。 报告通常需要几个小时才能生成,并且可以被下载为HTML,其钻头完好无损。
每一份报告都按届会和开支排序,其中多数使用显示;按产出类型(如分析、文件、内容草稿和代码)分类的可交付成果;每种产出的每届会议平均费用;任务结果;以及费用最高的会议集中之处。 痛点区块目录阻碍的东西,包括从未设置的连接器,错过请求、批准或签入吉特的输出,工具故障,以及复工环路,而低效率区块则计算出没有可用的会话,仅显示为总数和成本。
一份综合建议清单确定了值得转化为共享技能和规则的经常性工作流程,值得添加到一个代码存储库中,任何发现都可以作为文物共享。 报告还可以回答关于模型使用和成本的自定义问题,管理员可以将问题和自定义见解保存为可重复使用的模板。 拥有计费许可的管理员可以从报告中直接提高用户的支出限制,所有者可以让不属于管理员的团队领导为自己的团体管理报告。 报告的范围可以扩大到具有基于角色权限的团体,包括通过SCIM从身份提供者同步的团体,或者通过部门和成本中心属性过滤。
每个组织每月可免费提出多达10份报告,而且该功能默认关闭,直至主要所有人或所有人在组织环境中允许。 Anthropic表示,智能报告旨在理解Claude的收养和规划投资,而设计报告不是为了评估个人业绩或做出就业决定。
两条隐私护栏永久不变:自定义问题不能触及受限制的专题,涉及这些专题的Claude会旗只提供汇总分析,而不提供会议摘要。 限制名单涵盖受保护的特征、健康和医疗事项、工会活动、骚扰、举报人和法律投诉、政治或宗教观点、个人生活和对某个人的看法。 默认情况下,向个别用户的归属是无效的;当一个组织允许时,观众仍然看到“用户”代替姓名,直到他们积极披露姓名,而且每个披露都被记录下来。 使用客户管理的加密密钥,HIPAA配置或混合部署的组织完全不能使用智能报告,Claude Code零数据保留的组织只能得到覆盖聊天和 Cowork的报告。
Anthropic的公告包括周一,斯拉洛姆,维克斯,德勤,DoorDash,和多库西恩的声明。 称 Ran Yitzhaki是Wix的软件工程师。 Docusign 称报告显示,其团队如何使用Claude,从编码Docusign IAM,其AI-inative签约平台,到日常工作,可见度帮助其展现出真正的成果,并修复连接器瓶颈。 Vivek Kulkarni是德勤公司AI转型的总裁,DoorDash AI赋能带领约翰·詹诺内(John Jannone) 称智能报告露出他不知道的东西,尽管他的工作接近他的团队如何使用Claude.
App调查:默认问题和数据处理
企业计划可以进行调查,主要业主、业主、管理人员和有分析视野的定制角色可以建立这种调查。 Claude帮助中心的调查指南列出了四个默认问题:用户最近对Claude所做的最有价值的事情,以及他们如何能分辨结果比没有Claude要好;如果Claude在工作所花费的时间上有任何改变,那么Claude会有什么改变;使用Claude的一种方式是队友应该复制;如果球队失去对Claude的访问,会有什么突破或放慢。 管理者可以添加或删除问题,针对所有成员或特定群体,设定调查的开始和结束日期,并选择卡片是出现在聊天,合作,还是Claude Code中。
用户在自然休息时将调查视为一张小卡——在聊天中回复后,在合作中的任务之间,或在Claude完成Claude Code回复后,调查从不会中断运行中的任务。 该卡带有组织名称,表示答案由组织的管理员而不是Anthropic来回答,在调查进行期间,调查结果在调查网页上汇总,答复计数和费率,每次调查都作为CSV输出,其中包含提交时间、用户的电子邮件、用户组别、他们答复的表面以及每个问题各一栏。
调查答复作为组织的数据处理,它只能根据运行服务的需要获取这些数据。 调查支持客户管理的加密密钥,并遵循本组织的保留设置,调查及其答复在该时间表上被删除。 具有HIPAA配置的组织没有这种配置,Anthropic的文件指示受监管的客户不要将受监管的数据如PHI放入调查答复中。
集体预算:分担开支、提醒和限制
集合预算新增每月为一组成员分摊一个数额,以超过每个成员自己的每月开支限额。 每一份申请都以两者为理由,如果先用完,就有一个成员停止。 正如Anthropic所描述的那样,这种设计使得大量使用Claude的人在月初不会在同事未动用预算时碰到个人限制,而成员限制仍然是防止个人使用量异常高的护栏。 当一个成员达到限制时,Claude内部会有一个“要求更多”按钮,以及管理者审查的要求路线。 用户从未看到团体名称或集合金额。
Anthropic的集合预算文件建议从上一个月的实际开支中算出第一个数额,而不是一个估计数:集合预算大约是集团每月开支的三倍,成员限额大约是最大开支的三倍。 其实例表明,一个团体花费了1 450美元,其中最高开支为310美元,总预算为4 350美元,成员限额约为950美元。 持有计费许可的每个人都收到50%,75%,95%,100%的预算的电子邮件提示,使用时的酒吧转动琥珀75%,红色90%。 文件建议,如果预算在月20日之前使用75%,则考虑增加50%。
在基于使用的企业计划和具有使用权的 " 标准 " 或 " 特权 " 座席计划上,可以提供集合预算,因为其中仅适用于使用权,而包含座位的使用不计入集合。 当用户属于多个组时,最大的集合预算默认先支付,并有可选的自定义优先排序。 预算可冻结在0美元或暂停而不损失金额。 管理只在组织环境中进行,计费许可在全组织范围内适用,集合预算尚未通过行政API提供。
Anthropic 指出三种特性的可用性因配置而异,包括HIPAA配置或客户管理的加密密钥的组织,并将管理员点到Claude帮助中心,以获得资格和详细的设置步骤。
本文由 AI图鉴自动抓取并翻译,版权归原作者所有;如需查看原文请点下方链接。
AI Models & Platforms
Anthropic Adds Smart Reports, Surveys, Pooled Budgets to Claude Enterprise
Add Unite.AI to your preferred sources on Google
Anthropic made three Claude Enterprise features generally available on October 28, 2026: smart reports that analyze what teams accomplish with Claude and what that work costs, in-app surveys that gather employee feedback, and pooled group budgets that let administrators set one shared monthly spending pool per team.
Smart Reports: Workstreams, Costs, and Privacy Guardrails
An administrator starts a smart report by choosing a team, a date range covering up to the last 28 days, and the products to include (chat, Claude Code, Claude Cowork, or the combined chat and Cowork experience). According to the Claude Help Center’s setup guide, Claude then reads a sample of transcripts in that scope, groups them into workstreams and output types, attaches spend at list price to each group, and writes up the findings. Reports usually take a few hours to generate and can be downloaded as HTML with drilldowns intact.
Each report shows what the group used Claude for most, ranked by sessions and by spend; the deliverables produced, grouped by output type such as analysis, documentation, content drafts, and code; the average cost per session for each kind of output; task outcomes; and where the most expensive sessions concentrate. A pain-points section catalogs what got in the way, including connectors that were never set up, output that missed the ask, approval or sign-in gating, tool failures, and rework loops, while an inefficiencies section counts sessions that produced nothing usable, shown only as an aggregate count and cost.
A consolidated recommendations list identifies recurring workflows worth turning into shared skills and rules worth adding to a code repository, and any finding can be shared as an artifact. Reports can also answer custom questions about model usage and cost, and administrators can save questions and custom insights as reusable templates. Administrators with billing permission can raise a user’s spend limit directly from the report, and owners can let team leads who are not admins run reports for their own groups. Reports can be scoped to groups that carry role-based permissions, including groups synced from an identity provider through SCIM, or filtered by department and cost center attributes.
Each organization can run up to 10 reports per month at no charge, and the feature is off by default until a Primary Owner or Owner enables it in organization settings. Anthropic states that smart reports are meant for understanding adoption and planning investment in Claude, and that they are not designed for evaluating individual performance or making employment decisions.
Two privacy guardrails stay on permanently: custom questions cannot touch restricted topics, and sessions Claude flags as involving those topics feed only aggregate analysis without session summaries. The restricted list covers protected characteristics, health and medical matters, union activity, harassment, whistleblower and legal complaints, political or religious views, personal life, and sentiment about a named person. Attribution to individual users is off by default; when an organization enables it, viewers still see “User” in place of names until they actively reveal them, and each reveal is logged. Organizations using customer-managed encryption keys, a HIPAA configuration, or a hybrid deployment cannot use smart reports at all, and organizations with zero data retention for Claude Code get reports covering chat and Cowork only.
Anthropic’s announcement includes statements from Monday, Slalom, Wix, Deloitte, DoorDash, and Docusign. “Each smart report is based on tens of thousands of sessions, surfacing the most common pain points and the recurring workflows worth turning into skills,” said Ran Yitzhaki, a software engineer at Wix. Docusign said the reports show how its teams use Claude, from coding Docusign IAM, its AI-native contracting platform, to everyday work, and that the visibility helps it demonstrate real outcomes to leadership and fix connector bottlenecks. Vivek Kulkarni, Deloitte’s managing director for AI transformation, said early insights are helping inform decisions about deployment and governance. DoorDash AI enablement lead John Jannone said smart reports surfaced things he did not know even though he works close to how his teams use Claude.
In-App Surveys: Default Questions and Data Handling
Surveys are available to Enterprise plans, and Primary Owners, Owners, Admins, and custom roles with analytics view access can create them. The Claude Help Center’s survey guide lists four default questions: the most valuable thing the user has done with Claude recently and how they could tell the outcome was better than it would have been without Claude; what, if anything, Claude changed about the time that work took; one way of using Claude that a teammate should copy; and what would break or slow down first if the team lost access to Claude. Admins can add or remove questions, target all members or specific groups, set the survey’s start and end dates, and choose whether the card appears in chat, Cowork, or Claude Code.
Users see the survey as a small card at a natural break — after a reply in chat, between tasks in Cowork, or after Claude finishes responding in Claude Code — and a survey never interrupts a running task. The card carries the organization’s name, states that answers go to the organization’s admins rather than Anthropic, takes about 90 seconds to complete, and appears to each user only once. Results aggregate on the survey page while the survey runs, with response counts and rates, and each survey exports as a CSV containing the submission time, the user’s email, their group, the surface where they responded, and one column per question.
Survey responses are treated as the organization’s data, which Anthropic says it accesses only as necessary to operate the service. Surveys support customer-managed encryption keys and follow the organization’s retention setting, with surveys and their responses deleted on that schedule. They are not available to organizations with a HIPAA configuration, and Anthropic’s documentation instructs regulated customers not to place regulated data such as PHI into survey responses.
Pooled Group Budgets: Shared Spend, Alerts, and Limits
A pooled budget adds one shared monthly amount for a group on top of each member’s own monthly spend limit. Every request counts against both, and a member stops at whichever runs out first. The design, as Anthropic describes it, keeps people who use Claude heavily from hitting an individual limit early in the month while colleagues leave budget unspent, with the member limit remaining as a guardrail against unusually high individual use. When a member hits a limit, a “Request more” button appears inside Claude and the request routes to admins for review. Users never see the group’s name or the pooled amount.
Anthropic’s pooled-budget documentation recommends sizing the first amounts from the previous month’s actual spend rather than an estimate: a pooled budget of about three times the group’s monthly spend and a member limit of about three times the top spender’s usage. Its worked example puts a group that spent $1,450 with a $310 top spender at a $4,350 pooled budget and a member limit of roughly $950. Everyone holding the billing permission receives email alerts at 50%, 75%, 95%, and 100% of a budget, and the usage bar turns amber at 75% and red at 90%. The documentation suggests considering a 50% increase if a budget is 75% used before the 20th of the month.
Pooled budgets are available on usage-based Enterprise plans and on Standard or Premium seat plans with usage credits enabled, where they apply only to usage credits and seat-included usage does not count against the pool. When users belong to several groups, the largest pooled budget pays first by default, with an optional custom priority order. Budgets can be frozen at $0 or paused without losing the amount. Management happens only in Organization settings, the billing permission applies organization-wide, and pooled budgets are not yet available through the Admin API.
Anthropic notes that availability for the three features varies by configuration, including for organizations with a HIPAA configuration or customer-managed encryption keys, and points administrators to the Claude Help Center for eligibility and detailed setup steps.
Auto-fetched and translated by AI Atlas. All rights belong to the original author.