Getting Started with WARP Permissions

WARP is customer-scoped. Most portal pages show data for the active customer in your session, and the actions available to you depend on your role and permission scopes. If something is missing, disabled, or returns a permission error, the first questions are: "Which customer am I in?" and "Does my role include the required scope?"

Active Customer Context

When you sign in, WARP loads your user profile, active customer, role, and scopes. The active customer controls which trunks, numbers, port requests, invoices, team members, and API keys you are viewing.

If you have access to more than one customer, switch to the correct customer before making changes. After switching, the portal reloads your session context so navigation, scopes, and customer data line up with the selected account.

Buzz uses the same active customer context you do. When you ask about numbers, billing, trunks, or porting, Buzz should answer for the customer currently selected in the portal.

Why Pages or Buttons May Be Hidden

WARP uses scopes to decide what you can see and do. A page may be visible only when your role includes the read scope for that feature. Buttons that create, update, delete, submit, or execute actions usually require a write or action-specific scope.

Common examples:

• Number search requires numbers:read; assigning or changing numbers requires numbers:write.
• Viewing trunks requires trunks:read; creating, editing, deleting, or changing trunk IPs requires trunks:write.
• Viewing port requests requires porting:read; editing drafts requires porting:write; submission and activation have separate scopes.
• Viewing billing requires billing:read.
• Managing team members, roles, or API keys requires the matching team or API key scopes.

If a button is disabled or missing, your role may be intentionally read-only. Ask a customer admin or owner to update your role if you need more access.

Dashboard Cards

The dashboard combines account and operations data. Depending on your scopes, you may see balance, trunk count, number count, utilization, trends, recent call records, and account status.

Dashboard data is permission-aware. For example, usage and call-detail cards need call analytics scopes, number inventory cards need number scopes, and billing cards need billing scopes. If a card is absent, it does not necessarily mean the data does not exist. It may mean your role cannot read it.

Using Buzz in the Portal

Buzz is the in-portal assistant. It can explain what you are seeing, help find the right workflow, fill supported forms, and prepare actions for confirmation. Buzz reads your active customer and your scopes. It should not tell you to perform an action that your role cannot perform.

Buzz can answer general "how do I..." questions even when you lack a write scope. For actual changes, it needs the relevant feature scope and, for sensitive operations, may require step-up verification before execution.

Scopes and API Reference

Use these as the main permission anchors:

• buzz:use - ask Buzz, view sessions, submit feedback, upload files for Buzz where supported.
• analytics:read and cdrs:read - dashboard and call statistics.
• trunks:read, numbers:read, billing:read - customer resource summaries.
• team:read - view team members, roles, and the scope catalog.

Common endpoints:

• GET /v1/me loads your user, active customer, and effective scopes.
• POST /v1/me/switch-customer changes active customer context.
• GET /v1/scopes lists available scopes when your role can view team data.
• GET /v1/dashboard/stats reads dashboard statistics.
• GET /v1/customers/me/balance and GET /v1/customers/me/utilization read customer account summaries.

Fast Checklist

If you cannot find or use a feature:

1. Confirm you are in the right customer.
2. Confirm your role includes the needed read or write scope.
3. Try the page from the left navigation after switching customers.
4. Ask a customer admin to adjust your role if the missing access is expected.
5. Ask Buzz to identify the required scope for the page you are on.