Brand and Organization Applications - Admin Operations Guide

Published by Give.Gives · Updated April 2, 2026

Brand and Organization Applications - Admin Operations Guide

1. Purpose and Scope

This guide explains how the Give.Gives operations team should handle:

• Brand applications

• Organization applications

It covers:

• what happens when an application is submitted

• what AI pre-analysis does before human review

• what admins should evaluate before approving or rejecting

• what happens after approval or rejection

This is a combined workflow guide for the platform's application intake process.

2. Application Intake Overview

When the platform receives a new application, the operational flow is:

1. The applicant submits a Brand or Organization application.

2. The system stores the application record.

3. The applicant receives a confirmation email.

4. The system runs an AI pre-analysis in the background.

5. If the submission is identified as obvious spam, it may be auto-rejected.

6. All non-obvious cases remain available for admin review.

7. Admin reviews the application and decides whether to approve or reject it.

This means AI is a screening layer, not the final authority for normal cases.

3. Where to Review Applications

Brand Applications

Go to Brands > Applications in the admin sidebar.

Organization Applications

Go to Organization Management > Applications in the admin sidebar.

[Placeholder: Screenshot of the Brand Applications list page]

[Placeholder: Screenshot of the Organization Applications list page]

4. What AI Pre-Analysis Does

The application review flow includes AI pre-analysis for both Brands and Organizations.

Inputs AI reviews

For Brand applications, AI reviews:

• brand name

• email

• industry

• website

• slogan

• description

• logo image, if provided

For Organization applications, AI reviews:

• organization name

• email

• website

• description

• logo image, if provided

What AI returns

AI produces these fields:

• isSpam

• spamSeverity

• priority

• reason

How AI is supposed to behave

The AI policy is intentionally conservative:

• it should mark an application as spam only when the spam signal is obvious

• if the case is uncertain, weak, incomplete, or low quality, AI should not auto-reject it

• unclear or borderline cases should still go to human review

What counts as obvious spam

AI is meant to flag only clearly bad cases such as:

• explicit illegal or inappropriate content

• scams, phishing, fraud, or impersonation

• obvious junk text or nonsense submissions

• clearly unrelated commercial spam with no real application intent

Short text, imperfect English, weak branding, or missing website should not be treated as automatic spam by themselves.

Priority meaning

AI also marks an application as high or low priority.

This is only a triage signal:

• High priority means the submission appears more promising, more complete, or more mission-aligned

• Low priority means the submission does not stand out strongly, but it is still not necessarily a rejection case

Important rule

AI does not decide normal approvals.

The only automatic rejection behavior is for cases classified as:

• isSpam = true

• spamSeverity = obvious

All other applications should be reviewed by an admin.

5. What Admin Should Judge Manually

Before approving any application, the admin should make a real business and operational judgment.

Use the AI result as a shortcut for triage, not as a substitute for review.

Core questions for both Brand and Organization applications

Check whether:

• the applicant appears to be a real, legitimate entity

• the person submitting seems authorized to represent that entity

• the description is coherent and aligned with the platform

• the email and website appear credible

• the materials create any legal, operational, fraud, or reputational concern

• the application appears workable for the platform rather than just interesting in theory

If the answer is unclear, do not approve just because the application is not spam.

6. How to Review Brand Applications

What the Brand application page shows

Brand applications include fields such as:

• brand name

• email

• industry

• slogan

• website

• description

• logo

• preferred organization partner (ngoIntent), if selected

• requested transparency share

• AI spam result

• AI priority

• AI reasoning

[Placeholder: Screenshot of the Brand Application detail dialog]

What admins should evaluate for Brand applications

When reviewing a Brand application, check:

• whether the business looks real and lawful

• whether it sounds like a physical, operationally suitable brand for the platform

• whether the description shows a realistic understanding of participation

• whether the contact information appears credible

• whether the website and branding are broadly consistent with the submission

• whether the requested transparency share is reasonable for platform policy

• whether the preferred organization intent makes sense, if one was selected

Special caution for Brand applications

A Brand application approval does not automatically create the Brand record in the main Brand database.

Operationally, approval means:

• the application is approved

• the applicant is notified

• the admin must then use the approved application as the source to pre-fill and manually complete Brand creation

In practice, this means there are two steps:

1. approve the Brand application

2. create the actual Brand record in admin, using the application as source data

This is one of the most important differences between Brand and Organization approvals.

Required follow-up after Brand approval

After approving a Brand application, do not assume onboarding is finished.

Operations should check the page's action required prompt and manually complete Brand creation from the approved application.

Once the Brand is actually created:

• the manager account onboarding flow is triggered

• the manager's username and temporary password are sent automatically by email

So the correct operational sequence is:

1. approve the application

2. follow the action required guidance

3. manually create the Brand record

4. let the system send manager login credentials automatically after creation

When to reject a Brand application

Common rejection reasons include:

• the business does not appear legitimate

• the applicant is not credible or appears unauthorized

• the submission is too inconsistent or risky to onboard

• the application does not fit the platform's operating model

• the information is too weak to support approval even after review

Reject with a clear reason, because the system sends that reason to the applicant.

7. How to Review Organization Applications

What the Organization application page shows

Organization applications include fields such as:

• organization name

• email

• website

• mission description

• location

• bank account name

• bank address

• bank account number

• bank routing number

• logo

• AI spam result

• AI priority

• AI reasoning

[Placeholder: Screenshot of the Organization Application detail dialog]

What admins should evaluate for Organization applications

When reviewing an Organization application, check:

• whether the organization appears legitimate and mission-aligned

• whether the mission description is coherent and credible

• whether the website and contact identity appear real

• whether the organization seems suitable for public association with the platform

• whether the provided banking details are present and sensible if settlement is expected

• whether there are legal, fraud, or reputation concerns

Banking judgment matters

For Organizations, banking readiness is especially important because approved organizations may need to receive settlement through the platform.

Admins should pay attention to whether:

• the applicant provided usable account-holder information

• the bank details appear consistent with an organization rather than a personal payout setup

• the submission is operationally ready for payout-related onboarding

What happens when an Organization application is approved

Unlike Brand applications, approving an Organization application triggers a direct onboarding flow:

• the Organization record is created automatically

• an Organization admin account is created or reset automatically

• login credentials are emailed to the Organization admin email

This means Organization approval has immediate system effects and should be treated with extra care.

When to reject an Organization application

Common rejection reasons include:

• legitimacy concerns

• unclear or unsuitable mission

• verification concerns

• weak or risky banking/setup information

• broader legal or reputational risk

Reject with a clear explanation because that rejection reason is sent to the applicant.

8. Auto-Rejection vs Human Review

Auto-rejection

The system may auto-reject only when AI marks the application as:

• spam

• with obvious spam severity

In those cases:

• the application status becomes rejected

• the AI reason is stored

• the applicant receives a rejection email

Human review

Everything else should be treated as a human review queue, including:

• low-quality but plausible submissions

• incomplete but believable applications

• unusual but not clearly bad applications

• any case where AI marked low priority but not obvious spam

This distinction is critical. The system is designed to be strict on obvious spam but cautious on uncertain cases.

9. Approval and Rejection Outcomes

Brand approval outcome

When a Brand application is approved:

• the application status becomes approved

• the applicant receives an approval email

• the actual Brand record still needs to be created separately in admin

• operations must follow the page's action required reminder and manually create the Brand

• after Brand creation, the manager's username and temporary password are emailed automatically

Brand rejection outcome

When a Brand application is rejected:

• the application status becomes rejected

• the rejection reason is stored

• the applicant receives a rejection email

Organization approval outcome

When an Organization application is approved:

• the application status becomes approved

• the Organization record is created

• an Organization admin account is created or reset

• login credentials are sent by email

Organization rejection outcome

When an Organization application is rejected:

• the application status becomes rejected

• the rejection reason is stored

• the applicant receives a rejection email

10. Practical Review Checklist

Use this checklist before approving:

For Brand applications

Confirm:

• the brand appears real

• the contact information is credible

• the applicant seems authorized

• the business fits the platform's physical and operational model

• the description is coherent

• the requested setup does not create obvious policy or risk problems

For Organization applications

Confirm:

• the organization appears real and suitable

• the mission is aligned and understandable

• the contact identity is credible

• the website supports the claim where possible

• banking information is sufficiently usable if payout onboarding is expected

• the organization is appropriate for platform association

11. Day-to-Day Operations Suggestions

• Use AI results to sort and prioritize, not to replace judgment.

• Review all non-obvious cases manually.

• Reject with clear reasons, because those reasons are applicant-facing.

• Be especially careful when approving Organizations, because approval immediately creates live records and admin access.

• Remember that Brand approval is not the same as Brand creation. The actual Brand still needs to be created in admin afterward.

• If an application feels suspicious but not clearly spam, keep the decision in human review rather than forcing an AI-style rejection.