# Business Unit

In SimplifyQA, the Business Unit is a logical grouping feature that helps organizations manage and segregate their testing assets, users, and project activities based on different departments, clients, or functional divisions. It acts as the top-level container under which multiple projects and user roles are organized.

This feature is particularly useful for companies with multiple clients, departments, or business streams who wish to maintain data privacy, better access control, and operational clarity.

### Key Features of Business Units

1. **Segregation of Projects**
   * Each business unit can have its own set of projects, completely isolated from other units.
   * Projects created under a business unit are only visible to users associated with that unit.
2. **User Management and Access Control**
   * Admins can assign users to specific business units.
   * Role-based access within a business unit ensures that users only see and manage what's relevant to them.
3. **Data Isolation**
   * Test cases, defects, requirements, and execution plans are isolated per business unit.
4. **Analytics and Reporting**
   * Reports can be generated at the business unit level for more targeted insights.
   * Helps in evaluating performance and test coverage for each business division.

### Creating a Business Unit

To create a new Business Unit in SimplifyQA, follow these steps:

1. **Login as Admin**\
   Only Admin users have the rights to create and manage business units.
2. **Navigate to Admin Settings**
   * Click on your profile or settings icon in the top-right corner.
   * Select Admin Panel or Settings from the dropdown.
3. **Go to 'Business Unit' Section**
   * In the left panel of the Admin Panel, select Business Unit.
4. **Create New Unit**
   * Click on Create New Business Unit button.
   * Fill in the required details:
     * Business Unit Name (e.g., Retail Banking, Healthcare Division, Client-X)
     * Description (optional, but helpful for context)
5. **Save**
   * Click Save to successfully create the business unit.

<figure><img src="/files/zw2AvwKpfPkKgrTS9Wsi" alt=""><figcaption></figcaption></figure>

### Managing Business Units

* **Edit or Delete a Business Unit**
  * From the list of existing units, click on the View Details icon next to the desired unit.
  * Note: Deleting a business unit will also remove all its associated projects and data. Proceed with caution.
* **Assign Users to a Business Unit**
  * Navigate to the Project section.
  * Select a project and assign them to the appropriate business unit(s).
  * A user can be part of multiple business units but will only have access based on their role in each.

<figure><img src="/files/q53194Zq4Syx0j0P8ktK" alt="" width="460"><figcaption></figcaption></figure>

* **Switch Between Business Units**
  * If a user is part of multiple units, they can switch units using the dropdown selector typically located at the top of the dashboard.

<figure><img src="/files/S8xf0U6GQUdDi7YBu4IQ" alt="" width="446"><figcaption></figcaption></figure>

### Accessing Business Unit on the Landing Page

Users can view and switch between their assigned Business Units directly from the landing page, provided their role has the appropriate privileges.

**Steps to Enable Business Unit Visibility on Landing Page:**

1. **Go to Project Settings**
   * Navigate to the Project Settings from the top menu or the settings icon.
2. **Access Roles & Privileges**
   * Click on Roles & Privileges.
3. **Select the Respective Role**
   * Choose the role for which you want to enable access (e.g., QA Engineer, Project Manager).
4. **Enable the ‘Show Project’ Privilege**
   * Under the section Project & Release Management, enable the checkbox for “Show Project”.
   * This allows users with that role to view the Business Unit and project details directly on the landing page.
5. **Save Changes**
   * Click **Save** to apply the updated role privileges.

Once this is enabled, users will see a dropdown or listing of available Business Units on their dashboard, making it easier to navigate and access the relevant projects.

### Use Case Scenarios

* **Multiple Clients**:\
  An organization serving different clients can create separate business units for each client to keep their projects, test cases, and reports completely isolated.
* **Department-wise Testing**:\
  If internal QA teams handle testing for various departments like HR, Finance, IT, and Operations, each department can have its own business unit for better organization and visibility.
* **Multi-Domain Projects**:\
  For companies that handle multiple business domains (e.g., Banking, Insurance, Retail), setting up business units per domain can streamline project and user management.
* **Offshore-Onshore Teams**:\
  In a global delivery model, you can create business units for offshore and onshore teams to manage access, reporting, and work ownership.
* **QA Service Providers**:\
  For QA consulting or service companies, business units can be used to create client-specific environments ensuring data privacy and independent project execution.

### Frequently Asked Questions (FAQs)

<details>

<summary>Can a user access multiple business units?</summary>

Yes, a user can be part of multiple business units but must be assigned accordingly by the admin.

</details>

<details>

<summary>Is it possible to restrict visibility of test cases or defects by business unit?</summary>

Yes, all artifacts in SimplifyQA are scoped to their respective business units, ensuring data isolation.

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.simplifyqa.ai/admin-controls-and-configurations/business-unit.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
