{"section":"tutorials","requestedLocale":"en","requestedSlug":"buyer-organization-members","locale":"en","slug":"buyer-organization-members","path":"docs/en/tutorials/b2b/b2b-buyer-portal/buyer-organization-members.md","branch":"main","content":"In a B2B buyer organization, members are the people who interact with the store on behalf of the organization. Their actions are defined by roles and permissions assigned to them, as well as by how the organization uses **recipients** and **buyer information**. This article describes the types of members and related concepts to explain the actions different users can perform in your organization.\n\n> ⚠️ This feature is only available for stores using B2B Buyer Portal, which is currently available to selected accounts.\n\n## Storefront roles\n\nRoles define what each user can do in the store, including managing the organization account. Each role has a set of permissions. When you assign one or more roles to a user, they acquire the combined capabilities of those roles. Applying permissions in the store allows restricting users to view and edit approved resources only.\n\nThe table below summarizes the main roles and their functions:\n\n| Role                           | Purpose                                                                                                                                                                                               |\n| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| **Organizational unit admin**  | Full control over the organizational unit: manages organization and contract, users, buying policies, budgets, accounting fields, quotes, and organization hierarchy. |\n| **Super buyer admin**          | Can manage all organizational units at the root level of the organization, beyond the limits of each unit.                                                                            |\n| **Buyer**                      | Can place orders in the store.                                                                                                                                                        |\n| **Order approver**             | Can approve or reject orders following the configured approval flows.                                                                                                                 |\n| **Order modifier**             | Can use the order change feature on orders they have access to.                                                                                                                       |\n| **Address manager**            | Can add addresses during checkout, save them to the contract or organizational unit, update address information at checkout, and view saved addresses.                                |\n| **Buyer organization manager** | Can view all orders for their organizational unit, manage authentication settings, view payment cards, and view addresses.                                                            |\n| **Contract manager**           | Can view orders placed under the contract assigned to them.                                                                                                                           |\n| **Contract viewer**            | Can view saved addresses (read-only).                                                                                                                              |\n| **Buying Policy Manager** | Can create, edit, and delete purchase policies and approval workflows, and view purchase policies. |\n| **Budget Manager** | Can create, edit, allocate, and delete budgets, and view budget details, allocations, limits, and spending history. |\n| **Accounting Fields Manager** | Can create, edit, and delete accounting fields. |\n| **Quote Manager** | Can create, edit, and delete quotes. |\n| **Personal card user**         | Can use a new credit card not saved in the contract by default at checkout.                                                                                                           |\n\n> ℹ️ Learn more about Storefront roles and resources in the developer guide [Storefront Roles](https://developers.vtex.com/docs/guides/storefront-roles).\n\n## Recipients\n\n**Recipients** or **Contacts** are the people who can be selected as order recipients — the people who'll receive the shipment. The order contact may be different from the user who placed the order. When placing an order, the buyer can choose the contact (recipient) the order is for.\n\nRecipient information is managed at the organization level. Contacts can be linked to addresses so that, when selecting a shipping address, the user can choose from the contacts associated with that address. This keeps recipient information centralized and reusable between orders.\n\nFor technical details on how to create, update, and integrate recipients via APIs, see the [B2B Recipients API](https://developers.vtex.com/docs/api-reference/b2b-recipients-api).\n\n## Buyers\n\n**Buyers** are users who can place orders and are associated with the buyer organization. Buyer details identify and describe the users in the store and in order flows, such as checkout and order history.\n\nBuyer details are used by the store to identify who is placing the order and to apply the correct permissions, contracts, and policies.\n\nTo learn how to create and manage buyer details, see the [B2B Buyer Details API](https://developers.vtex.com/docs/api-reference/b2b-buyer-data-api)."}