Build it in your own project.
Use the same SDK examples as Bird's product pages, then give your coding agent a brief that includes the failure paths you practised.
A brief for your coding agent
# Build with Bird: Account access and permissions Read these current sources before proposing an implementation: - Authentication & API keys: https://bird.com/docs/guides/authentication - Should I use an API key or an OAuth token, and how do I rotate one?: https://bird.com/explained/platform/api-key-or-oauth-token-and-how-do-i-rotate-one - Users, teams & roles: https://bird.com/docs/guides/users-teams-roles ## Task Help me implement Account access and permissions in my project. First inspect the application and identify the relevant server, framework and existing Bird integration. Confirm the exact workflow and supported surface against the linked documentation. Some operations are available only in the dashboard. Do not invent endpoints or derive API contracts from a learning simulation. ## Implementation Use the official Bird SDK or CLI where supported. Keep credentials on the server and request the smallest necessary permissions. Follow the channel's documented test procedure before proposing any external send or production change. Keep request acceptance separate from delivery. For incoming events, verify signatures using the original request body, deduplicate stable identifiers, and apply valid state transitions. Respect recipient preferences and channel requirements. ## Acceptance Show the implementation and relevant tests. Exercise the documented failure paths, invalid signatures and duplicate events where applicable. Explain any dashboard steps or missing prerequisites. Ask for approval before sending to real recipients or changing production.