Connections are scoped to a team
GET /teams/{teamId}/connections lists connections for the authenticated user
in the current team. The result can also include connections shared with the
team and connections granted from another team when the organization-level
Connections sharing setting is enabled. The type filter uses an integration
type, not a native OAuth provider key.
Personal OAuth connections are created for a specific user and team. When you
need a personal connection in another team, select that team (for example, with
--team) and authorize the account there. A connection is not moved when you
change teams; an eligible connection can also be explicitly granted to another
team when organization-level Connections sharing is enabled. For sharing
Connections within a team, see One Builder, Many Users.
Agent Memory follows the team plan and Agent setting
When a team plan includes Memory, newly created Agents have Memory enabled by default. You can disable it for an Agent in Agent Builder → Memory → Disable memory, withPATCH /v2/agents/{agent_id} and
{"agentic_memory_enabled": false}, or with
duvo agents update <agent-id> --disable-agentic-memory.
Disabling Memory stops the Agent from reading or updating its saved files; the
files remain available to view and become available again if Memory is
re-enabled. The Public API can list and read an Agent’s Memory files even when
the per-Agent Memory setting is off. It does not expose an API to delete them;
delete files from the Agent’s Memory tab in the dashboard.
Team names are managed in Team Settings
The Public API exposesGET /teams/{teamId} to read a team, but it does not
expose an endpoint to rename a team. A team Owner or Administrator can rename
the team in the Duvo app under Team Settings → General.