Introducing and Using Team Seats

Team seats let you create separate subscription identities under one main service. Each seat gets its own credentials and subscription link, making it suitable for a team member, device group, automation task, or internal department.

A seat is not a separate billing service. It belongs to the main service and is managed inside the same product details page.

Important behavior Each seat has its own subscription link and usage statistics, but its traffic still counts toward the main plan quota. Seat limits do not replace the limits of the parent service.

1. What Is a Seat

A seat is a child subscription under your main service. It is useful when you want to issue separate subscription links for different users or systems without purchasing a completely separate service.

• Each seat has its own UUID and subscription link.
• Each seat has its own usage records and online session view.
• Each seat still belongs to the same parent service and follows the service's overall plan limits.

2. Before You Start

• Your service must include available seat capacity. If the seat limit has been reached, you cannot create more seats.
• Think about how you want to identify the seat before creating it. A clear label such as Alice, Sales Team, or CI Runner makes later management easier.
• You may optionally define a seat cap and a seat speed limit, but those settings do not override the parent service's global limits.
• If you plan to share the seat link with someone else, treat it as sensitive data and distribute it only to the intended user or system.

3. Core Seat Concepts

4. How to Create a Seat

1. Log into your Client Area and open your Product Details Page.
2. Open the Team seats section.
3. Click Create team seat.
4. Enter a clear Label for the seat.
5. Optionally set Quota (GB). Use 0 if you do not want a separate seat cap.
6. Optionally set Speed (Mbps). Use 0 if the seat should follow the main service speed limit.
7. Choose what should happen when a seat cap is reached: Pause this seat or Throttle this seat.
8. If you choose throttling, enter the throttle speed value.
9. Click Create.

Once created, the seat appears in the team seat list and can be managed independently from other seats under the same service.

5. How to Manage a Seat

1. Open the Team seats list in your product details page.
2. Click Details for the seat you want to manage.
3. Review the seat's UUID, masked subscription link, usage summary, and online status.
4. Use the View button to reveal the current subscription URL when needed.
5. Edit the seat label, optional quota, optional speed limit, and overage action.
6. Click Save to apply the changes.

6. Seat Actions

On the seat details page, you can perform several operational actions:

• Pause: Temporarily disables the seat without deleting it.
• Resume: Re-enables a paused seat, unless it is still locked because the seat cap was exceeded.
• Reset usage: Clears the seat usage counters for the current reset window.
• Reset link: Generates a new subscription link and credentials for that seat. Existing client configurations for the seat stop working until updated.
• Delete: Permanently removes the seat and its records.

7. Traffic and Online Status

Each seat includes its own monitoring pages and current usage summary:

• Traffic usage card: shows used traffic, seat cap, remaining traffic, and today's upload/download totals.
• Traffic log: shows seat-level hourly and daily traffic history.
• Online status: shows whether the seat is currently active and lists recent active sessions.
• Subscribe logs: records recent access to the seat's subscription URL.

These records help you understand how the seat is being used, but the usage still contributes to the parent service totals.

8. Seat Access Control

Each seat can have its own subscription access rules.

• You can enable an IP allowlist for the seat's subscription URL.
• When enabled, only listed IP addresses or CIDR ranges can download that seat's subscription.
• This seat-level policy overrides the main service IP allowlist for that specific seat.
• You can add remarks to each allowlist entry to make administration easier.

9. Important Notes and Limitations

• A seat is part of the parent service, not a standalone purchased product.
• Seat traffic always counts toward the main service quota.
• A seat cap is optional. Setting it to 0 means there is no separate seat cap.
• A seat speed limit is optional. Setting it to 0 means the seat follows the main service speed limit.
• The seat speed limit cannot exceed the main service speed limit.
• Seat reset scheduling is fixed to the parent service reset cycle and cannot be customized per seat.
• If a seat reaches its configured seat cap, the selected overage action is applied only to that seat, while the main plan policy still applies globally.

Recommended Workflow

1. Create one seat for each person, department, or automation system that needs its own subscription link.
2. Use clear labels so you can identify seats quickly in the list and logs.
3. Only set a seat cap when you want to enforce a separate limit for that specific seat.
4. Use Reset link only when a seat link may have been exposed or you intentionally need to rotate credentials.
5. Enable seat access control for sensitive seats that should download subscriptions only from fixed IPs or trusted networks.