An IcloneU account can be run by more than one person, and the Team page is where you decide who gets in and what they can touch. Access is role-based: three predefined roles IcloneU maintains for you, plus custom roles you build yourself. This guide is the deep reference — what each role actually grants, how the permission groups break down, and the change-role and remove flows. If you just want to add your first teammate, start with the quickstart: Inviting team members.
Open the avatar menu in the top-right corner and choose Team. The Team surface is verified on the Expert plan; if the menu entry isn't there on your plan, that capability may not be included on your tier. Only Owners and administrators can add, remove, and change member roles — the page says so itself.
The Team page at a glance
The page states its own model up front: "Select a team from the dropdown to view its members. Use Invite member to add new users and Manage roles to configure permissions. Owners and administrators can add, remove, and change member roles." Three elements do the work:
- The team selector — a Select a team dropdown naming the team (labelled with the account email) and its member count. It's a selector, which implies you can belong to more than one team and switch between them.
- The Members grid — a summary row (N total · N confirmed · N pending invite), a search box, and the columns Email / Role / Last active / Actions. Your own row is tagged You; the account creator's row carries the Owner badge. Each row has per-member action icons.
- Roles — opened with the Manage roles button, where custom roles are created and the predefined ones are explained.
The summary row tracks three member states. A teammate you've invited but who hasn't accepted yet counts under pending invite; once they accept they move to confirmed. That count is the in-product signal of where an invite stands.
The three predefined roles
Every role is a bundle of granular permissions spread across four groups — Account, Clones, Connections and Interactions. There are 51 individual permissions in total (13 + 9 + 7 + 22). IcloneU ships three predefined presets; the table shows how many permissions each one enables in each group.
| Role | Account | Clones | Connections | Interactions | Best for |
|---|---|---|---|---|---|
| Administrator | 13 / 13 | 9 / 9 | 7 / 7 | 22 / 22 | A second person who can do everything — all 51 permissions on |
| Clone editor | 3 / 13 | 9 / 9 | 2 / 7 | 5 / 22 | Someone who builds and tunes Clones and their Knowledge, with light access elsewhere |
| Response editor | 2 / 13 | 2 / 9 | 2 / 7 | 15 / 22 | Someone focused on conversations — reviewing, editing and handling replies |
Read the counts as defaults, not handcuffs: a preset is a starting configuration. The dialog is explicit about it — "You can modify individual permissions afterward to create a custom setup." So Clone editor giving 9/9 on Clones means it turns on every Clone permission by default; you're free to dial any of them back before you send the invite.
The groups mirror the product's surface areas: Account (settings and billing), Clones (Knowledge and Clone configuration), Connections (channels) and Interactions (messages, post replies and contacts). Each group expands to its individual toggles in the dialog — the exact per-permission names aren't catalogued in this guide, so open a group on screen to see precisely which switches it holds.
Owner is not a role you can assign
Owner is the account creator's badge — it appears on their row in the Members grid, and it carries full control. But it is not one of the invite presets: the role dropdown offers only the three predefined roles plus any custom roles you've made. You cannot invite someone as Owner.
Because the Owner row is fixed, it isn't something you remove or re-permission from the grid — you can't take the Owner off the team or rewrite their access there. To hand off the workspace itself, you'd be transferring ownership, which isn't something this guide can walk you through; contact support if you need it.
Building a custom role
When the three presets don't fit, make your own. There are two ways in, and both end up in the same place — a named role with exactly the permissions you choose.
Open Manage roles
On the Team page, click Manage roles. The Roles dialog lists your custom roles in a Role name / Members / Permissions grid. Until you've made one it shows the empty state: "No custom roles yet. Click \"New role\" to create one."
NoteThe dialog spells out the governance rule, verbatim: "Predefined roles are managed by IcloneU and cannot be renamed or deleted. You can still fork them into a custom role." That's the key idea — you can't edit Administrator, Clone editor or Response editor, but you can fork one as the starting point for your own.
Create the role
Click New role. A new custom role appears in the list, ready for you to rename and to expand its permission groups and toggle individual switches on or off.
Or fork a predefined role while inviting
The other route lives in the Invite member dialog: pick a predefined role as your starting point, adjust its permissions, then use the Create role button to save that combination as a reusable custom role. This is how you "fork" a preset — start from Administrator, trim what you don't want, and keep the result.
Custom roles belong to your account and show up alongside the predefined ones in the role dropdown, tagged Custom versus Predefined so you always know which is which.
Changing a role or removing a member
Both live in the Members grid's Actions column, and both are reserved for Owners and administrators. The Owner row is the exception — its actions stay disabled.
Find the member
On the Team page, use the search box (it filters by email) to locate the person, or just scan the grid. Their current role shows in the Role column.
Change what they can do
Use the row's edit action in the Actions column to adjust their permissions — you can pick a different role as a starting point or fine-tune individual toggles, the same way you set access at invite time.
TipChanging access is non-destructive and reversible — you can re-open the same member any time and adjust again. New permissions apply to what that member can do going forward.
Remove someone
Use the row's remove action in the Actions column. If the row is still a pending invite, removing it revokes the outstanding invitation; if the member has accepted, it takes them off the team — you'll typically be asked to confirm first.
Removing a teammate only revokes that person's access to your workspace — it doesn't touch your Clones, Knowledge or conversation history. This is unrelated to a Connection's Remove, which permanently purges a channel and its conversation history. Different surfaces, different consequences.
Frequently asked
Inviting team members is the quickstart — the few clicks to add your first colleague and pick a role. This guide is the reference behind it: what each role actually grants, how to build custom roles, and how to change or remove people later. Read the quickstart to get moving; come here when you need the detail.
No — the dialog states it plainly: "Predefined roles are managed by IcloneU and cannot be renamed or deleted." What you can do is fork one into a custom role: start from Administrator, Clone editor or Response editor, adjust the permissions, and save the result as your own role with Create role.
Owner is the account creator's badge, not an invite preset. The role dropdown offers the three predefined roles plus any custom roles you've created — there's no "Owner" option, and the Owner's own row can't be removed or edited from the grid.
Access changes are non-destructive and apply to what that member can do from then on. You can re-open the same member and adjust again at any time; nothing about the change is permanent or one-way.
No. Removing someone revokes their access to your workspace; it doesn't delete Clones, Knowledge or conversations. Don't confuse it with a Connection's Remove, which is permanent and purges that channel's conversation history.
Last updated July 6, 2026 · Account & Settings
