创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

Amp 推出工作区所有的服务账号

AI 总结

Amp 已推出服务账号。这是一种不绑定单一用户、由工作区所有的账号,由工作区管理员创建,并拥有独立的 API 密钥和第三方凭据。由服务账号创建的线程可由其他工作区成员查看和发送消息。该账号适用于团队共同负责的工作,包括拉取请求审查、文档维护,以及用于启动 Amp 线程的 CI 任务。由于工作区任何成员都可以使用服务账号的线程,因此管理员只应分配所有工作区成员都适合获得的凭据。

深度见解

服务账号使团队即使在原配置人员暂时无法工作时,仍能访问共享工作流和自动化线程,同时为程序化工作提供具有独立 API 密钥和凭据的工作区级身份。

Amp now has Service Accounts. A service account is a workspace-owned account that's not tied to a single user.

Service accounts are created by workspace admins. They have their own API keys and third-party credentials.

Each thread created under a service account can be viewed by other members of the workspace. These threads are multiplayer too, so workspace members can send messages in them.

Since anyone in the workspace can drive a service account's threads, make sure to only assign credentials to it that you would be happy bestowing on all workspace members.

When to Use Service Accounts

Service accounts fit any work that belongs to the team rather than to one person. For example, threads with automations that workspace members want to have access to, even if the person who set them up is on vacation.

#Amp#Amp Service Accounts#Puck#GitHub

原文约 2 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。