Roles & Permissions

SipPulse AI uses roles to control what each team member can see and do. Every user in your organization is assigned a single role, and that role determines their level of access across the platform.

Roles are assigned by an Admin when adding or managing team members.

Understanding Scope

The most important concept in our permission system is scope. Each role operates at one of two levels:

Organization Scope

Owner and Admin have automatic access to all projects and all resources — they don't need to be added to each project individually.

Project Scope

Project Manager, Developer, Member, and Viewer can only see and interact with projects they've been explicitly added to.

	Organization Scope	Project Scope
Roles	Owner, Admin	Project Manager, Developer, Member, Viewer
Project visibility	All projects, automatically	Only assigned projects
Needs to be added to projects?	No	Yes
Project Switcher	Shows all projects	Shows assigned projects only

TIP

When you add a new team member, think first about scope: do they need to see everything, or just specific projects? This narrows your role choice immediately.

Available Roles

SipPulse AI provides six roles, listed from most to least privileged.

---

Owner Organization Scope

The user who created the organization. Has unrestricted access to everything, including the ability to delete the organization itself.

• Full control over all resources, members, billing, integrations, and settings
• The only role that can delete the organization
• Cannot be reassigned to another user

---

Admin Organization Scope

Best for: Team leads, managers, or operations staff who need full control.

What they can do:

• Manage all team members — invite, change roles, remove, reset passwords
• Manage billing, subscription, and plan settings
• Create and manage projects, including assigning members
• Full access to all agents, knowledge bases, structured analyses, webhooks, and API keys across all projects
• Manage integrations and provider credentials
• View the Dashboard and organization analytics
• Use the Playground (text generation, speech-to-text, text-to-speech, anonymization)

What they cannot do:

• Delete the organization (only the Owner can)

---

Project Manager Project Scope

Best for: Team leads who run specific projects and their members, but don't need organization-wide control.

What they can do:

• Manage the team within their assigned projects — add and remove project members
• Create, edit, and delete agents, knowledge bases, and structured analyses
• Manage webhooks within their projects
• View and manage API keys within their projects
• Reset passwords for members in their projects
• Use the Playground (text generation, speech-to-text, text-to-speech, anonymization)

What they cannot do:

• View the Dashboard or organization analytics
• Manage billing or subscription settings
• Manage integrations and provider credentials
• Create or manage projects
• Access projects they haven't been assigned to

---

Developer Project Scope

Best for: Technical users who build and configure agents within specific projects.

What they can do:

• Create, edit, and delete agents and their configurations
• Manage knowledge bases and structured analyses
• Create and manage webhooks
• Create and manage their own API keys
• Use the Playground (text generation, speech-to-text, text-to-speech, anonymization)

What they cannot do:

• View the Dashboard or organization analytics
• Manage the project team (add or remove members)
• Manage billing or subscription settings
• Manage integrations and provider credentials
• Access projects they haven't been assigned to

---

Member Project Scope

Best for: Day-to-day users who interact with existing agents and manage their own work.

What they can do:

• Create agents and manage (edit, delete) their own agents
• View all agents and interact with them through conversations (threads)
• Create and manage their own threads
• Create knowledge base entries and manage (edit, delete) their own entries
• Create structured analyses, execute them, and manage their own
• Create and manage their own API keys
• Use the Playground (text generation, speech-to-text, text-to-speech, anonymization)

What they cannot do:

• Edit or delete agents, knowledge bases, or structured analyses created by others
• View the Dashboard, analytics, or the members list
• Manage webhooks, projects, or integrations
• Manage team members or billing
• Access projects they haven't been assigned to

---

Viewer Project Scope

Best for: Stakeholders, clients, or QA team members who need to observe without making changes.

What they can do:

• View agents, threads, knowledge bases, and structured analyses

What they cannot do:

• Create, edit, or delete any resource
• Use the Playground
• View the Dashboard or analytics
• Access projects they haven't been assigned to

---

Resource Ownership

Some roles let you manage only the resources you personally created. This is especially relevant for Members.

How it works:

• If you created an agent, you can edit and delete it — even if your role doesn't grant full agent management
• Resources created by other users are read-only for you (unless your role grants full access to that type of resource)
• Admins and Owners can manage any resource regardless of who created it

This applies to:

• Agents (edit, delete)
• Threads (edit, delete)
• API Keys (view, delete)
• Structured Analyses (edit, delete)
• Knowledge Base entries (edit, delete)

TIP

Ownership is determined by who created the resource. If you create an agent while you have permission to do so, you keep the ability to manage it even if your role changes later.

When Your Role Changes

When an Admin changes your role, your session ends automatically. The next time you open SipPulse AI, you'll log in as usual and your new permissions will already be in effect — there's nothing you need to do.

Setting Up Roles for Your Team

Here are some common patterns:

Small team (2–5 people) Typically one Owner + one or two Admins. Everyone has organization-wide access.

Growing team (5–20 people) Add Project Managers to lead specific projects. Developers build and configure agents. Members handle day-to-day conversations.

Enterprise or multi-client setup Use Viewers for external stakeholders or clients who need visibility into conversations. Create separate projects per client and assign team members only to the projects they work on.

External consultants Assign the Developer role scoped to specific projects. They get full build access within those projects without seeing anything else.

Next Steps

• Team Management — Add members and assign roles
• Projects & Workspaces — Understand how projects scope resources
• Plan & Subscription — View plan limits and pricing