Partner Management Guide
This guide covers the complete partner lifecycle from initial onboarding to ongoing support.Partner Onboarding Process
Step 1: Create Organization & Entity
1
Navigate to Partner Management
Internal Dashboard → Partner Management → Create New Partner
2
Create Organization
3
Create Entity
Step 2: Generate Invitation
1
Find Created Entity
The entity appears in Partners list with “Pending” status
2
Generate Code
Click “Generate Code” and enter:
- Admin email (MUST match signup email)
- Expiry (default 7 days)
3
Share Securely
Copy invitation URL and send via:
- Secure email
- Scheduled call
- Partner portal
Step 3: Partner Activation
The partner will:- Visit invitation URL
- Create account with matching email
- Automatically become entity admin
- Complete profile setup
Example Organization Structures
- University
- High School
- Company
Support Workflows
Common Support Tickets
Can't Log In
Can't Log In
Troubleshooting Steps:
- Verify email in
partner_userstable - Check for typos (case-sensitive)
- Test password reset flow
- Check auth logs for errors
Missing Features/Permissions
Missing Features/Permissions
Troubleshooting Steps:
- Check role and permissions
- Verify entity is visible
- Confirm affiliation exists
Can't Invite Team Members
Can't Invite Team Members
Common Causes:
- User lacks admin/manage_team permission
- Entity relationship issue
- Invalid email format
- Verify user has admin role
- Check entity exists and is active
- Test with different email
- Generate manual invitation if needed
No Analytics Data
No Analytics Data
Troubleshooting Steps:
- Check for student interactions
- Verify date range
- Confirm entity linkage
Ticket Response Templates
Initial Response
Information Request
Resolution Confirmation
Database Troubleshooting
Key Queries
Escalation Guide
When to Handle Yourself
- Password resets
- Permission updates
- Basic troubleshooting
- Invitation regeneration
When to Escalate
- Database corruption
- Missing foreign keys
- Auth system issues
- Feature bugs
- Security concerns
Escalation Process
- Document all troubleshooting steps
- Include relevant queries/results
- Create detailed GitHub issue
- Tag in #partner-support channel
- Follow up with engineering
Best Practices
Always Verify
Confirm partner identity before making account changes
Document Actions
Log all support actions in ticket system
Test First
Try fixes on test accounts before production
Follow Up
Check back after 24 hours to ensure issue resolved
Quick Reference
Priority Response Times:- 🔴 Urgent: 1 hour
- 🟡 High: Same day
- 🟢 Normal: 24 hours
- ⚪ Low: 48-72 hours
- Login problems → Check email/auth
- Missing features → Verify permissions
- No data → Check interactions
- Can’t invite → Confirm admin role