# Working With Clients

{% hint style="info" %}
You would need a PRO or Business Plan to use these workflows
{% endhint %}

This article is a recommendation on how to provide managed services for your clients. Blynk defines *managed service* as a workflow where your company acts as an administrator and manually sets up every client. This is an opposite to self-serve workflow (available in Business Plan only) where users can create new account in your app using their email address and then add devices by themselves. 

Overall, all you need to do is to create an organizational hierarchy that works for your business. Our recommendation is to use [Organizations](https://docs.blynk.io/en/blynk.console/organizations) feature and build a structure similar to this:  

```
Your Company Organization (Root Organization in Business Plan)
└ My Clients (this is an organization/group where all of your clients will be kept)
   ├ Client 1 Organization
   ├ Client 2 Organization
   ├ ...
   └ Client N Organization
```

{% hint style="info" %}
For Business Plan users. If you don't plan to allow users regiser by themselves, you can use **Clients** Organization (available out-of-the-box) and keep all of your clients there.
{% endhint %}

We highly recommend placing clients under one Organization (e.g. *My clients*) because: 

1. You can set up Roles and Permissions for this organization and apply these settings to all organization down the tree. Even though you can set up roles and permissions individually for any client, organizing it this way will save you a lot of time in the future.
2. You can set up which columns to show in the Device List in Console and apply it to all organizations below.
3. You can give access to My Clients Organization to your staff and control how what they can do there (using Roles and Permissions). 

Get yourself familiar with these features to manage clients more efficiently: 

* [Creating a sub-organization](https://docs.blynk.io/en/blynk.console/organizations/create-a-sub-organization) and [inviting customers](https://docs.blynk.io/en/blynk.console/organizations/browse-and-edit-a-sub-organization#invite-users-to-a-sub-organization)
* Navigating ([switching](https://docs.blynk.io/en/blynk.console/organizations/browse-and-edit-a-sub-organization#switching-to-a-sub-organization)) between organizations (in mobile app and console)
* Working with [Roles and Permissions](https://docs.blynk.io/en/blynk.console/settings/access) 
* [Transferring Organizations](https://docs.blynk.io/en/blynk.console/organizations/browse-and-edit-a-sub-organization#transfer-a-sub-organization)
* [Transferring Users](https://docs.blynk.io/en/blynk.console/organizations/browse-and-edit-a-sub-organization#how-to-transfer-a-user-to-another-organization)
* [Transferring Devices](https://docs.blynk.io/en/blynk.console/devices/actions-with-devices#device-transfer) 


---

# 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.blynk.io/en/commercial-use/working-with-clients-pro-business-plan.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.