Community guidelines

The ORGanizer community — the Ideas board, the Salesforce news, the polls, the surveys, the comments and the members' profiles, here and in the extension's panel — is where Salesforce people shape the extension they use every day and talk about the platform. A few simple rules keep it useful for everyone.

1. Be kind and respectful

Discuss ideas, not people. No insults, harassment, threats, or discrimination of any kind.
Assume good faith: many members do not write in their first language, and a short comment is not necessarily a rude one.
Disagree with arguments, and keep the tone you would use with a colleague.

2. Stay on topic

Ideas are about ORGanizer: what it should do next, or do better.
A comment is about what it sits under: the idea, the article or the poll.
Bugs and questions about your license belong on the Support page, where they get an answer much faster than in a comment.

3. Propose ideas that can be acted on

Search the board first: if your idea is there already, vote for it and add what is missing in a comment, rather than proposing it again.
One idea per proposal, with a title that says what it is.
Describe the problem you have, not only the solution you picture: it helps find the best way to solve it.
Every idea is reviewed before it is published. An idea may be declined, or edited for clarity, and no idea comes with a promise that it will be built.

4. Vote fairly

One person, one account. Never create accounts to vote more than once, nor ask others to trade votes.
Vote for what you would really use: the votes are how the next features are chosen.
Answer polls and surveys for yourself, honestly: they are only as useful as the answers.

5. Protect your data, and other people's

Never post passwords, session ids, security tokens, license keys, ORG ids or usernames, nor any data of your customers or your company.
Check a screenshot or a snippet of code before you share it, and mask what is not meant to be public.
Do not post anything personal about someone else.
Your public profile, if you turn it on, is public: put in its bio and links only what you want everyone to read.

6. No spam, no advertising

A link is welcome when it adds to the discussion: the documentation, a release note, an article that answers the question.
Advertising, referral links, posting the same message in several places and comments written only to promote a product or a service are not, and are removed. The same goes for a profile's bio and links.
Mention a member (@username) when they have something to add, not to draw a crowd: every mention reaches them.

7. Share only what is yours to share

Respect copyright: quote briefly, and link to the source rather than copying it.
The Salesforce news belong to their authors: discuss them here, read them where they were published.
What you post is public, and is published on the site and in the extension's panel, as the EULA explains.

8. Write to be read

Write in English, the language the whole community shares.
Use Markdown: `code` and code blocks for Apex, SOQL and formulas, lists for steps, > to quote.
You can edit a comment for 15 minutes after posting it, and delete it whenever you like.

9. Reports and moderation

If a comment breaks these guidelines, do not answer in kind: signed in, click Report under it (shown under other members' comments, not your own). The moderators have a look at it, and its author is never told who reported it.
Comments are published at once and moderated afterwards: a comment that breaks these guidelines is hidden or removed.
How often an account may propose, vote and comment is limited, to keep spam away.
An account that breaks these guidelines repeatedly, or seriously, may be suspended.
A question about a moderation decision? Write to [email protected].

These guidelines say in practice what clause 16 of the End User License Agreement asks of every community account; where the two differ, the EULA is what applies. Thank you for helping keep the community a good place to be.