What can each role do? (Admin, Designer, Editor, Viewer)
TeleportHQ has six roles: Owner, Admin, Designer, Editor, Viewer and Limited Viewer. Owner, Admin, Designer and Editor can change projects, and each uses an editor seat. Viewer and Limited Viewer are free, read-only roles that can leave comments. The Editor role is more limited than its name suggests: it can't publish, view code, edit components or change project settings, and by default it only sees the pages you give it.
The roles at a glance
- Owner: the person who created the workspace. There is exactly one, and the role can't be given to someone else.
- Admin: can do everything in the workspace's projects, including inviting and removing people. Admins can't manage the plan or billing.
- Designer: can build and publish, but can't invite people or share projects. This is the default role when you invite someone.
- Editor: can edit pages and content on the pages they can see, but can't publish or change the site's design system.
- Viewer: can open every page and leave comments, but can't change anything.
- Limited Viewer: can open only the pages or folders you give them access to, and leave comments.
Permissions table
This table shows what each TeleportHQ role can do inside a project.
| What the person can do | Owner | Admin | Designer | Editor | Viewer | Limited Viewer |
|---|---|---|---|---|---|---|
| Uses an editor seat | Yes (included) | Yes | Yes | Yes | No (free) | No (free) |
| Invite and remove people | Yes | Yes | No | No | No | No |
| Open the Share window and change project privacy (Private, Can view, Can clone) | Yes | Yes | No | No | No | No |
| Set which pages each person sees | Yes | Yes | No | No | No | No |
| See every page in the project | Yes | Yes | Yes | No, only pages given to them or created by them | Yes | No, only pages given to them |
| Create, edit and delete pages | Yes | Yes | Yes | Yes | No | No |
| Create, edit and delete components | Yes | Yes | Yes | No | No | No |
| Change CSS classes, breakpoints and the Design Language (saved colors and text styles) | Yes | Yes | Yes | No | No | No |
| Open and change Project Settings | Yes | Yes | Yes | No | No | No |
| Use AI features | Yes | Yes | Yes | Yes | No | No |
| Upload images and files | Yes | Yes | Yes | Yes | No | No |
| Delete images and files | Yes | Yes | Yes | No | No | No |
| Publish the site | Yes | Yes | Yes | No | No | No |
| View or download the code | Yes | Yes | Yes | No | No | No |
| Create new projects in the workspace | Yes | Yes | Yes | No | No | No |
| Create backups | Yes | Yes | Yes | Yes | No | No |
| Clone the project into their own workspace | Yes | Yes | Yes | Yes | Yes | Yes |
| Leave comments | Yes | Yes | Yes | Yes | Yes | Yes |
Things only the Owner or an Admin can do
Some TeleportHQ actions are limited to the top two roles, on top of the table.
Owner only:
- See and change the workspace's Plans, Billing, Custom Domains, Extra Languages and Web Apps tabs.
- Rename or delete the workspace.
- Change a workspace member's role in Workspace Settings → Collaborators.
- Delete project secrets.
Owner or Admin only:
- Delete any project from its card's ⋯ menu. A Designer can delete projects too, but only in folders they were added to, or anywhere while the workspace has no folders. Editors and Viewers can't delete projects.
- Rename projects, edit their tags and move them into folders.
- Delete several projects at once with Select on the dashboard.
- Create, rename and delete dashboard folders.
- Rename, delete and restore backups.
- Set graduation projects and graduate students in an Academic workspace.
Workspace members and project collaborators
A TeleportHQ role applies in one of two scopes, and the scope matters as much as the role.
- Workspace collaborators are invited to the whole workspace. Their role applies to every project in it, including new ones. Admins can create projects anywhere. Designers can create projects in folders they were added to, or anywhere while the workspace has no folders.
- Project collaborators are invited to one project from its Share button. Their role applies only to the projects they were invited to, and can be different on each one. They can't see the workspace's other projects and can't create new ones.
See How to invite people to your workspace and How to invite someone to one project.
Which role should I pick?
- A teammate who builds and publishes the site: Designer.
- A second person who manages the team with you: Admin.
- A copywriter who only updates text on a few pages: Editor. Remember to give them access to the pages they need. See How to control which collaborators see each page.
- A client who reviews the work and leaves feedback: Viewer. It's free.
- A client who should see only one section of the site: Limited Viewer, with access to that folder.
Roles, plans and seats answer different questions
In TeleportHQ, a role decides what a person may do in a workspace. The workspace's plan decides what the workspace may do. Whether a role costs money is a billing question.
- "Your current role does not have enough permissions to …" is about the role. For example, an Editor who clicks Publish sees "Your current role does not have enough permissions to publish this project". The Owner or an Admin can give them another role. Changing the plan doesn't help.
- A window that asks you to choose a plan, upgrade or buy a slot is about the plan. Only the Owner can change it.
- Seats: every editing role uses an editor seat. During the trial extra editors are free; on Pro and Premium each editor beyond the Owner is a paid seat; Viewers and Limited Viewers are always free. See How do editor seats work, and what do they cost?.
Good to know
- The role descriptions in the app are out of date. Pointing at a member's role shows text like "Will be able to do anything in a project, except granting access, creating, editing or deleting components" for Editor. The table above is what the app actually allows.
- Avatars simplify roles. The avatars at the top of the editor show the Owner as "Owner", every other editing role as "Editor" and every read-only role as "Viewer".
- An ended subscription makes everyone read-only. When a workspace's trial or subscription ends, every project in it becomes read-only for all roles, the Owner included, until the Owner subscribes.