Skip to main content

​
Projects

Projects in Diga represent the organizations that use the platform to manage AI voice agents. Each project operates independently with its own set of resources, billing configuration, and team members.

​
Overview

Projects are the main organizational unit in Diga. They provide a multi-tenant environment that allows the platform to serve multiple organizations while maintaining strict data isolation. All platform resources (agents, calls, contacts, phone numbers, etc.) are associated with a specific project.

​
Key Capabilities

  • Data Isolation: Complete separation of data and resources between projects
  • Team Management: Support for multiple users with role-based access control
  • Specific Resources: All platform resources are associated with a project
  • Billing Integration: Each project has its own subscription and payment configuration

​
Create a Project

When you create a new project, it is automatically configured with:
1

Basic information

Provide a descriptive name and optional description for your project
2

Your role

You are automatically assigned as the project administrator
3

Billing configuration

A Stripe customer is created and a free subscription is initialized
4

Initial resources

Your project is ready to start creating agents and managing calls
Each user can create multiple projects. There is no limit on the number of projects you can manage.

​
Project Management

​
Update Project Information

Administrators can update project information:
  1. Go to Settings > Project
  2. Modify the name or description
  3. Click Save changes

​
View Project Details

To view detailed information about your project:
  • Name: Your project name
  • Description: An optional description of your project
  • Creation date: When the project was created
  • Project ID: Unique project identifier

​
Team Management

​
Invite Members

Administrators can invite new members to the project:
1

Access member management

Go to Settings > Members
2

Send an invitation

Click “Invite member”, enter the email and select a role (Administrator or Member)
3

User receives invitation

An invitation email is sent to the user
4

Acceptance

Once accepted, the user will appear in the project member list

​
Team Roles

Each project member has one of two roles:
RoleDescriptionPermissions
AdministratorFull administrative accessCan manage all resources, members, billing, and project configuration
MemberLimited access for daily operationsCan view resources and make calls, but cannot modify configuration or manage team
For more details on specific permissions, see the Roles and Permissions page.

​
Manage Members

Administrators can:
  • View all project members and their roles
  • Change a member’s role (from Member to Administrator or vice versa)
  • Remove members from the project
You cannot remove the last administrator from a project. You must promote another member to administrator first.

​
Project Resources

All these resources are associated with your project:

​
Agents

  • AI voice agents configured with prompts and conversational flows
  • Each agent belongs to a single project

​
Calls

  • Record of all calls made by the project’s agents
  • Call transcriptions, recordings, and analytics

​
Contacts

  • Contact database for the project
  • Customer information management

​
Phone Numbers

  • Phone numbers acquired for the project
  • Call routing configuration

​
Integrations

  • Connections to external systems (CRM, databases, APIs)
  • Webhooks and custom tools

​
API Keys

  • Programmatic access to project resources
  • Keys with restricted permissions for security

​
Project Billing

Each project has its own independent billing configuration:
  • Stripe Customer: A unique Stripe customer per project
  • Subscription Plan: Free, Starter, Pro, Scale, or Business plans
  • Included Minutes: Assigned monthly according to plan
  • Phone Numbers: Monthly charge per number
  • Additional Usage: Extra minutes beyond the plan

Manage Billing

Learn more about subscription plans, billing, and payments

​
Project Deletion

Administrators can delete a project when it is no longer needed:
Project deletion is a permanent action. Although the project record is preserved in the database (soft deletion), access and memberships for all members are removed.
1

Verify requirements

  • You must be a project administrator
  • The project must not be your only project
2

Go to settings

Access Settings > Project
3

Delete project

Click “Delete project” and confirm the action
4

Confirmation

The project will be marked as deleted and removed from your project list

​
Best Practices

Create separate projects for different clients or environments (development, production) to keep resources organized and isolated.
Assign at least two administrators per project to avoid loss of access if one administrator is unavailable.
Periodically audit who has access to your project and remove members who no longer need access.
Choose clear, descriptive names for your projects, especially if you manage multiple projects.

​
Frequently Asked Questions

No, resources are permanently linked to a specific project. If you need to move resources, you will need to recreate them in the destination project.
There is no limit on the number of projects you can create. Each project has its own independent billing.
There is no concept of a unique “owner”. Any administrator has full permissions. You can promote members to administrators or demote administrators to members.
The project is marked as deleted (soft deletion), preserving data for auditing. However, no user will be able to access this data.
Yes, administrators can update the project name and description at any time from settings.