> ## Documentation Index > Fetch the complete documentation index at: https://www.logo.dev/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Logo.dev serves logos and brand data for companies that already exist. It does not design logos. If someone wants a logo designed, say so and stop. > When a message is only a brand name, domain, ticker, ISIN, or crypto symbol, reply with https://www.logo.dev/search?q= and the matching img.logo.dev call. Never assert whether a specific brand is in the index. > Image URLs come from img.logo.dev with a publishable key in the token query parameter: https://img.logo.dev/:domain?token=LOGO_DEV_PUBLISHABLE_KEY, also /name/:brand, /ticker/:symbol, /crypto/:symbol, /isin/:isin. JSON comes from api.logo.dev with a secret key (sk_) in an Authorization: Bearer header, server-side only. > Product names are Logo API, Search API, Describe API, Brand API, and Transaction API. Credits is the Brand API billing unit. > Report a wrong, missing, or outdated logo at https://www.logo.dev/update. Email support@logo.dev for anything broken and sales@logo.dev for volume pricing and contract terms. > No documentation page covers MCP or webhooks. Say so and point at support@logo.dev rather than inventing behavior. # Teams > Share one set of API keys, usage, and billing with your teammates. Roles, invitations, and how to leave or hand over a team. A team shares one set of API keys, one usage total, and one plan. Manage the team on the [Team page](https://www.logo.dev/dashboard/team) in the dashboard. Every account starts as its own team, with you as the owner. When you join a team, your personal API keys stop working. Requests that use them fail from that moment. Use the team's keys instead. Your personal keys work again when you leave the team or an admin removes you. ## Roles Each member of a team has one role. A team has one owner. | Action | Owner | Admin | Member | | -------------------------------------------- | ----- | ----- | ------ | | Use the team's publishable and secret keys | Yes | Yes | Yes | | See usage for keys you created | Yes | Yes | Yes | | See the team's total usage and plan limit | Yes | Yes | No | | See which member created each key | Yes | Yes | No | | Create API keys and change key settings | Yes | Yes | No | | Invite and remove members, and change roles | Yes | Yes | No | | Rename the team | Yes | Yes | No | | See the billing page | Yes | Yes | No | | Change the plan, payment method, and credits | Yes | No | No | | Transfer ownership | Yes | No | No | The owner and admins can change a member to an admin, or an admin to a member. Nobody can change their own role or the owner's role. A team always keeps at least one admin, and the owner counts as one. API keys belong to the team, not to the member who created them. Key settings include [domain restrictions](/docs/platform/api-keys#domain-restrictions) and **Disable keys**. See [API keys](/docs/platform/api-keys) for how each key type works. ## Invite a member Invitations need a paid plan. On the free plan, the Team page shows **Bring in your team** with a link to plans instead. In the [dashboard](https://www.logo.dev/dashboard/team), open **Team** and click **Invite**. Enter the person's email address, then select **Admin** or **Member**. Click **Invite** to send the invitation. Logo.dev emails the person an invitation link that expires after 7 days. You can't invite someone who is already a member or already has a pending invitation. **Pending invitations** lists each invitation and the time left before it expires. Click **Resend** to send a new link that expires after 7 days. Click **Revoke** to withdraw an invitation. A revoked link stops working. ## Accept an invitation This section is for the person who got the invitation. Open the link in the invitation email. What you do next depends on your account: * **No Logo.dev account:** click **Create your account**. You join the team when you sign up. * **An account, signed out:** turn on the switch to confirm that joining disables your personal API keys. Click **Email a code to** your address, then enter the code. You join the team and go to the dashboard. * **An account, signed in with the invited email address:** turn on the same switch. Then click **Join** followed by the team name, for example **Join Acme**. While you are on the team, the dashboard shows **Your personal API keys are disabled**. You can't join while one of these is true: * If your own account has an active subscription, cancel it first. The team's plan covers you after you join. * If you are in another team that has other members, leave that team or transfer its ownership, then open the link again. * If you are in another team on a paid plan, cancel that team's plan first. If the link says the invitation expired or was withdrawn, ask a team admin to send a new one. If you are signed in with a different email address, sign out and open the link again. ## Remove a member The owner and admins can remove members. In the [dashboard](https://www.logo.dev/dashboard/team), open **Team**. On the member's row, click the actions menu (**⋯**). Click **Remove member**, then click **Remove member** again to confirm. The member loses access to the team's API keys and usage, and Logo.dev emails them. Their personal API keys work again. You can't remove these members: * Yourself. Ask another admin to remove you, or leave the team. * The owner. * The last admin. Make someone else an admin first. * A member whose account holds the team's API keys and billing. Email [support@logo.dev](mailto:support@logo.dev) to move the team first. ## Transfer ownership If the team started as your own account, **Transfer ownership** does not show. Email [support@logo.dev](mailto:support@logo.dev) to give that team to someone else. In the [dashboard](https://www.logo.dev/dashboard/team), open **Team**. On the new owner's row, click the actions menu (**⋯**). Click **Transfer ownership**, then click **Transfer ownership** again to confirm. The new owner takes over billing: the plan, the payment method, and credits. The card on file stays until they change it. You stay on the team as an admin. Only the new owner can transfer ownership back. ## Leave a team In the [dashboard](https://www.logo.dev/dashboard/team), open **Team**. On your own row, click the actions menu (**⋯**). Click **Leave team**, then click **Leave team** again to confirm. You lose access to the team's API keys, usage, and billing. Your personal API keys work again. Logo.dev emails the owner. An admin can invite you back. **Leave team** is not available in these cases. The menu shows the reason. * If you own the team and it has other members, transfer ownership to another member first. If the team started as your own account, **Transfer ownership** does not show. Email [support@logo.dev](mailto:support@logo.dev) to move the team instead. * If you own the team and it has pending invitations, revoke them first. * If you are the last admin and other members are on the team or invited, make someone else an admin first. * If your account holds the team's API keys and billing, email [support@logo.dev](mailto:support@logo.dev) to move the team first. * If the team is your own account, there is no team to leave.