--- title: "Create Teams" slug: "create-teams" updated: 2026-02-12T22:00:28Z published: 2026-02-12T22:00:28Z stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://resource.payrix.com/llms.txt > Use this file to discover all available pages before exploring further. # Create Teams You can create teams from the **Teams** page in the portal. Each user added as a member within a team can share access with the other members, based on the **Allowed Access** assigned. Team members can belong to either the merchant or partner access levels, or in some cases, both. ## Create a Team To create a new Team: 1. Click the **Plus**icon next to Users in the left navigation panel to open a dropdown menu. 2. Click **Teams**in the Users dropdown menu to open the Teams page. 3. Click **ADD TEAM** in the upper-right section of the page to open the Create Team dialog. 4. Enter a name for your team. 5. (Optional) Enter a description for the team. 6. Click **Add**to finish creating your new team. Your new Team is created and is displayed on the **Teams** page table. From here, you can begin enrolling users to activate and apply your Team permissions. ## Add Users to a Team To add users to your team: 1. Select the new team listed in the Teams table to open the Team Profile page. 2. Click **Users**on the left side of the page to open the Users tab. 3. Click **ADD USERS**in the upper-right corner of the page to open the Add Users dialog. 4. Enter the username of the user into the search bar at the top of the dialog to search by name, or scroll down the list of usernames. 5. Click the **checkmark**icon to select the user. 6. (Optional) Select **Allowed Access** to grant all access capabilities for the team. > [!WARNING] > Important! > > **Allowed Access** levels within a Team can extend a user’s access beyond their preset User Roles when accessing other merchant or partner accounts in the Team. Ensure that **Allowed Access** levels are assigned carefully to avoid unintended access. 7. Click **Add Users**at the bottom of the dialog to add the users to the team. Each added user is shown on the **Users** tab of the **Team Profile** page. > [!TIP] > Tip > > You can add new merchant users to specific teams after successful boarding by assigning your preferred team to your white-labeled Merchant Signup Form. Contact your Partner Experience Manager for more information. --- ## Examples of Team-Based Access The following sections provide examples of how different business types can use Teams to assign access across multiple merchant accounts. Each scenario demonstrates how specific access levels support the intended responsibilities of users in a Team. ### Configure Owner Access for a Multilocation Franchise Managing multiple locations under a single entity can be a complex yet essential task. For these types of businesses, you can set up a [multilocation merchant structure](/v1/docs/overview-of-users#multilocation-merchant-structure) that enables business owners to organize data, manage operations, and report across separate merchant locations. Imagine a hair salon merchant named HairMaster operates a business with multiple franchise locations accepting payments in-store and online. Each franchise location is onboarded to Payrix Pro as a separate merchant entity. The owner of HairMaster wants to view the transaction and reporting data across all their franchises in one place to reconcile their accounts and track each location’s progress against sales goals. > [!NOTE] > Note > > This example assumes each location’s manager is an admin user for their respective merchant account. These users must be added to the Team because they serve as the link between the Team and each merchant account. To grant the business owner full access to each location’s account: 1. Create a Team called **All Merchant Locations**. 2. When adding users, assign the required **Allowed Access** levels: 1. **Owner:** Assign **Admin** access. 2. **Location Managers:** Assign **None** access. The owner can now log in and view merchant account information for each location in the portal. ### Configure Manager Access for a Multilocation Franchise Imagine you own a fast food business, ChompWay, with five locations, and each location needs its own separate merchant account. As the owner, you want your corporate manager to oversee all five locations, but they only have a user account with one location. > [!NOTE] > **Note** > > This example assumes each location is treated as a separate merchant account, with each location’s manager as its respective admin user. These admin users must be added to the Team because they act as the link between the Team and each merchant account. See [Multilocation Merchant Structure](/v1/docs/overview-of-users#multilocation-merchant-structure) for more information about multilocation structure setups. To grant access: 1. Create a Team called **ChompWay Stores**. 2. When adding users, assign the required **Allowed Access** levels: 1. **Corporate Manager:** Assign **Edit** access. 2. **Location Managers:** Assign **None** access. Even though your corporate manager does not have a direct user account at all five ChompWay locations, their Team membership allows them to view and manage data across all five merchant accounts. Similarly, the location managers are not able to view or modify data on the corporate manager’s merchant account or the other locations’ merchant accounts. ### Configure Payment Processing Support Access Imagine you are the payment services provider, *PaySprocket* Solutions, acting as the partner over a portfolio of more than 100 merchants using Payrix Pro for payment processing. Each merchant has its own account, but *PaySprocket* wants direct and secure access for its support agents to assist with reporting and other portal features. As the support manager, you want a way to make sure your support group has the appropriate access to help merchants troubleshoot issues. To grant access: 1. Create a Team called **PaySprocket Support**. 2. Assign the Allowed Access levels to support team members and the merchant's employees, as follows: 1. **Support Manager:** Assign **Edit** access. 2. **Support Specialists:** Assign **View** access. 3. **Merchants' Employees:** Assign **None** access. *PaySprocket* Support can now log in and view merchant accounts within the Team with the appropriate access for support specialists to review a merchant’s issue. The support manager can make authorized changes as needed to resolve the issue without full administrative access to any merchant account. The movement of funds between a customer (cardholder or eCheck account holder) and a merchant to purchase a good or service.