28 lines
980 B
Markdown
28 lines
980 B
Markdown
|
# Customize Organization Branding
|
||
|
|
|
||
|
|
**ID:** ORG-004
|
||
|
|
**Priority:** Medium
|
||
|
|
**Status:** Planned
|
||
|
|
|
||
|
|
## User Story
|
||
|
|
As an organization owner, I want to customize the branding of my organization's login and account pages so that my team sees our company identity when authenticating.
|
||
|
|
|
||
|
|
## Acceptance Criteria
|
||
|
|
- [ ] Upload organization logo
|
||
|
|
- [ ] Set primary and secondary brand colors
|
||
|
|
- [ ] Custom login page welcome message
|
||
|
|
- [ ] Organization name displayed on login/register
|
||
|
|
- [ ] Preview branding changes before saving
|
||
|
|
- [ ] Reset to default branding option
|
||
|
|
- [ ] Branding applies to email templates (org-specific emails)
|
||
|
|
|
||
|
|
## Technical Notes
|
||
|
|
- Organization model needs branding fields (logo URL, colors, message)
|
||
|
|
- Frontend components need to accept branding props
|
||
|
|
- Email templates should support organization branding
|
||
|
|
- Consider white-label subdomain support (org.idp.global)
|
||
|
|
- Image storage similar to user avatars (EU-008)
|
||
|
|
|
||
|
|
## Related TODOs
|
||
|
|
- New feature - no existing infrastructure
|