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 keep every client in one agency workspace with a folder per client, or build in a workspace the client owns. The Growth coach watches each site and emails you, not the client, what needs a look. This guide says what you get on day one, what the first week looks like and what you will be asked to decide before you build.
Who this guide is for
- Agencies, freelancers and studios building sites for several clients.
- Anyone delivering a website, a store or a booking site that the client must update themselves afterwards.
What you get on day one
- A workspace per agency, a folder per client. A workspace holds the projects, the members and the billing, with one Owner. On a paid plan you keep each client's projects in their own folder. To show a client only their folder, invite them as a Limited Viewer (free, read-only) and add them to that folder's collaborators: they can look and leave comments, nothing else. Your own people get Designer (builds and publishes, can't invite or share) or Admin (can also invite and share). See What is a workspace?, How to control who can see a project folder and What can each role do?.
- Or the client's own workspace. The client creates it, 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 per client. Build your starter 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, 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 and How to start a project from a template.
- 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.
- The client's back office. The admin panel at
/admin/dashboardon the published site is where your client works: users, orders, products and their reviews, shipments and subscriptions, bookings, invoices, blog posts and comments, newsletter issues and subscribers, 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. The client gets in through the site's own sign-in: when you switch on Authentication, you create the first admin account. See What is the admin panel?, How to manage a database table from the admin panel, How to build your own admin pages from blocks and How to manage your site's users and roles.
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.
What happens in the first week
- The client works in the admin panel; you hear from the coach. Each project's Growth coach reads the site's visitors once a day and lists what to change under Growth → Today in that project. Its emails go to the workspace owner by default, to members who can edit the project only if they switch on Alerts by email, and never to Viewers or Limited Viewers. So in an agency workspace, you get the daily digest (about 8 in the morning, on days with news) and the critical alerts, and a client invited as a Viewer gets none. In the client's own workspace, the client, as owner, gets them unless they switch them off. See How to set up Growth Settings.
- "Your site is not answering" reaches you first. TeleportHQ checks each published site every 15 minutes; after three misses in a row (about 45 minutes) the email goes out at once, and so does "Your site is back" when it answers again. Weekly, each site gets its audit again, a link check and a Search Console read. See How to keep an eye on your site every week (SEO Monitoring).
- Each project's numbers live in that project. Visitor analytics, the site health audit, form submissions, orders and bookings are under Growth in that project's editor; there is no cross-client dashboard. See How to see who visits your site (Analytics).
- Automations do the follow-ups. For a client's store, Growth → Automations sends a thank-you when an order is paid or a note when stock runs low; the client sees the results, you edit the steps. See How to send emails automatically when something happens on your site (Automations).
- The Monday report can go to the client. With AI coach and Weekly report on, the report is emailed to everyone whose Alerts by email is on, in the site's language. It uses the workspace's AI tokens (at least 600 per report).
What you will be asked to decide
- Where the site lives, before you build it. There is no "move this project to another workspace" command, and a workspace's ownership can't be transferred. Either build in the client's own workspace from the start, with you as a member, or keep it in your workspace with the client as an admin on their site and a free Viewer or Limited Viewer in the workspace. 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. See Can I transfer a project to another account?.
- Who pays for what. AI tokens are a workspace balance shared by all its projects and members; editor seats are per workspace, with Viewers and Limited Viewers free; custom domains come in slots per workspace; each web app needs a Web App slot after its first 7 days. See What are AI tokens, and how many do I get?, How do editor seats work?, How many custom domains can I connect? and Why does my web app need a slot?.
- Which emails reach the client. The coach's emails follow the roles above. The emails the site sends to the client's customers (orders, bookings, newsletters) go through an email provider connected in the client's project, on an account the client or you own. See How to choose which email and SMS provider your project sends through.
- Which plugins the client runs. A store, bookings, a blog, a help center and a newsletter each add their own screens to the admin panel; the client never needs the editor for them. The design of their pages stays yours.
Where to start
- What is a workspace? and What can each role do?
- How to duplicate a project (and reuse it like a template)
- How to add sign-up and login to your site, then How to turn on the admin panel
- How to set up Growth Settings: who gets the coach's emails
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?.