Sub-Users Management

What are Sub-Users?

Sub-users allow you to organize and distribute your residential proxy data across multiple accounts under your main account. This is perfect for:

Key Benefits

✅
Team Management: Create separate accounts for team members
✅
Project Organization: Isolate different projects or clients
✅
Data Control: Allocate specific amounts to each sub-user
✅
Usage Tracking: Monitor consumption per sub-user
✅
Security: Separate credentials for different use cases

How Sub-Users Work

•Main Account: Your primary account that purchases residential data
•Sub-Users: Separate proxy accounts created under your management
•Data Allocation: Data is transferred from your main account to each sub-user
•Individual Credentials: Each sub-user gets completely unique credentials (ID and password)
•Unified Billing: All usage is tracked under your main account

Example Use Case

You buy 100GB of residential data and create:

•Sub-user A: 30GB allocation (Web scraping project)
•Sub-user B: 40GB allocation (Social media automation)
•Sub-user C: 20GB allocation (Market research)
•Remaining: 10GB buffer for your main account

Each sub-user gets their own credentials and can only use their allocated amount.

Creating Sub-Users

Step-by-Step Guide

Step 1: Access Sub-Users Section

•Login to your BirdProxies dashboard
•Navigate to Dashboard → Residential Proxies
•Click the "Sub-Users" tab

Step 2: Create New Sub-User

•Click the "Create Sub-User" button
•Fill in the required information:

- Username: Unique identifier for the sub-user

- Data Allocation: Amount of GB to allocate (from your available data)

- Description (optional): Notes about this sub-user's purpose

Step 3: Confirm Creation

•Review the allocation details
•Click "Create Sub-User" to confirm
•The sub-user will be created instantly with unique credentials

Step 4: Get Sub-User Credentials

•Each sub-user receives unique credentials:

- Username: Unique identifier (displayed in dashboard)

- Password: Unique password (generated automatically)

- Endpoint: Same residential endpoints

- Port: Same ports (8080, 8081, etc.)

Important Notes

•⚠️ Data Requirement: You must have available unused data to allocate to sub-users
•🔄 Instant Creation: Sub-users are created immediately with separate accounts
•📊 Real-time Tracking: Usage is tracked in real-time for each sub-user
•💡 Unique Credentials: Each sub-user has completely independent login credentials

Managing Sub-Users

Data Allocation Management

Viewing Current Allocation

•See all sub-users and their data limits in the dashboard
•Monitor usage in real-time
•Track remaining data for each sub-user

Modifying Allocations

•Click the "Edit" button next to any sub-user
•Increase or decrease their data allocation
•Changes are applied immediately

Data Transfer Between Sub-Users

•Use the "Transfer Data" feature
•Data is first removed from source sub-user
•Then added to destination sub-user
•Useful for rebalancing allocations mid-project

Bulk Operations

Bulk Data Split

•Select multiple sub-users
•Choose "Split Data Equally" or "Custom Split"
•Redistribute your available data across selected sub-users

Bulk Creation

•Create multiple sub-users at once
•Upload a CSV file with sub-user details
•Automatically allocate data based on your specifications

Bulk Deletion

•Select multiple sub-users to delete
•Reclaim their allocated data back to your main account
•Useful for cleaning up unused sub-users

Individual Sub-User Actions

View Details

•Click on any sub-user to see:

- Total data allocated

- Data consumed

- Usage history

- Connection statistics

Pause/Resume

•Temporarily disable a sub-user without deleting
•Paused sub-users cannot make new connections
•Resume anytime to restore functionality

Reset Usage

•Reset usage statistics for a sub-user
•Useful for monthly reporting cycles
•Does not affect actual data consumption

Using Sub-User Credentials

Credential Format

Each sub-user receives completely unique credentials:

Username: Unique ID assigned to the sub-user

Password: Unique password generated for the sub-user

Endpoints: Same as main account (residential.birdproxies.com)

Ports: 8080, 8081, 8082, 8083, 8084

Example Connection

When you create a sub-user, you'll receive credentials like:

•Username: `65f8a9b2c3d4e5f6`
•Password: `xK9mN2pQ5rT8`

bash

# cURL example
curl -x http://65f8a9b2c3d4e5f6:[email protected]:8080 https://httpbin.org/ip

# Python example
proxies = {
    'http': 'http://65f8a9b2c3d4e5f6:[email protected]:8080',
    'https': 'http://65f8a9b2c3d4e5f6:[email protected]:8080'
}

Authentication

•Unique Passwords: Each sub-user has its own password
•Independent Accounts: Sub-users are separate proxy accounts
•Real-time Limits: Connection will fail if sub-user exceeds their allocated data
•Shared Endpoints: All sub-users use the same proxy endpoints as your main account

Testing Sub-User Connections

Quick Test Script (Python):

python

import requests

def test_sub_user(username, password):
    proxies = {
        'http': f'http://{username}:{password}@residential.birdproxies.com:8080',
        'https': f'http://{username}:{password}@residential.birdproxies.com:8080'
    }
    
    try:
        response = requests.get('https://httpbin.org/ip', proxies=proxies, timeout=10)
        print(f"✅ Sub-user {username} working: {response.json()['origin']}")
        return True
    except Exception as e:
        print(f"❌ Sub-user {username} failed: {e}")
        return False

# Test your sub-users with their unique credentials
sub_users = [
    {"username": "65f8a9b2c3d4e5f6", "password": "xK9mN2pQ5rT8"},
    {"username": "78g9b0c3d4e5f7h8", "password": "yL3nP4qR6sT9"},
    {"username": "89h0c1d4e5f6g7i9", "password": "zM5oQ7rS8uU0"}
]

for sub in sub_users:
    test_sub_user(sub["username"], sub["password"])

Sub-User Best Practices

Naming Conventions

Use Descriptive Names:

✅`web_scraping_project_a`
✅`social_media_automation`
✅`market_research_team`

❌ test1, user2, temp

Follow Consistent Patterns:

•Project-based: `project_[name]`
•Team-based: `team_[name]`
•Client-based: `client_[name]`
•Purpose-based: `[purpose]_[date]`

Data Allocation Strategy

Conservative Allocation:

•Start with smaller allocations
•Monitor usage patterns
•Increase as needed
•Keep 10-20% buffer in main account

Project-Based Allocation:

•Estimate project data needs
•Add 20% buffer for unexpected usage
•Monitor closely in first week
•Adjust based on actual consumption

Team-Based Allocation:

•Allocate based on team size and workload
•Consider peak usage periods
•Set up alerts for high consumption
•Regular review and rebalancing

Security Best Practices

Credential Management:

•Store each sub-user's unique credentials securely
•Document which sub-user is used for what purpose
•Keep credentials in password managers or secure vaults
•Remove unused sub-users promptly to reclaim data

Access Control:

•Create sub-users for specific purposes only
•Don't share sub-user credentials across projects
•Monitor usage patterns for anomalies
•Use descriptive names for easy identification

Monitoring and Maintenance

Regular Reviews:

•Weekly usage review for active projects
•Monthly cleanup of unused sub-users
•Quarterly rebalancing of data allocations
•Annual audit of all sub-user accounts

Usage Alerts:

•Set up notifications for high usage
•Monitor for unusual traffic patterns
•Track data consumption trends
•Plan for scaling needs

Documentation:

•Keep records of sub-user purposes
•Document data allocation reasoning
•Track project timelines and data needs
•Maintain credential sharing logs

Common Scenarios

Development vs Production:

•`dev_project_a`: 5GB for development/testing
•`prod_project_a`: 50GB for production workload

Team Segregation:

•`team_frontend`: Web scraping for frontend data
•`team_backend`: API testing and integration
•`team_qa`: Quality assurance testing

Client Management:

•`client_acme_corp`: Dedicated allocation for Acme Corp project
•`client_beta_inc`: Separate allocation for Beta Inc work

Seasonal Projects:

•`q4_holiday_scraping`: Temporary high-volume allocation
•`annual_report_data`: One-time data collection project

BirdProxies

On this page