Projects & Workspaces
Every resource in SipPulse AI — agents, knowledge bases, API keys, threads, structured analyses — belongs to a Project. Projects are the primary way to organize your work, control access, and manage budgets across your organization.
What is a Project?
A Project is an isolated workspace that groups related resources together. Think of it as a folder for everything related to a specific initiative, client, or team.
Examples of projects:
- "Customer Support" — agents and knowledge bases for your support team
- "Sales Outbound" — voice agents and analytics for sales calls
- "Internal Tools" — API integrations and structured analyses for internal use
Default Workspace
When your organization is created, a Default Workspace is automatically set up. All pre-existing resources (agents, knowledge bases, API keys, etc.) are assigned to this workspace.
You can rename the Default Workspace and customize it like any other project, but it cannot be deleted.
TIP
If your team works on a single initiative, the Default Workspace may be all you need. Create additional projects only when you need clear separation between different workloads.
Creating a Project
- Navigate to Projects in the sidebar
- Click Create Project
- Fill in the details:
- Name: A descriptive name for the project
- Icon: Choose from available icons to visually identify the project
- Color: Pick a color that appears in the Project Switcher and throughout the UI
- Click Save
Project Switcher
The Project Switcher is located in the sidebar and allows you to quickly switch between projects. When you select a project, the entire platform filters to show only resources belonging to that project.
- All pages (Agents, Knowledge Base, API Keys, Dashboard, etc.) respect the currently selected project
- Creating a new resource automatically assigns it to the active project
- The Project Switcher shows the project icon and color for quick identification
Resources Belong to Projects
The following resources are scoped to the active project:
| Resource | What it means |
|---|---|
| Agents | Each agent belongs to one project. You can copy agents to other projects. |
| Knowledge Bases | Tables and their data are project-scoped. |
| API Keys | Each key is tied to a project and can only access that project's resources. |
| Threads | Conversations are associated with the project of the agent that created them. |
| Structured Analyses | Analysis schemas belong to a project. |
| Webhooks | Webhook configurations are project-scoped. |
Org-Scope vs Project-Scope Members
How a team member interacts with projects depends on their role scope:
Org-Scope Roles (Admin, Member)
- See all projects in the Project Switcher — no restrictions
- Not subject to project budgets — their usage is tracked at the organization level
- Can manage resources across any project
- Full sidebar visibility (based on their role permissions)
Project-Scope Roles (Developer, Viewer)
- See only assigned projects — they must be explicitly added to each project they need access to
- Subject to project budgets — their usage counts against the project's budget limits
- Can only interact with resources in their assigned projects
- Reduced sidebar visibility based on permissions
Practical Example
An Admin can switch between all projects and manage everything. A Developer assigned to "Customer Support" and "Sales Outbound" will only see those two projects in their Project Switcher, and cannot access "Internal Tools" at all.
Customization
Each project can be customized with:
- Icon: Visual identifier shown in the Project Switcher and project headers
- Color: Accent color used throughout the UI when the project is active
This helps teams quickly distinguish between projects, especially when switching frequently.
Budget per Project
Organization-scope users (Owner and Admin) can configure spending budgets for individual projects to control costs. Budget configuration is accessed via the Budget Settings button (wallet icon) in the projects table. Project-scope users cannot configure budgets — they can only view their budget status.
Time Windows
Budgets use a time window system with two independent windows:
| Window | Default | Purpose |
|---|---|---|
| Short window | 5 hours | Prevent sudden cost spikes (e.g., a runaway agent) |
| Long window | 7 days | Control overall project spending over a longer period |
Each window tracks spending independently. Windows start counting from the first billable operation and reset automatically when they expire — no manual intervention needed.
How Budgets Work
- Budget limits are set in your organization's currency
- Project-scope members (Project Manager, Developer, Member, Viewer) see budget as percentages only — no dollar amounts
- Org-scope members (Owner, Admin) see full details including amounts, remaining balance, and reset times
- A Budget Indicator appears in the page header when a project has a budget configured, showing mini progress bars for each active window
- In the projects table, the Usage column shows budget consumption at a glance with color-coded bars (green → amber → orange → red)
When Budget is Exceeded
When a project's budget is exceeded in any window:
- New billable operations (LLM calls, transcriptions, TTS) are blocked for that project
- The Budget Indicator turns red with a "Budget exceeded" alert
- API calls return a 429 error with the time remaining until the window resets
- Existing resources remain accessible — only new billable operations are blocked
Budget Configuration
| Setting | Description |
|---|---|
| Short window hours | Duration of the short window (default: 5h, min: 1h) |
| Short window limit | Maximum spend in the short window (in your currency) |
| Long window days | Duration of the long window (default: 7d, min: 1d) |
| Long window limit | Maximum spend in the long window (in your currency) |
| Enforce limit | Whether to block operations when exceeded, or just track usage |
| Enforce for org-scope | Whether Owner and Admin are also subject to the budget (default: off — they bypass) |
| Count org-scope usage | Whether usage from Owner and Admin counts toward the project budget (default: off) |
Each window can be enabled or disabled independently. Setting a limit to empty disables that window.
Budget Alerts
You can configure email notifications for each time window independently:
- Enable the budget limit for a window (short or long)
- Toggle Email Alert within that window's settings
- Set the Alert Threshold — the percentage at which the notification triggers (e.g., 80%)
- Choose which roles should receive the alert email
By default, Owner, Admin, and Project Manager receive notifications. You can customize this per project in the budget configuration modal.
TIP
Set different thresholds for short and long windows. A lower threshold on the short window (e.g., 70%) gives your team more time to react to sudden spending spikes.
Removing a Budget
To remove a project's budget and revert to unlimited spending, delete the budget configuration in the budget settings modal.
Managing Projects
| Action | Who can do it |
|---|---|
| Create a project | Admin |
| Edit project details | Admin |
| Archive a project | Admin |
| Add members to a project | Admin |
| Switch between projects | Anyone (within their visible projects) |
For a complete breakdown of what each role can do, see Roles & Permissions.
Next Steps
- Roles & Permissions — Understand what each team role can access
- Team Management — Add members and assign them to projects
- Plan & Subscription — Configure budgets and resource limits