Portal Admin Guide
System administration and configuration guide
As a Portal Administrator, you have full access to system configuration, user management, integrations, and monitoring capabilities. This guide covers all administrative functions.
Admin Permissions
Admin functions can significantly affect system operations. Always double-check before making changes to user roles, integrations, or billing settings.
User Management
Managing Users
Access user management at /admin/users.
User Roles
Customer
- • Order sample kits
- • Submit samples
- • View own orders/reports
- • Manage own profile
Lab Technician
- • Process kit orders
- • Manage samples
- • Update workflows
- • Generate reports
Admin
- • All Lab Tech permissions
- • Manage users
- • Configure integrations
- • System settings
Creating a Lab Technician
Navigate to Users
Go to Admin Dashboard → Users.
Click "Add User"
Open the new user creation form.
Enter Details
Fill in name, email, and set role to "Lab Technician".
Set Company Assignment
Assign the lab tech to a company for access control.
Company Settings
Company Configuration
Companies are automatically created based on user email domains. Users with the same email domain are grouped together.
Company Data
- • Company name
- • Billing address
- • Contact information
- • Custom branding (if enabled)
Company Users
- • View all users in company
- • Manage user permissions
- • View company orders
- • Access company reports
Domain-Based Grouping
Users with @company.com emails are automatically grouped. This helps customers within the same organization share access to orders and reports.
Integration Setup
Available Integrations
UPS Shipping
Configured via EnvironmentAutomated shipping label generation and tracking updates.
Features:
- • Automatic label creation
- • Real-time tracking updates
- • Delivery confirmation
- • Return label generation
QuickBooks
OAuth ConnectionAutomated invoicing and payment processing.
Features:
- • Automatic invoice creation
- • Payment tracking
- • Customer sync
- • Financial reporting
Security Notice
Integration credentials (API keys, secrets, OAuth tokens) are stored securely in environment variables and are never exposed in the UI. Contact your system administrator for credential configuration.
Billing Configuration
Pricing Management
Access pricing configuration at /admin/pricing.
Default Pricing
Extracted DNA
$65
per sample
Plant Material
$70
per sample
Viable Seed
$75
per sample
Invoice Management
- View all invoices at /admin/invoices
- Track payment status
- Send payment reminders
- Export financial reports
System Monitoring
Dashboard Metrics
The admin dashboard provides real-time visibility into system operations:
📊 Order Statistics
- • Active kit orders
- • Pending shipments
- • Samples in processing
- • Reports awaiting delivery
⚠️ Error Monitoring
- • UPS shipping errors
- • Failed invoices
- • Integration issues
- • System alerts
Automated Processes
- Delivery Checks: UPS tracking updates run every 4 hours
- Email Notifications: Sent automatically at key workflow stages
- Invoice Sync: QuickBooks sync runs after order completion
Security Settings
Security Features
Authentication
- • JWT-based authentication
- • Secure password hashing
- • Token expiration
- • Email verification
Data Protection
- • HTTPS encryption
- • Role-based access control
- • Data isolation per company
- • Audit logging
Password Requirements
- • Minimum 8 characters
- • At least one uppercase letter
- • At least one lowercase letter
- • At least one number
- • At least one special character
Credential Security
Never share API keys, passwords, or OAuth tokens. All credentials should be stored in environment variables, not in code or documentation. If credentials are compromised, rotate them immediately.
Best Practices
Do's
- Regularly review user access permissions
- Monitor integration health daily
- Keep lab address information up-to-date
- Test integrations after any configuration changes
- Respond promptly to shipping errors
Don'ts
- Share admin credentials with others
- Ignore error notifications
- Delete users with active orders
- Store credentials in documentation
- Make changes without testing first