Social media accounts can be powerful tools for NGOs, but using social media also involves risks. For example, social media posts can rapidly reach a large audience. Engaging in electioneering (or even appearing to engage in it) could threaten IREX’s nonprofit status.
We trust employees to exercise good judgment online and offline. The intent of the following policies is to manage risks without restricting employees’ personal free speech. We encourage employees to think carefully about the content that they post online, since it could have unintended consequences for IREX’s reputation, competitiveness, or security.
Social media accounts that teams manage on behalf of IREX
- Approval: Employees must obtain approval before creating a new website or social media account on behalf of IREX. Approval is required from the practice head (or unit head) and Strategic Communications.
Before granting approval, the teams must agree about the answers to the following questions: (1) What are the objectives of the new social media account?, (2) who are the intended audiences?, and (3) what is the timetable for assessing the account's performance and improving or retiring it if it underperforms?
IREX will give priority to accounts that align with multiple criteria: (1) It supports an opportunity in IREX’s Strategic Communications Plan, (2) it will strengthen IREX’s positioning for funding streams that have long-term potential, and/or (3) it will help diversify IREX’s funding sources or attract key partners.
- Account manager: When a team manages a social media account on behalf of IREX, the team must appoint one person to serve as the account’s manager. The account’s manager is responsible for coordinating contributions and making decisions about the account (in alignment with the policies, standards, and guidelines that IREX establishes). The team must send the account manager’s contact information to Strategic Communications.
- “Group” e-mail address: Social media accounts that employees administer on behalf of IREX must be connected to “group” irex.org e-mail addresses (such as teamname@irex.org) not personal e-mail addresses (such as jsmith@irex.org or jsmith@yahoo.com). This policy does not apply to Facebook accounts. Contact support@irex.org to set up a group address.
- Log-in information: Teams that manage a social media account on behalf of IREX must ensure that Strategic Communications has up-to-date log-in information for the account.
- Political activities: Employees should not use the accounts to engage in political activities.
- Sensitive information: Employees should not share information on social media that could compromise any person’s privacy or security.
- Dishonorable content: Employees are expected not to post or share dishonorable content such as obscenities, personal insults, or slurs (e.g., racial, ethnic, sexual, religious, or disability).
- Stewardship: Accounts that violate IREX’s policies or standards will be given a warning. If the violations continue, Strategic Communications and the corresponding practice head (or unit head) will make a joint decision about whether to appoint a new account manager or close the account.
Personal social media accounts
- Political activities: IREXers should not engage in political activities on their personal social media accounts while on duty, while using IREX equipment, or while in an IREX building.
- Sensitive information: IREXers should not share information on their personal social media accounts that could compromise any person’s privacy or security.
IREXers may talk about their work on their personal social media accounts, but they should not reveal trade secrets or other sensitive information. If you are not certain whether a piece of information is sensitive, consult with your manager or Strategic Communications first.
-
Associating your account with IREX: If your personal social media profile mentions that you work at IREX, your account's bio must state that the opinions expressed in the account are your own.
Authors: Strategic Communications & Practice Heads
Last updated: June 19, 2017