Today chat sessions belong to the organisation and every /api/chat route is admin-only. A conversation belongs to the person who started it: only they can list, read, continue, rename or delete it. Each turn acts as that person: the agent's tool calls, judgement and approvals use their principal and role, so an admin's chat has admin access and an operator's chat has operator access, never more. Done when an operator can chat on the binary, can't see or touch another person's conversation, and a tool call an operator isn't allowed is refused in their chat but allowed in an admin's. Part of #2023 and #2017.
Today chat sessions belong to the organisation and every /api/chat route is admin-only. A conversation belongs to the person who started it: only they can list, read, continue, rename or delete it. Each turn acts as that person: the agent's tool calls, judgement and approvals use their principal and role, so an admin's chat has admin access and an operator's chat has operator access, never more. Done when an operator can chat on the binary, can't see or touch another person's conversation, and a tool call an operator isn't allowed is refused in their chat but allowed in an admin's. Part of #2023 and #2017.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Today chat sessions belong to the organisation and every /api/chat route is admin-only. A conversation belongs to the person who started it: only they can list, read, continue, rename or delete it. Each turn acts as that person: the agent's tool calls, judgement and approvals use their principal and role, so an admin's chat has admin access and an operator's chat has operator access, never more. Done when an operator can chat on the binary, can't see or touch another person's conversation, and a tool call an operator isn't allowed is refused in their chat but allowed in an admin's. Part of #2023 and #2017.