e3 Users Management
Overview
The users interface in the cloud storage dashboard allows you to create and manage multiple storage users, their access permissions, and API credentials.
Understanding Users vs Subusers
Primary Users
Main account holders with full access to all their buckets
Can create and manage their own buckets
Can create and manage subusers under their account
Subusers
Secondary accounts created under a primary user
Have restricted permissions (Read-only, Write, Full Access, etc.)
Useful for team collaboration and access control
Ideal for employees, contractors, or third-party integrations
Why Use Subusers?
Security: Grant minimal necessary permissions
Organization: Separate access for different team members
Billing: All subuser activity falls under the primary user's account
Control: Primary user maintains oversight of all subuser activities
Compliance: Easier to audit and manage access across teams
User Isolation & Security Architecture
Complete Account Isolation
Each user in the system operates as a completely isolated account with strict boundaries:
Isolated Storage: Users can only access their own buckets and data
Scoped Credentials: API keys grant access exclusively to the owning user's resources
Independent Namespaces: User buckets exist in separate virtual environments
No Cross-Access: No user can view, modify, or access another user's data
Access Key Scope & Limitations
User-Specific Keys: Each API key pair only works for the user who owns it
Subuser Inheritance: Subuser keys can only access their parent user's resources (with permission restrictions)
Use Cases
Storage Resellers
Perfect for service providers who need to offer isolated storage to multiple customers:
Reseller: Creates separate users for each of their customers
Customer A: Gets their own user account with dedicated API keys
Customer Isolation: Each client's data is completely separate
Independent Billing: Track usage per customer easily
Branded Access: Provide customers with their own credentials
Scalable Management: Add new customers without affecting existing ones
Security Assurance: Guarantee customers their data is private and isolated
Enterprise Multi-Department Use
Large organizations with multiple departments or divisions:
Marketing Department: Separate user with their own buckets and keys
Development Team: Isolated environment for application data
Finance Department: Secure, separate storage for sensitive documents
External Partners: Controlled access without exposure to internal data
Software-as-a-Service (SaaS) Providers
Application developers serving multiple clients:
Each SaaS Customer: Gets dedicated storage user account
Application Integration: Uses customer-specific API keys
Data Sovereignty: Customer data never mixes with other customers
Compliance Ready: Meets data isolation requirements for regulations
Managed Service Providers (MSPs)
IT service companies managing multiple client infrastructures:
Client Separation: Each managed client gets isolated storage
Service Boundaries: Clear separation between different client services
Access Control: Granular control over which technicians access which clients
Audit Trails: Per-client activity logging and monitoring
Getting Started with Multi-User
Creating Users
Click the "+ Create User" button
Fill in required user information
Confirm user creation
User Actions
Click on a user row to access additional options:
Generate API Keys (Green): Create new access credentials
Create Subuser (Blue): Add a restricted user account
Delete User (Red): Remove user and all associated data
Bulk Operations
Select Multiple Users: Check boxes next to usernames
Bulk Delete: Remove multiple users simultaneously
Select All Toggle: Quickly select/deselect all visible users
Expanded User Details
Click any user row to reveal detailed information in two main sections:
API Keys Section
Purpose: Manage programmatic access credentials for applications and integrationsFeatures:
Generate API Keys: Create new access/secret key pairs
Decrypt Keys: View actual key values (password protected)
Hide Keys: Secure sensitive credentials from view
Copy Keys: One-click clipboard copying
Delete Keys: Remove compromised or unused credentials
Security:
Keys are encrypted and require password verification to view
All key operations are logged for security auditing
Keys can be hidden immediately after use for enhanced security
Subusers Section
Manage team members and restricted access accounts
Create Subuser: Add new restricted accounts
Permission Levels: Set appropriate access rights
Subuser API Keys: Independent credential management
Last updated
Was this helpful?