# Adding and Managing Team Members

How to access on Fynd Commerce 
Commerce Panel → Company → Team

## Introduction

Use this section to manage your team, invite individuals and add to your staff. You can flexibly grant your staff with company-level access to its team, products, orders and much more. Moreover, you can also set their access to one or more sales channels, including marketplaces and resellers.

### Main Screen

![QG1](https://cdn.pixelbin.io/v2/doc/original/searchlight/platform-panel/Updates-to-docs/Documentation-update/Team/fig-1-Main-page.png)

center
em
Figure 1: Team - Main Screen
br
In this document, you will learn more about:

* [Invite Users](#invite-users)
* [Roles](#roles)
* [Partner Invites](#partner-invites)


## Invite Users

1. Click on **Invite**.
2. You can type an email address or mobile number and press the `Enter` key to add more. Next, click the **Search** button.
![QG1](https://cdn.pixelbin.io/doc/original/searchlight/platform-panel/team/userinvite.png)
Figure 2: Invite Users by email/number

3. You will get the following list:
  * Unregistered - Users who are being invited.
  * Pending - Users who have been sent an invite but are yet to accept it.
  * Registered - Users who have registered using the invite link, but are yet to be added as staff.
  * Staff - Users who have been added as a staff member.
![QG1](https://cdn.pixelbin.io/doc/original/searchlight/platform-panel/team/userlist.png)
Figure 3: List of Users

As you can see in the list, 3 out of 4 users are unregistered and 1 of them is already a staff. You can individually invite users by clicking **Send Invite** or invite them all at once using **Invite All**.
4. Assigning Roles to Staff: When inviting a new staff member or updating an existing one, you can assign a role using one of the following options under Role Details:
  * **Full Access**: Grants access to all sections and features.
  * **Existing Role**: Allows you to assign a predefined role that already contains a fixed set of permissions created by your team. Click the dropdown under Search existing role, use the search bar to find the role, and select it to auto-apply all associated permissions. [Click here to learn how to create a role](#roles).
  * **Custom Role**: Enables you to define specific permissions manually.
Only users with Admin access can assign roles to others using the Existing Role dropdown during staff invitation or modification.
Custom roles assigned through this method are created and managed from the Roles section in Company > Team > Roles.
Each permission listed under **Company Access** form enables the merchant to control what areas of the platform a team member can access.
  1. **Profiles**: This permission allows members to access and manage company profiles. They can create, configure, and customize the brands and selling locations associated with the company.
  2. **Extensions**: Members can extend the application’s capabilities by integrating additional features or third-party tools.
  3. **Settings**: This permission grants access to configure and customize application features across multiple touchpoints.
  4. **Analytics**: Members with this permission can get real-time insights into a product's lifecycle. They can view detailed reports and analytics about products, including the option to download graphs and data for deeper analysis.
  5. **Logistics**: This permission enables members to manage delivery and shipment logistics. This includes handling setups for various delivery partners and coordinating self-shipping services for the business.
  6. **Orders**: This permission provides access to the history of all customer orders placed using the platform. Members can view, manage, and track customer orders, enabling smooth order processing.
  7. **Teams**: With this permission, members can manage team members and configurations. It allows you to add individuals to your staff, manage the company's internal team structure, and configure different sales channels.
  8. **Developers**: Members gain access to platform APIs and SDKs, which allow them to build systems, develop applications, and integrate the e-commerce platform with other tools.
  9. **Audit Trail**: This permission gives access to activity logs that track and display the changes made by platform users. It’s useful for tracking modifications, ensuring compliance, and maintaining oversight of platform usage.
  10. **Product**: This permission allows users to manage and update products and their inventories within the platform.
    1. **Inventory**: This permission grants the ability to manage product inventory. They can view, create, update, and delete stock levels for the items listed in the catalog, ensuring inventory accuracy.
    2. **Catalog**: This permission allows members to manage the product catalog itself. They can create, update, and delete products, manage product categories, and ensure the catalog reflects the company’s offerings accurately.
5. **Order Role** is used to decide the permissions that the staff would have in the Order Management System (OMS).
![QG1](https://cdn.pixelbin.io/doc/original/searchlight/platform-panel/team/6.png)
Figure 5: Selecting Order Role

  * **Full Access**: Staff can perform all kinds of operations (process, cancel, etc.) on all the orders in the company.
  * **Store Manager**: Staff having store manager role can view, confirm, cancel, generate invoice, generate manifest, and accept an order return. It's important to note that a staff manager won't be able to process an order return.
  * **Customer Care**: Those with customer care as their role can view the orders, cancel orders, trigger an order return, and update bank details in case of a return. Staff won't be able to place or process an order.
  * **Read-Only**: Those with read-only access will be able to perform only those actions that do not alter the system. This includes viewing the order and downloading the invoice/manifest. Staff with read-only permissions will not be able to place a phone call to a customer via Order Management System.
6. Similar to **Order Role**, the **Store Access** option is also in strict accordance with the Order Management System. In short, staff can view or edit the orders of only those stores which are defined here.
![QG1](https://cdn.pixelbin.io/doc/original/searchlight/platform-panel/team/6a.png)
Figure 6: Granting Store Access

  * **All Stores**: Staff can view/edit the orders of all the selling locations created in the company.
  * **Specific Stores**: Staff can view/edit the orders of few selected stores in the company.
Use the **Sales Access** checkbox to grant the staff the permission to create sales channels.
7. Select the sales channel and its sections to which a staff will get access. In this example, we have 2 sales channels *fancywardrobe* and *mamba*. Using the **Select Role** drop-down, you can grant permissions to access the sections within the sales channel.
![QG1](https://cdn.pixelbin.io/doc/original/searchlight/platform-panel/Updates-to-docs/Documentation-update/Teams/fig-7a-store-access.png)
Figure 7a: Selecting Sales-level Role

The below chart depicts the permissions that are granted to the staff w.r.t the role.
![QG1](https://cdn.pixelbin.io/doc/original/searchlight/platform-panel/team/permission_chart.png)
Figure 7b: Role & Permission Chart

8. You can also click on **Edit Store Access** to edit stores while sending the invite. Select the store from the dropdown and click **ok**.
![QG1](https://cdn.pixelbin.io/v2/doc/original/searchlight/themes/astra/11.png)
Figure 8: Manage Application Stores

9. You can grant your staff the permission to manage marketplaces, such as Flipkart, Amazon, Myntra, AJIO, and many more using the **Marketplaces** checkbox.
![QG1](https://cdn.pixelbin.io/doc/original/searchlight/platform-panel/team/8.png)
Figure 9: Other Permissions

**Other Sellers** option allows your staff to monitor the companies and selling locations that are reselling products through your inventory (a.k.a franchise mode).
You can also allow your staff to view and manage the billings and payments. Moreover, you may write  a custom message that will appear in the invite message.
10. Click **Send Invite** and wait for the users to accept the invite and register in the application.
11. Add the users who have accepted the invite as a staff.
![QG1](https://cdn.pixelbin.io/doc/original/searchlight/platform-panel/team/registered.png)
Figure 10: Adding As Staff

12. Confirm the inclusion of the user.
![QG1](https://cdn.pixelbin.io/doc/original/searchlight/platform-panel/team/member.png)
Figure 11: List Of Staff Members



## Roles

If your organization maintains a list of members, your members need not register separately on Fynd Commerce . Instead, they can use the **Login as Organization** option. Read [SAML SSO](/commerce/docs/manage-company/saml-sso) for more details. The **Roles** section is only for creating a role and deciding the permissions that will be granted to the users who log in via SSO.

Let's assume, you want to choose the permissions users would get if they login via Azure AD.

1. On the **Team** page, go to **Roles**.
![QG1](https://cdn.pixelbin.io/v2/doc/original/searchlight/platform-panel/Updates-to-docs/Documentation-update/Team/fig-11-roles-section.png)
Figure 12: Roles Section

2. Click **Create Role**.
![QG1](https://cdn.pixelbin.io/doc/original/searchlight/platform-panel/team/4.png)
Figure 13: Creating A Role

3. Choose the permissions.
![QG1](https://cdn.pixelbin.io/doc/original/searchlight/platform-panel/Updates-to-docs/Documentation-update/Teams/fig-13-roles.png)
Figure 14: Giving Permissions

4. Click **Save**.
![QG1](https://cdn.pixelbin.io/doc/original/searchlight/platform-panel/Updates-to-docs/Documentation-update/Teams/fig-14-save-roles.png)
Figure 15: Role Creation Successful



For more details on how the role is used, refer our [Azure AD](/commerce/docs/manage-company/saml-sso#azure-ad) documentation.

## Partner Invites

Here you can see the pending, accepted and rejected invites.

1. On the **Team** page, go to **Partner Invites**.


![QG1](https://cdn.pixelbin.io/v2/doc/original/searchlight/platform-panel/Updates-to-docs/Documentation-update/Team/partner-invites/fig-1.png)

center
em
Figure 1: Partner Invites 
br
1. You can see the list of pending invites.


![QG1](https://cdn.pixelbin.io/v2/doc/original/searchlight/platform-panel/Updates-to-docs/Documentation-update/Team/partner-invites/fig-2.png)

center
em
Figure 2: Pending Invite
br
1. You can click on the invite and either accept or reject the invite. Let's click **Accept** for this invite.


![QG1](https://cdn.pixelbin.io/v2/doc/original/searchlight/platform-panel/Updates-to-docs/Documentation-update/Team/partner-invites/fig-3.png)

center
em
Figure 3: Accept Invite
br
1. Go to **Accepted Invites**, you can see the list of users that have been accepted.


![QG1](https://cdn.pixelbin.io/v2/doc/original/searchlight/platform-panel/Updates-to-docs/Documentation-update/Team/partner-invites/fig-4.png)

center
em
Figure 4: Accepted Invites
br
1. Similarly you can reject invites. Let's select a pending invite and select **Reject**.


![QG1](https://cdn.pixelbin.io/v2/doc/original/searchlight/platform-panel/Updates-to-docs/Documentation-update/Team/partner-invites/fig-5.png)

center
em
Figure 5: Reject Invite
br
1. Go to the **Rejected Invites** page to see the rejected user.


![QG1](https://cdn.pixelbin.io/v2/doc/original/searchlight/platform-panel/Updates-to-docs/Documentation-update/Team/partner-invites/fig-6.png)

center
em
Figure 6: Rejected Invites
br