Skip to main content
Workspace settings control team access, API access, and integrations that affect the whole Ringg AI workspace.

Workspace Members

Use Workspace Members to invite teammates and control what they can change.

View Members

  1. Click Workspace Members in the left sidebar under More.
  2. Review the member list.
The table shows each member’s name, email, permission level, owner status, and invitation status.

Invite a Member

  1. Click Invite Member.
  2. Enter the teammate’s email address.
  3. Choose the permission level.
  4. Send the invitation.

Permission Levels

PermissionUse It For
View & EditTeammates who create or update assistants, campaigns, numbers, or settings
View OnlyTeammates who only need to review history, analytics, or configuration

Remove a Member

  1. Find the member in the table.
  2. Click Remove User.
  3. Confirm the removal.
You cannot remove the workspace owner from the workspace. Transfer ownership first if ownership needs to change.

API Key

Use API Key when engineers need to connect Ringg AI to your product, CRM, website, or data systems.

Copy the API Key

  1. Click API Key in the left sidebar.
  2. Click the eye icon only if you need to reveal the key.
  3. Click the copy icon to copy it.
  4. Send it to the developer through your company’s approved secret-sharing process.
The API key is sent as the X-API-KEY header in Ringg AI API requests.
X-API-KEY: $RINGG_API_KEY
Treat the API key as a secret. Do not paste it into public tickets, docs, chat channels, frontend code, screenshots, or emails.

Regenerate the API Key

Click Regenerate only when you intentionally want to rotate the key. Regenerating immediately invalidates the old key. Coordinate with developers before rotating so existing integrations do not break.

Open API Docs

Click Docs to open the Ringg AI API reference.

Integrations

Click Integrations in the left sidebar. Integrations connect Ringg AI to telephony providers and workflow tools.

Your Telephony

Use Your Telephony when your company wants to use its own provider numbers.
  1. Open Integrations.
  2. Click the Your Telephony tab.
  3. Click Add New.
  4. Choose the provider, such as Twilio, Exotel, or Plivo.
  5. Enter the provider credentials.
  6. Click Save.
  7. Open Numbers and confirm the provider numbers appear.
If you do not connect a custom telephony provider, Ringg AI uses the default Ringg AI telephony setup.

Zapier

Use Zapier when business users want to connect Ringg AI to other apps without a custom backend. Common examples:

Google Sheets to Ringg AI

Start a Ringg AI action when a new row appears in a sheet.

Shopify to Ringg AI

Start customer calls for new orders or delivery updates.
To connect:
  1. Open Integrations.
  2. Go to Zapier.
  3. Click Sign up or Log in.
  4. Choose Ringg AI and the app you want to connect.
  5. Follow Zapier’s setup steps.
Zapier may ask for the Ringg AI API key. Use the same secret-handling rules as any backend integration.

Webhook Setup Handoff

Webhooks send call results to another system automatically. Business users usually decide what should happen; developers usually configure the endpoint. Give developers:
ItemWhy They Need It
Business goalExample: send completed call results to CRM
Assistant name and agent_idWebhook subscriptions are configured for an assistant
Events neededExamples: call status, recording, transcript, analysis, all processing completed
Destination systemCRM, support tool, data warehouse, Google Sheets, or another backend
Receiver URL ownerThe team that owns the webhook endpoint
API keyNeeded to configure the subscription through the API
Developers can follow Webhook setup.

Developer Handoff

For workspace-level setup, send developers:
ItemUse
Workspace API keyServer-side API authentication
Telephony providerConfirms whether calls use Ringg AI telephony or BYOT
Workspace members with edit accessConfirms who can change production settings
Number listHelps map caller IDs to campaigns and products
Webhook requirementsDefines what post-call data should be delivered automatically
Ask developers to store the API key in a secret manager and to tell you before they regenerate or rotate it.