Branding

1. 1

   Load the shared branding record

   Branding settings are loaded through feature queries before the admin form renders.

   Relevant Product code

   • src/features/branding/server/queries.ts
2. 2

   Validate form and media inputs

   Form and upload helpers constrain appearance values and accepted media before writes.

   Relevant Product code

   • src/features/branding/shared/settings.ts
   • src/lib/uploads/media-types.ts
3. 3

   Write through the repository

   Brand updates are centralized in the branding repository so public and admin behavior stay aligned.

   Relevant Product code

   • src/features/branding/server/actions.ts
   • src/features/branding/server/repository.ts
4. 4

   Re-check public surfaces

   Marketing header, auth surfaces, dashboard shell, metadata, logo, and favicon should reflect the updated values.

   Relevant Product code

   • src/features/branding/ui/form.tsx

Use this example as a starting point, then adapt it to your product's rules and configuration.

Branding writes require an authenticated profile, non-read-only access, and branding permission.

export async function updateBrandingSettings(formData: FormData) {
  const supabase = await getServerSupabase();
  const profile = await getActiveProfile();
  if (!profile) {
    return { success: false, message: "User not authenticated" };
  }

  if (hasReadOnlyAccess(profile)) {
    return { success: false, message: "This account has read-only access and cannot make changes." };
  }

  const hasAccess = await canAccessAsync(profile.role, "branding");
  if (!hasAccess) {
    return { success: false, message: "Unauthorized: Super Admin access required" };
  }