Members and roles
Members are the people who work in your workspace: the ones who build agents, answer customers in the Inbox or just look at the numbers. Each member has one role that decides what they can see and change. You manage members in Settings → Members.
The five roles
Roles are ordered. Each role can do everything the role before it can, plus more.
| Role | In one line | Typical person |
|---|---|---|
| Viewer | Reads everything, changes nothing. | A manager who checks conversations and analytics. |
| Operator | Answers customers in the Inbox. | A support agent at your dental clinic's front desk. |
| Editor | Builds and changes agents. | The person who sets up your store's assistant. |
| Admin | Runs the workspace: members, API keys and settings. | The team lead or IT contact. |
| Owner | Everything, including other owners and deleting the workspace. | The business owner. |
Peki shows the same summary under the members list: "Viewer: read only. Operator: answers in the Inbox. Editor: builds agents. Admin: members, keys and settings. Owner: everything, including other owners."
What each role can do
The table lists the lowest role that can do each thing. Higher roles can always do it too.
| Action | Lowest role |
|---|---|
| See agents, their instructions, tools, knowledge and versions | Viewer |
| Read conversations in the Inbox and open customer details | Viewer |
| See analytics, records and files | Viewer |
| See the members list and the credit balance in Plan & credits | Viewer |
| See workspace Variables | Viewer |
| Chat with the Copilot (it never acts beyond your role) | Viewer |
| Take over a conversation, reply, send files, Hand back to AI and Resolve | Operator |
| Edit a customer's details (name, tags, notes) | Operator |
| Create agents and edit the draft: instructions, tools, Functions, skills, knowledge, model and guardrails | Editor |
| Test in the Test panel | Editor |
| Publish a version or restore an older one | Editor |
| Connect and change channels (website chat, Telegram) | Editor |
| Create and change automations, record tables and records | Editor |
| Approve or reject actions waiting in Approvals | Editor |
| See Settings → Secrets and add keys | Editor |
| Create, change and delete Variables | Editor |
| Change analytics settings | Editor |
| Invite members, change roles and remove members | Admin |
| Create and revoke API keys | Admin |
| Change the workspace name, default language, timezone and Business hours | Admin |
| Change a key's allowed sites, assign or remove secrets | Admin |
| Delete an agent | Admin |
| Delete a record table | Admin |
| See the credit History and the Usage page | Admin |
| Add, change or remove owners | Owner |
| Delete the workspace | Owner |
Peki checks your role on every request, not only when you sign in. If an admin changes your role or removes you, it applies to your very next click.
Roles and the Copilot
Every member can open the Copilot, but it only does what your role allows. A viewer can ask questions about an agent; an editor can ask it to change the agent. Actions with real effects, like publishing, still wait for your approval on a card.
Roles and API keys
API keys are not members, but they act with a role too. A Read only key acts as a viewer and a Read and write key acts as an editor. A key can never act as an admin or owner, so a key can't manage members, create other keys or delete the workspace. See API keys.
Invite a member
You need to be an admin or owner.
- Go to Settings → Members.
- Type the person's email address.
- Pick a role. The form starts on Operator.
- Click Invite.
What happens next depends on whether the person already has a Peki account:
- They have an account. They join right away and see the workspace in their workspace switcher.
- They don't have one yet. They show in the list as Invited — joins on first sign-in. When they sign in with that exact email address (with Google or an email link), they join automatically.
Either way, Peki sends them an invitation email in the workspace's default language. If the email doesn't arrive, the invite still stands: tell them to sign in at https://peki.ai with that address.
Invite the address the person actually signs in with. An invite to [email protected] won't match a Google account on [email protected].
Invite errors
| Message | Why | What to do |
|---|---|---|
| Already a member or invited | That email is already in the list. | Change their role instead. |
| Only owners can add owners | You're an admin and picked Owner. | Ask an owner, or invite with another role. |
| Requires admin role | You're not an admin or owner. | Ask an admin to invite them. |
Change a member's role
- In Settings → Members, find the person.
- Choose the new role from the menu next to their email. It saves at once.
Rules:
- Only owners can make someone an owner, and only owners can change an owner's role.
- A workspace always needs at least one owner. You can't demote the last owner. Make someone else an owner first.
- You can't change your own role. Another admin or owner has to do it.
Remove a member
- In Settings → Members, click Remove next to the person.
- Confirm. Peki warns: "They lose access to this workspace right away."
Removing someone ends their access immediately, on their next request. Their past work stays: the agents they built, the replies they sent in the Inbox and the changes they made are kept. Removing an invited person who hasn't joined yet cancels the invite.
Rules:
- Only owners can remove an owner.
- You can't remove the last owner.
- You can't remove yourself from this screen.
Owners
Owners can do everything admins can, plus:
- add owners, change an owner's role and remove owners,
- delete the workspace in Settings → Workspace (see Workspace settings).
The person who creates a workspace becomes its first owner. If that person leaves the business, make someone else an owner before you remove them.
Give the Owner role sparingly. An owner can delete the workspace and everything in it, and that can't be undone.
Every change is recorded
Invites, role changes and removals are written to the workspace's audit log with who made them and when. See Security model.