> ## Documentation Index > Fetch the complete documentation index at: https://docs.wegive.com/llms.txt > Use this file to discover all available pages before exploring further. # Organization Settings > WeGive Help Center article: Organization Settings Your Organization Profile is where you manage the core identity, contact information, and key feature settings for your nonprofit within WeGive. These details power everything from your donor-facing portal to your receipts and email communications — so keeping them accurate is important. You can find your Organization Profile under **Settings > Organization** in the WeGive dashboard. ## Organization Identity These fields define who your organization is within the WeGive platform. **Legal Entity Name** — Your organization's official legal name. This is typically set during onboarding and managed by WeGive support. It appears on tax receipts and legal documents. **Doing Business As (DBA)** — The public-facing name your donors see. If your legal name is different from how donors know you (for example, "Greater Metro Community Foundation" vs. "GiveMetro"), set your DBA here. This name is used across checkouts, the donor portal, and email communications. **EIN (Employer Identification Number)** — Your organization's tax identification number. This appears on tax receipts and is required for payment processing compliance. ## Address Your organization's mailing address is used on tax receipts and other official correspondence. The address form includes the following fields: * Street Address * City * State * Postal Code * Country (defaults to US) ## Contact Information These contact details determine how donors and the WeGive platform communicate with your organization. **Support Email** — The public-facing email address shown to donors when they need help. This appears on checkout pages, receipts, and in the donor portal. **Donor Relations Email** — A separate email for donor relations correspondence. Use this if you want donor-specific communications to go to a different inbox than general support. **Support Phone Number** — Your organization's phone number, available to donors who prefer to call. **Website URL** — Your organization's website. This is linked in donor-facing materials. ## Timezone Set your organization's timezone to ensure that donation timestamps, scheduled communications, and reporting all reflect the correct local time. This setting affects how dates and times are displayed throughout the dashboard and in donor communications. ## Mission Statement A text field for your organization's mission statement. This can be displayed on your donor portal to help donors understand your purpose and impact. ## Feature Toggles The Organization Profile includes several feature-level settings that control important platform behaviors. ### Dunning Flow When enabled, WeGive automatically sends reminder emails to donors whose recurring donation payments have failed — the "Recurring Installment Failed #1–4" notice chain. The dunning flow sends periodic reminder emails giving donors an opportunity to update their payment method and recover the failed transaction. Toggle this off if you prefer to handle failed payment follow-ups manually. ### Stripe for Apple Pay / Google Pay Only When enabled, your connected Stripe account is used exclusively to process Apple Pay and Google Pay transactions, while your primary processor (WeGive's native Payrix/Finix processing) continues to handle standard card and ACH payments. This is the setting behind the hybrid configuration described in the payment processor documentation. ### Transaction Tracking URL When enabled, this feature tracks which specific checkout form a transaction originated from. This is useful for measuring the performance of different fundraising sources — for example, comparing donations from your website checkout versus an email campaign checkout. A related **UTM Attribution Window (hours)** setting controls how long the attribution cookie persists. ### Engagements for Integrations This toggle controls whether triggered emails (such as donation confirmations and receipts) are sent for transactions that come in through external integrations. If your organization syncs transactions from another system and you don't want WeGive to send duplicate confirmation emails for those, turn this off. Note: in the backend, this setting uses inverted logic — the on-screen toggle labeled "Engagements for Integrations" maps to a `disable_engagement_events_for_integrations` field under the hood. What you see in the dashboard is the intended behavior: toggling it on means engagement emails will be sent for integration transactions, and toggling it off means they won't. ### Other settings on this page A few additional, more technical settings also live on the Organization Profile page: * **Access Token Lifetime** — how long API personal access tokens remain valid before expiring (set to no expiry if left at `0`). * **Engagement Processing Delay** — a delay applied before triggered engagement emails (receipts, confirmations, etc.) go out. * **Default Brand** — which organization brand is used by default when no other brand is specified. * **Recurring Plan Limit** — a cap on recurring plans tied to a brand. * **Hide Inactive Designations** — hides archived/inactive funds from designation pickers across the dashboard and donor-facing forms. ## Saving Changes When you make changes to your Organization Profile and click save, WeGive displays a review modal that shows a before-and-after comparison of every field you modified. This gives you a chance to verify your changes before they go live. You can confirm and save, or go back to keep editing. If you navigate away from the page with unsaved changes, you'll be prompted to either discard your changes or continue editing. ## Where Organization Profile Data Appears The information in your Organization Profile isn't just internal — it flows into many parts of the donor experience: * **Checkout pages** display your DBA name, logo, and brand colors * **Tax receipts** include your legal name, EIN, and address * **Donor portal** shows your logo, colors, favicon, tab header, and mission statement * **Email communications** reference your support email and organization name * **Recurring donation failure emails** (when dunning is enabled) come from your organization's contact info This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.