EvidofOS frequently asked questions

No. Invite colleagues through the authorized membership workflow with access appropriate to their work. Separate accounts keep approvals and activity attributable.

Inspect the affected campaign and its saved public version. Profile information and campaign publication have separate review responsibilities; review changes before republishing.

Have your legal organization name, website, mission and logo available. Start with confirmed facts and use the Setup guide to identify the rest.

No. It confirms access to the email address. Organization identity, charitable status and payment-provider checks have separate purposes.

Yes, use the organization logo upload control. Review the image and save the profile; a public image URL is not required.

Enter the address manually. Search is optional. Check city, region, postcode and country, and add any suite or unit yourself.

Use the person’s organizational responsibility, such as Executive Director. Leadership category identifies staff, board or officer. Neither field needs an honorific such as Mr.

Review and select the suggestions you want, then save the profile. Suggested values, audiences and voice are drafts that need your organization’s judgment.

No. Draft recovery helps interrupted entry but may depend on the browser and device. Use Save changes and reopen the profile to confirm the committed values.

Start with the information you know and preserve gaps. Do not invent outcomes or dates. Review evidence before using factual claims publicly.

An Engagement engine uses campaign inputs and its timeline to prepare dated private content drafts. Inspect the generated package and calendar before approval or scheduling.

It anchors the phase timeline and the dates of planned content. Recheck the start and time-sensitive details when duplicating or restarting a campaign.

Generation prepares drafts. Approval, channel readiness and explicit publishing confirmation remain separate. Inspect delivery status for evidence that a provider received a post.

It is the four-part content framework: explain the issue, show the mission’s human side, invite participation and offer a clear action. It helps vary posts across a campaign.

A factual claim may lack support, use the wrong source or need validation after editing. Open the finding, correct the claim or evidence, save and revalidate.

Use campaign package review to inspect posts, media, links and dates together. Blocking findings must be resolved. Changed content needs renewed review; publishing prerequisites still apply.

The calendar includes planned and private drafts as well as delivery states. Check approval, connected account, media and publishing schedule, then inspect the provider result.

Select one primary Community Funding campaign. Check that the link or QR code reaches the intended published donation page, and retain the organization website where appropriate.

No. Runway is an optional tenant-configured service for finished AI video. Text and existing approved images do not require a Runway account.

No. Asset generation and network delivery are separate. Use the channel and format options shown; unsupported destinations may require manual handoff.

Yes. Complete the organization’s Stripe connection and onboarding. Evidof’s operator account collects payments for Evidof services and does not replace the nonprofit’s donation account.

The organization may not have completed its connection or required provider checks. Review Community Funding payment readiness and the error reference before retrying.

No. New campaign saves a private draft. Preview it and use the separate authorized publication action when ready.

Yes. Select the saved program or project in New campaign, then review the prefilled story, selected evidence and photos before saving.

Yes. Each published campaign has its own page and purpose. Offering another campaign as a donation designation does not merge the pages.

On a campaign page, it supports that campaign’s greatest need. It is not an automatic redirection to the organization’s general fund.

Only when it is eligible and explicitly opted into cross-campaign giving. Existing campaigns are excluded unless opted in.

Yes. Organization defaults can be overridden per campaign. Preview the public form to verify the saved amounts and accepted frequencies.

Use the campaign image editor to upload approved photos, add descriptions and choose available layout options. Preview the page, including how it looks without images.

The campaign transparency experience presents supported material over the donation page. Check the actual preview and document behavior before publishing.

Use the designated Stripe test environment for test transactions. Live payment accounts and test accounts are separate; do not enter test details into a live checkout.

No. Future installments have their own payment status. Use recorded transactions and provider outcomes instead of treating the full intended schedule as received funds.

No. It is an alignment signal. Review eligibility, current official terms, timing and organizational capacity before deciding to apply.

It supports what the program says it does. Measured outcomes need suitable evidence, a reporting period and a clear explanation of how they were measured.

Preserve the disagreement and ask the responsible person to resolve it. Do not choose the more attractive figure or combine incompatible counts.

No. Approval accepts a reviewed version. Submission requires the supported external workflow, delegated authority and the funder’s instructions.

Organization profiles, evidence, Community Funding and Engagement. Funding Operations requires an applicable paid plan or valid promotion; provider setup and permissions still apply.

Do not assume it does. Review the service agreement and provider terms. Payment processing, optional video and other third-party usage can be separate.

The screen, attempted action, expected result, exact error and relevant campaign or operation reference. Remove beneficiary details; never send passwords, verification codes or API keys.

Guidance explains workflows and can help prepare a support escalation. Account changes, approvals, publication and financial actions require the appropriate authorized product workflow.