TeleportHQ for agencies: deliver sites your clients can run themselves
In TeleportHQ, an agency designs and publishes a client's site in the editor, and the client runs the live site from the admin panel on their own site: orders, products, bookings, blog posts, users, files and new pages built from blocks, without opening the editor. You can keep every client in one agency workspace, with a folder per client, or build in a workspace the client owns. This guide says how that works day to day, what the client can do alone, and how a site is handed over.
Who this guide is for
- Agencies, freelancers and studios building sites for several clients.
- Anyone delivering a website or an online store that the client must update themselves afterwards.
The short answer
The agency designs and publishes in the TeleportHQ editor. The client runs the live site from its own admin panel, at /admin/dashboard on their published site. The two never need the same screen: the editor is where you design the site, and the admin panel is where your client runs it. See What is the admin panel?.
How an agency works in TeleportHQ
- A workspace holds the projects, the members and the billing. Every TeleportHQ workspace has one Owner, members with roles, and its own plan and billing, and you can own several, for example one per client. See What is a workspace?.
- One agency workspace, a folder per client. Keep each client's projects in their own folder (folders are a paid-plan feature). To show a client only their folder, invite them as a Limited Viewer, which is free and read-only, and add them to that folder's collaborators: they can look and leave comments, and nothing else. Your own people get Designer (builds and publishes, can't invite or share) or Admin (can also invite people and share projects). See How to control who can see a project folder and What can each role do?.
- Or the client's own workspace. The client creates the workspace, pays for its plan and invites you as Admin or Designer. The site, the domain and the subscription are the client's from day one, and your access ends when they remove you. See How to invite people to your workspace.
- A base project, copied for each client. Build your starter project once and clone it for each new client (⋯ → Clone on its dashboard card), then replace its texts and images with AI, page by page. A client started from a gallery template can instead be rewritten for their business by the Tailor this project window, which the AI Assistant opens, with the layout kept. See How to duplicate a project (and reuse it like a template), How to replace all images or texts on a page with AI, How to start a project from a template and What can the TeleportHQ AI Assistant do?.
- Each project on its own domain, with a private staging address where the client reviews changes before they go live, and a password while it's in progress. A Can view link lets a client look at the project in the editor without editing it. See How to connect your own domain, How to test changes on a staging site before going live, How to password-protect your site and How to make a project private, view-only or cloneable.
What the client does without the editor
The TeleportHQ admin panel is a back office TeleportHQ builds for a web app at /admin/dashboard on the published site. Your client signs in there and manages, depending on what the site uses: users, orders, products and their reviews, shipments and subscriptions, bookings, invoices, blog posts and comments, files, the log of every email the site sent, and new pages built from blocks. Any database table you add, for example a Menu table, gets its own list, create and edit pages there. See What is the admin panel?, How to manage a database table from the admin panel and How to build your own admin pages from blocks.
What stays with the agency, in the editor: the design, the layout and the texts of the pages you designed, the workflows, the project settings and publishing.
The client gets in through the site's own sign-up and login. When you switch on Authentication, you create the first admin account; that account signs in with full admin rights and opens the admin panel. You can create more accounts and set their roles later. See How to add sign-up and login to your site and How to manage your site's users and roles.
What the agency sees across clients
- Each project's numbers live in that project. Its visitor analytics, site health audit, form submissions and reports are under Growth in that project's editor. See How to see who visits your site (Analytics) and How to check your site's SEO health.
- AI tokens are a workspace balance, shared by all its projects and members. See What are AI tokens, and how many do I get?.
- Editor seats are per workspace. Each person with an editing role uses a seat; Viewers and Limited Viewers are free. See How do editor seats work, and what do they cost?.
- Custom domains come in slots, per workspace. See How many custom domains can I connect (and how to get more)?.
Handing a site over
There is no "move this project to another workspace" command in TeleportHQ, and a workspace's ownership can't be transferred. Decide where the site lives before you build it:
- Build it in the client's own workspace from the start, with you as a member. The client owns the site, the domain and the billing, and removes you when the work is done.
- Keep it in your agency workspace, with the client as an admin on their site and a free Viewer or Limited Viewer in the workspace. You keep the editor and the billing; they run the site.
A Can clone link gives the client a copy, not a move: the copy starts unpublished, without the domain, the Secrets, the payment set-ups or the customer data (user accounts, orders, bookings). See Can I transfer a project to another account?.
Try TeleportHQ
Every new TeleportHQ account starts with a free 7-day trial, with no credit card, on 1 project. See How does the TeleportHQ free trial work?. Then follow How to create your first website in TeleportHQ.