I have an idea
Create a private draft, add the need, location, timeframe, and help wanted, then make it public only when you are ready for collaboration.
All These YDays
Community workspace user guide
Use this guide to create an idea, invite the right people, coordinate a project, and share progress without exposing private workspace information.
Start here
Create a private draft, add the need, location, timeframe, and help wanted, then make it public only when you are ready for collaboration.
Create a profile, invite authorized teammates, and decide who may represent the organization in ideas and projects.
Browse public needs and volunteer roles, submit a response or application, and track invitations and service from your dashboard.
1. Account and dashboard
Your account email and private contact details are not placed on public idea or project pages.
2. Organizations
Add the organization type, description, service area, capabilities, interests, public contact details, and an optional logo. Choose private or public visibility deliberately.
From View team, an owner can invite members, assign owner, admin, or member access, and separately decide whether a person may represent the organization. Invitees accept or decline from their own dashboard.
A public profile is not automatically verified. Only a platform administrator can apply the verified status after reviewing the required evidence.
3. Ideas and projects
There is no self-service ownership transfer. If an idea or project belongs to the wrong account, use the contact form. Include the current account, destination account, and item title. Support must verify both the requester and the destination before changing ownership.
4. Project workspace
Invite people into project roles and invite organizations through their authorized representatives. Pending invitations reveal no private workspace content. Organization representatives can ask questions before accepting.
Post structured resource needs, review private responses, move responses through their status steps, and assign lightweight tasks. Only make a need public when the wider community should see it.
Link an existing event or submit one from the workspace. Linking a project does not change the event owner or silently grant event-edit access.
Publish updates for internal participants or the public. Public updates appear only when both the update and parent project are eligible for public display.
5. Volunteers and community partners
Open a public need, sign in, and respond personally or through an organization you are authorized to represent. The response message and your identity remain private to authorized organizers and administrators.
Review the role, dates, location, skills, and requirements before applying. An application is not an automatic qualification, background clearance, or acceptance.
Authorized coordinators can record service, volunteers can review their own history and request corrections, and verified records can be downloaded as an operational CSV.
6. Planning money and reporting impact
Finance-authorized roles can track estimated budget, confirmed funding, actual expenses, and projected remaining need. These are private planning records, not bank or accounting records.
Record monetary or in-kind support for planning and optionally approve a contributor name for public recognition. Values and private contributor details never appear in the public recognition view.
Record outcome metrics with a source note, confirmation status, and visibility. Only confirmed public metrics on an eligible public project appear on public project, organization, and impact pages; private source notes stay private.
7. Privacy and current limits
Questions, corrections, suspected misuse, and account ownership requests can be sent through the contact form.
Ready for the next step?