Rules

These rules hold for every agent, whichever client it runs in and whichever way it connects. There are two ways:

• Signing in, for a person using an agent: you sign in to poddub.com with your own poddub account, choose the organization, and allow the agent with the most it may do, never above your own role. See Connect claude.ai and Connect Claude Code.
• A key, for work that runs without a person: an owner makes it in the app. See Keys.

Either way, an agent never does more than its person can.

1. ConsentCopy Anchor Link

An agent acts as its person, the one who signed it in or whose key it holds, and that person's own acceptance of the current list of providers poddub works with covers what the agent does. Nothing else covers it. Starting an episode and having poddub write a script or a line again are refused with consent_required until that person has accepted the current list, in the app. An agent cannot accept it for them.

2. ApprovalCopy Anchor Link

Approval stays with a person. An agent may read a script in review, edit it and have poddub write it again, and may retry and publish an episode within its person's role. It does not approve, because approving spends the organization's minutes and starts the audio.

An owner may allow agents to approve in their organization. It is off until they turn it on, and the app records who turned it on and when. While it is off, an agent's approval is refused and names the episode, so the person can open it in the app.

3. AttributionCopy Anchor Link

What an agent changes in a script, and an approval it makes, are recorded in the episode's history under its person. For an agent with a key, the app names the person and the key, such as "Approved by Ada through Release bot". For an agent connected by signing in, the app names the person.

4. What an agent never doesCopy Anchor Link

An agent never:

• manages people, invitations, roles or teams;
• buys, changes or restores a subscription;
• deletes a source, an episode, an organization or an account;
• puts an episode on the public show or takes one back, unpublishes an episode, or narrows who hears it;
• accepts or withdraws consent;
• reads or replaces a private feed link, or sees who listens;
• creates, reads or revokes a key;
• reaches anything only poddub's own operators can do.

5. Connections and keysCopy Anchor Link

A connection you make by signing in is yours, works in one organization, and is capped at the role you chose when you allowed it. It stops at once when you end it on poddub.com/connections, when you leave or are removed from the organization, when the organization is deleted, and when your poddub account is deleted. Each person sees and ends their own connections there, and an owner sees and ends everyone's in their organization.

A key belongs to one person, works in one organization, is capped at a role, and expires. It stops working when it expires, when it is revoked, when its person leaves or is removed from the organization or no longer has the role a tool needs, when the organization is deleted, and when its person's poddub account is deleted. An owner can see and revoke every key made in their organization. See Keys.

6. RateCopy Anchor Link

An agent's calls count against its own limit, its key's or its connection's, and against its person's. An agent has no allowance of its own: the minutes and script generations are the organization's, whoever spends them. See Limits.