A practical reference for installers acting as service providers: how to structure Omada Central for multiple clients, adopt VIGI cameras and Omada Guard NVRs into the right Organisation, and share access with end users using the TP-Link ID invitation system — without exposing your own credentials.

What is Omada Central?

Omada Central is TP-Link's cloud-based management platform, accessed at omada.tplinkcloud.com. It is the evolution of the Omada Cloud-Based Controller and now supports both networking and surveillance in one portal. It consists of two applications you can enable per Organisation:

• Omada Network Manages Omada networking devices — gateways, switches, and access points. Handles Wi-Fi, VLANs, routing, and site-wide network configuration.
• Omada Guard Manages surveillance devices — VIGI cameras and NVRs. Handles live view, playback, recording, and AI-based detection features.

You can enable one or both applications when creating an Organisation. For a pure surveillance install, you may only need Omada Guard. For a full network + camera deployment, enable both.

Omada Central — Essentials vs Standard

When creating an Organisation, you choose between two tiers. Both are managed from the same portal and the same devices work with either version.

VIGI Cameras & Omada Guard — Key Facts

• VIGI cameras & NVRs TP-Link's dedicated surveillance hardware brand. VIGI cameras and NVRs are adopted directly into Omada Central and managed via the Omada Guard application.
• Third-party cameras Cannot be added directly to Omada Central. They can be connected through a VIGI NVR (ONVIF S support). AI features such as People Counting and Line Crossing Detection require TP-Link hardware and are not available on third-party cameras.
• VIGI App / VIGI VMS Legacy VIGI management applications. These are legacy applications for standalone VIGI device management. For cloud-based management of VIGI cameras and NVRs alongside your network devices, use Omada Central instead.

Setting Up Your Multi-Client Cloud Structure

Step 1 — Create an Organisation

Each client should have their own separate Organisation. This provides complete isolation of devices, users, and permissions between clients.

1. 1 Log in to omada.tplinkcloud.com with your installer TP-Link ID. Your account automatically becomes the Owner of any Organisation you create.
2. 2 Click + Add Organization on the dashboard.
3. 3 Select Essentials or Standard according to the client's requirements, then click Next.
4. 4 Enter the Organisation Name, Country/Region, and Time Zone. Under Select Applications, choose Omada Network, Omada Guard, or both. Click Done.

Step 2 — Create Sites within the Organisation

TP-Link's official guidance is to create one Site per LAN. All devices within the same local network should belong to the same Site. Separate physical locations = separate Sites.

1. 1 Open the Organisation and navigate to Admin > Org & Site. Click the + button.
2. 2 Enter the Site Name, Country/Region, Time Zone, and optionally set the location (longitude/latitude). Click Add.
3. 3 The Site now appears in the list. Use the Network icon in the Action column to manage networking devices, or the Guard icon to manage cameras and NVRs.

Step 3 — Adopt Devices into the Site

1. 1 Add devices by entering the device's serial number or device key from the packaging. Gateway devices also require a username and password.
2. 2 VIGI cameras and NVRs are adopted via the Guard icon in the Site view. Once adopted they appear alongside networking devices in the topology.

Sharing Access with End Users — Step by Step

The correct and only supported method is to invite your client's own TP-Link ID to the Organisation. You assign them a role and optionally restrict which Sites they can access. This is how it works according to TP-Link's official documentation:

1. 1 Client registers a free TP-Link ID at tp-link.com using their own email address. Each person who needs access needs their own TP-Link ID.
2. 2 In Omada Central, go to Omada Central Plane > Accounts > Add New User.
3. 3 Enter the client's TP-Link ID (their email address). Select their Role for Omada Guard, and optionally set their Omada Network and Omada Central Plane roles. Under Privileges, choose which Sites they can access — all sites or specific ones only.
4. 4 Click Invite. An invitation email is sent to the TP-Link ID's address.
5. 5 The client checks their inbox and clicks Accept Invitation. Once accepted, they can log into omada.tplinkcloud.com or the Omada app with their own TP-Link ID and see only the Organisation they were invited to.

User Roles in Omada Guard

There are six roles available when inviting a user to an Organisation with Omada Guard. These are the exact role names and descriptions as defined in TP-Link's official documentation:

Role	Description (per TP-Link)	Recommended for end users?
Owner	The one who creates the organisation and holds the highest permission by default.	Installer only
Super Admin	Has all permissions and can access all resources.	Use with care
Admin	Has all permissions but can only view specific users and sites.	Suitable for IT contacts
Operator	Can perform all device operations but lacks permissions for user and system management.	Good default
Viewer	Can only view video resources and has no operation or system management permissions.	Monitoring only
Live Only User	Can only view live video.	Front desk / lobby screen

What the End User Experiences

• Receiving the invite The client receives an email from TP-Link. They click the Accept Invitation link, which opens Omada Central in their browser and binds their TP-Link ID to the Organisation.
• Logging in They sign into omada.tplinkcloud.com or the Omada mobile app with their own TP-Link ID. They will see only the Organisation(s) they have been invited to — your other clients are completely hidden.
• Viewing cameras With a Viewer or Live Only User role, they can access live view (and playback if Viewer) for the sites they have privileges on. They cannot change any settings.
• Mobile access The Omada app for iOS and Android works with the same TP-Link ID login. Clients can view cameras and check device status on their phone without any additional setup from you.
• Removing access Go to Admin > Users within the Organisation and delete the user's entry. Their access is revoked immediately.

Best Practices for Installers Acting as Service Providers

• One Organisation per client Never share an Organisation between multiple clients. Full isolation prevents accidental permission crossover and makes offboarding a client clean and straightforward.
• One Site per physical LAN Follow TP-Link's guidance: all devices within one local network belong to the same Site. Multiple branches = multiple Sites within the same Organisation.
• Use distinct TP-Link IDs Each person (not company) who needs access should have their own TP-Link ID. If a client has multiple staff, invite each one individually so you have a clear audit trail and can revoke individual access.
• Assign minimum roles Most end users only need Viewer or Live Only User for Omada Guard. Reserve Admin for client IT staff. Super Admin should be the exception, not the default.
• Review access periodically When staff leave the client's organisation, remove their TP-Link ID from Admin > Users promptly. Dormant accounts with active access are a security risk.
• Start Essentials, upgrade later Essentials is free and handles the majority of residential and small-business installs. TP-Link allows migration from Essentials to Standard while retaining all existing device configurations — there is no hardware change required.

Quick Reference — Navigation Paths

Task	Navigation in Omada Central	Who performs it
Create Organisation	Dashboard → + Add Organization	Installer (Owner)
Create Site	Admin → Org & Site → +	Installer (Owner)
Adopt networking devices	Site view → Network icon → Add device	Installer (Owner / Admin)
Adopt VIGI cameras / NVR	Site view → Guard icon → Add device	Installer (Owner / Admin)
Invite end user	Omada Central Plane → Accounts → Add New User	Installer (Owner)
Client accepts invite	Email inbox → Accept Invitation link	End user
Client views cameras	omada.tplinkcloud.com or Omada app	End user (with Viewer / Live Only role)
Remove a user	Admin → Users → Delete	Installer (Owner)