diff --git a/Documentation/SUMMARY.md b/Documentation/SUMMARY.md
index 6562590..fd6fa49 100644
--- a/Documentation/SUMMARY.md
+++ b/Documentation/SUMMARY.md
@@ -42,16 +42,51 @@
* [afsafsaf](https://tiof.click/HeyBigTech)
* [Media Archive](comms/media-archive.md)
-## Packages
+## Infrastructure
-* [Page 7](packages/page-7.md)
+* [Basic Needs](infrastructure/basic-needs.md)
***
* [Page 3](page-3.md)
* [Page 4](page-4.md)
-## Handbooks
+## Imports
-* [Page 1](group-1/page-1.md)
-* [Page 5](handbooks/page-5.md)
+* [Page 1](imports/page-1.md)
+* [Page 5](imports/page-5.md)
+* [Call To Actions](imports/call-to-actions.md)
+* [Creative Commons Malaysia Chapter](imports/creative-commons-malaysia-chapter.md)
+* [Handbook: Banking](imports/handbook-banking.md)
+* [Handbook: Comms](imports/handbook-comms.md)
+* [Handbook: Devs](imports/handbook-devs.md)
+* [Handbook: Finance](imports/handbook-finance.md)
+* [Handbook: Human Resources](imports/handbook-human-resources.md)
+* [Handbook: Initiatives](imports/handbook-initiatives.md)
+* [Handbook: Organization Identity](imports/handbook-organization-identity.md)
+* [Handbook: Procurement](imports/handbook-procurement.md)
+* [Handbook: Staff](imports/handbook-staff.md)
+* [Handbook: Tags](imports/handbook-tags.md)
+* [Handbook: Terminology](imports/handbook-terminology.md)
+* [Handbooks](imports/handbooks.md)
+* [Hey Big Tech! declaration](imports/hey-big-tech-declaration.md)
+* [Home](imports/home.md)
+* [Creative Commons Malaysia Chapter](imports/creative-commons-malaysia-chapter-1.md)
+* [Hey Big Tech! declaration](imports/hey-big-tech-declaration-1.md)
+* [Infrastructure: Calendar.com](imports/infrastructure-calendar.com.md)
+* [Infrastructure: Custom Fields](imports/infrastructure-custom-fields.md)
+* [Infrastructure: Encharge.io](imports/infrastructure-encharge.io.md)
+* [Infrastructure: Funnels](imports/infrastructure-funnels.md)
+* [Infrastructure: Github](imports/infrastructure-github.md)
+* [Infrastructure: Google Calendar](imports/infrastructure-google-calendar.md)
+* [Infrastructure: LinkedIn](imports/infrastructure-linkedin.md)
+* [Infrastructure: QPage](imports/infrastructure-qpage.md)
+* [Infrastructure: Salesforce](imports/infrastructure-salesforce.md)
+* [Infrastructure: Slack](imports/infrastructure-slack.md)
+* [Media Kit](imports/media-kit.md)
+* [Policies](imports/policies.md)
+* [Policy: Children Protection](imports/policy-children-protection.md)
+* [Policy: Data & Privacy](imports/policy-data-and-privacy.md)
+* [Policy: Data Protection](imports/policy-data-protection.md)
+* [Policy: Donations](imports/policy-donations.md)
+* [Policy: Health and Safety](imports/policy-health-and-safety.md)
diff --git a/Documentation/imports/call-to-actions.md b/Documentation/imports/call-to-actions.md
new file mode 100644
index 0000000..8fb5bb5
--- /dev/null
+++ b/Documentation/imports/call-to-actions.md
@@ -0,0 +1,35 @@
+# Call To Actions
+
+
+
+***
+
+## Table of Contents
+
+
+
+Expand / Collapse
+
+
+
+1. Introduction
+ * Definitions
+2. Concepts
+ * Name
+3. Contents
+ * Descriptions
+4. Official Channels
+ * Official Website
+5. TIOF Projects
+
+
+
+## THIS DOCUMENT IS A WORK IN PROGRESS
+
+## About
+
+This document synthetizes the different Calls To Action from The IO Foundation.
+
+## Join TIOF
+
+## Sign the DCDR Pledge
diff --git a/Documentation/imports/creative-commons-malaysia-chapter-1.md b/Documentation/imports/creative-commons-malaysia-chapter-1.md
new file mode 100644
index 0000000..15ff539
--- /dev/null
+++ b/Documentation/imports/creative-commons-malaysia-chapter-1.md
@@ -0,0 +1,118 @@
+# Creative Commons Malaysia Chapter
+
+
+
+> ## NOTICE: MINUTES OF THE FIRST MEETING ARE PUBLISHED [HERE](https://github.com/TheIOFoundation/TIOF/wiki/\[CC-MYS]-First-Meeting---20th-March-2021)
+
+## The CC Malaysia Chapter
+
+Welcome to the _Temporary Website_ for the CC Malaysia Chapter.
+
+> Please note that this website's sole purpose is to prepare for the First Meeting of the Chapter where the governance board and other positions will be elected. As the Chapter builds up it will have its own website and other management and outreach tools.
+
+> You can safely ignore the side menu.
+
+### Statutes
+
+As the Chapter gets constituted a clear Statue document must be implemented and observed for its functioning. This will be part of the [agenda](https://dothe.click/CCMYSAboutUs) during the First Meeting.
+
+## Members
+
+Currently the CC Malaysia Chapter does not have official members as it's undergoing its official constitution process. The current 2 persons organizing and facilitating this process are [Jean F. Queralt (The IO Foundation)](https://www.linkedin.com/in/jfqueralt/) and [Suma Jayachandran (Wawasan Open University)](https://www.linkedin.com/in/suma-jayachandran-13886728/). The final composition of the governance board and the rest of the Chapter members will be elected during the upcoming First Meeting. For more information on this process, please refer to the this [page](https://dothe.click/CCMYSAboutUs).
+
+### Upcoming Election
+
+The current election process is to take place on Saturday 20th March 2021, from 14:00 to 16:00 (UTC+8 - Malaysia time). The event will be hosted by The IO Foundation under its TechUp initiative. It will include the First Meeting session and a booth for CC Malaysia Chapter where people can gather for more information during the weekend.
+
+#### Timeline
+
+The following timeline has been set to move forward with the constitution of the CC Malaysia Chapter:
+
+* Candidacies to be open from 1st to 14th March.
+ * Submission of candidacies [here](https://github.com/TheIOFoundation/TIOF/wiki/Creative-Commons-Malaysia-Chapter#presentation-of-candidacies)
+* Info uploaded to Temp CC Chapter website (this page)
+* Preparation and publishing (this page) of candidacies on D-7 (Saturday 13h March)
+ * Candidacies will be published [here](https://github.com/TheIOFoundation/TIOF/wiki/Creative-Commons-Malaysia-Chapter#candidates)
+* First Meeting to be held online during TechUp event (Saturday 20th March - 14:00 to 16:00 UTC+8).
+ * See [agenda](https://dothe.click/CCMYSAboutUs).
+ * Vote for candidates [here](https://github.com/TheIOFoundation/TIOF/wiki/Creative-Commons-Malaysia-Chapter#voting)
+* Submission of results to CCGN
+* Formalization of the chapter and beginning of activities
+
+#### Presentation of candidacies
+
+The process of presentation of candidacies opens on the 1st of March 2021 and closes on the 14h of March 2021 EoD UTC+8.
+
+There will be 2 main positions to be filled during the constitution of the CC Chapter, namely:
+
+**Chapter Lead** Description and responsibilities: See the [official CC documentation](https://github.com/creativecommons/global-network-strategy/blob/master/docs/Role\_descriptions\_GNC\_rep\_and\_Chapter\_lead.md#role-description-for-chapter-lead-or-chapter-coordinator).
+
+**GNC Representative** **IMPORTANT:** The GNC Representative can ONLY BY a registered GNC Member. Should you want to initiate that process, please [read this guide](https://network.creativecommons.org/sign-up/).
+
+Description and responsibilities: See the [official CC documentation](https://github.com/creativecommons/global-network-strategy/blob/master/docs/Role\_descriptions\_GNC\_rep\_and\_Chapter\_lead.md#role-description-for-the-global-network-council-representative).
+
+Before submitting your candidacy, please make sure to:
+
+* Read the position descriptions (above) and make sure that you understand them and comply with their requirements.
+* Keep in mind that theses are NOT remunerated positions
+* Ensure that you will have enough time to properly fulfil your obligations and to help the Chapter solidify and grow
+
+> ## NOTICE: CANDIDACIES HAVE BEEN CLOSED. LIST OF CANDIDATES IS PUBLISHED [HERE](http://dothe.click/CCMYSCandidates)
+
+#### Candidates
+
+**For Chapter Lead** THIS SECTION WILL BE POPULATED WITH THE CANDIDACIES STARTING 14th MARCH.
+
+**For GNC Representative** THIS SECTION WILL BE POPULATED WITH THE CANDIDACIES STARTING 14th MARCH.
+
+#### Voting
+
+THE LINK TO THE VOTING PLATFORM WILL BE PUBLISHED ON THE 20th MARCH.
+
+### Join the Chapter
+
+The CC Malaysia Chapter will need of your collaboration to create a strong team who can build the chapter, disseminate knowledge on the CC movement and organize events. A good number of skills are required and no help is small. During the First Meeting we will be analyzing the different needs and you will be able to evaluate if you can contribute with your expertise. So far, the expected (yet unconfirmed) roles would be along the lines of:
+
+* Chapter secretary
+* Website manager
+* Comms coordinator
+* Events coordinator
+* Partners coordinator
+* HR (including Membership) coordinator
+
+## Activities
+
+For the time being, the only scheduled event is the First Meeting, where the CC Malaysia Chapter is to be officially constituted. One of the items in the [agenda](https://dothe.click/CCMYSAboutUs) is to discuss what should be the next events for 2021. Come and propose!
+
+### Proposing Activities
+
+See above.
+
+## Calendar
+
+One of the action items to be implemented by the CC Malaysia Chapter should be publishing its events through a publicly accessible calendar.
+
+## Media Channels
+
+Currently, the following media channels are being considered:
+
+* Website (Wordpress - likely to be provided by CC GNC)
+* Twitter (currently unclear who is handling this - working on it - If you know, please reach out to us: CCMYS@TheIOFoundation.org)
+* LinkedIn (recently registered)
+
+All these will require proper management, for which the Chapter will need to source adequate tools.
+
+### Website
+
+While we Chapter is constituted, the Temp Website will be a combination of:
+
+* [Wiki](https://github.com/TheIOFoundation/TIOF/wiki/Creative-Commons-Malaysia-Chapter) page
+ * To publish information on the ongoing processes
+* [Start.me](https://dothe.click/CCMYSAboutUs) page
+ * to publish a collection of relevant links
+
+Once the Chapter obtains its own website all this information will be migrated there.
+
+### Media Policy
+
+Another relevant policy that the Chapter will need to establish will be its Media Policy.
diff --git a/Documentation/imports/creative-commons-malaysia-chapter.md b/Documentation/imports/creative-commons-malaysia-chapter.md
new file mode 100644
index 0000000..15ff539
--- /dev/null
+++ b/Documentation/imports/creative-commons-malaysia-chapter.md
@@ -0,0 +1,118 @@
+# Creative Commons Malaysia Chapter
+
+
+
+> ## NOTICE: MINUTES OF THE FIRST MEETING ARE PUBLISHED [HERE](https://github.com/TheIOFoundation/TIOF/wiki/\[CC-MYS]-First-Meeting---20th-March-2021)
+
+## The CC Malaysia Chapter
+
+Welcome to the _Temporary Website_ for the CC Malaysia Chapter.
+
+> Please note that this website's sole purpose is to prepare for the First Meeting of the Chapter where the governance board and other positions will be elected. As the Chapter builds up it will have its own website and other management and outreach tools.
+
+> You can safely ignore the side menu.
+
+### Statutes
+
+As the Chapter gets constituted a clear Statue document must be implemented and observed for its functioning. This will be part of the [agenda](https://dothe.click/CCMYSAboutUs) during the First Meeting.
+
+## Members
+
+Currently the CC Malaysia Chapter does not have official members as it's undergoing its official constitution process. The current 2 persons organizing and facilitating this process are [Jean F. Queralt (The IO Foundation)](https://www.linkedin.com/in/jfqueralt/) and [Suma Jayachandran (Wawasan Open University)](https://www.linkedin.com/in/suma-jayachandran-13886728/). The final composition of the governance board and the rest of the Chapter members will be elected during the upcoming First Meeting. For more information on this process, please refer to the this [page](https://dothe.click/CCMYSAboutUs).
+
+### Upcoming Election
+
+The current election process is to take place on Saturday 20th March 2021, from 14:00 to 16:00 (UTC+8 - Malaysia time). The event will be hosted by The IO Foundation under its TechUp initiative. It will include the First Meeting session and a booth for CC Malaysia Chapter where people can gather for more information during the weekend.
+
+#### Timeline
+
+The following timeline has been set to move forward with the constitution of the CC Malaysia Chapter:
+
+* Candidacies to be open from 1st to 14th March.
+ * Submission of candidacies [here](https://github.com/TheIOFoundation/TIOF/wiki/Creative-Commons-Malaysia-Chapter#presentation-of-candidacies)
+* Info uploaded to Temp CC Chapter website (this page)
+* Preparation and publishing (this page) of candidacies on D-7 (Saturday 13h March)
+ * Candidacies will be published [here](https://github.com/TheIOFoundation/TIOF/wiki/Creative-Commons-Malaysia-Chapter#candidates)
+* First Meeting to be held online during TechUp event (Saturday 20th March - 14:00 to 16:00 UTC+8).
+ * See [agenda](https://dothe.click/CCMYSAboutUs).
+ * Vote for candidates [here](https://github.com/TheIOFoundation/TIOF/wiki/Creative-Commons-Malaysia-Chapter#voting)
+* Submission of results to CCGN
+* Formalization of the chapter and beginning of activities
+
+#### Presentation of candidacies
+
+The process of presentation of candidacies opens on the 1st of March 2021 and closes on the 14h of March 2021 EoD UTC+8.
+
+There will be 2 main positions to be filled during the constitution of the CC Chapter, namely:
+
+**Chapter Lead** Description and responsibilities: See the [official CC documentation](https://github.com/creativecommons/global-network-strategy/blob/master/docs/Role\_descriptions\_GNC\_rep\_and\_Chapter\_lead.md#role-description-for-chapter-lead-or-chapter-coordinator).
+
+**GNC Representative** **IMPORTANT:** The GNC Representative can ONLY BY a registered GNC Member. Should you want to initiate that process, please [read this guide](https://network.creativecommons.org/sign-up/).
+
+Description and responsibilities: See the [official CC documentation](https://github.com/creativecommons/global-network-strategy/blob/master/docs/Role\_descriptions\_GNC\_rep\_and\_Chapter\_lead.md#role-description-for-the-global-network-council-representative).
+
+Before submitting your candidacy, please make sure to:
+
+* Read the position descriptions (above) and make sure that you understand them and comply with their requirements.
+* Keep in mind that theses are NOT remunerated positions
+* Ensure that you will have enough time to properly fulfil your obligations and to help the Chapter solidify and grow
+
+> ## NOTICE: CANDIDACIES HAVE BEEN CLOSED. LIST OF CANDIDATES IS PUBLISHED [HERE](http://dothe.click/CCMYSCandidates)
+
+#### Candidates
+
+**For Chapter Lead** THIS SECTION WILL BE POPULATED WITH THE CANDIDACIES STARTING 14th MARCH.
+
+**For GNC Representative** THIS SECTION WILL BE POPULATED WITH THE CANDIDACIES STARTING 14th MARCH.
+
+#### Voting
+
+THE LINK TO THE VOTING PLATFORM WILL BE PUBLISHED ON THE 20th MARCH.
+
+### Join the Chapter
+
+The CC Malaysia Chapter will need of your collaboration to create a strong team who can build the chapter, disseminate knowledge on the CC movement and organize events. A good number of skills are required and no help is small. During the First Meeting we will be analyzing the different needs and you will be able to evaluate if you can contribute with your expertise. So far, the expected (yet unconfirmed) roles would be along the lines of:
+
+* Chapter secretary
+* Website manager
+* Comms coordinator
+* Events coordinator
+* Partners coordinator
+* HR (including Membership) coordinator
+
+## Activities
+
+For the time being, the only scheduled event is the First Meeting, where the CC Malaysia Chapter is to be officially constituted. One of the items in the [agenda](https://dothe.click/CCMYSAboutUs) is to discuss what should be the next events for 2021. Come and propose!
+
+### Proposing Activities
+
+See above.
+
+## Calendar
+
+One of the action items to be implemented by the CC Malaysia Chapter should be publishing its events through a publicly accessible calendar.
+
+## Media Channels
+
+Currently, the following media channels are being considered:
+
+* Website (Wordpress - likely to be provided by CC GNC)
+* Twitter (currently unclear who is handling this - working on it - If you know, please reach out to us: CCMYS@TheIOFoundation.org)
+* LinkedIn (recently registered)
+
+All these will require proper management, for which the Chapter will need to source adequate tools.
+
+### Website
+
+While we Chapter is constituted, the Temp Website will be a combination of:
+
+* [Wiki](https://github.com/TheIOFoundation/TIOF/wiki/Creative-Commons-Malaysia-Chapter) page
+ * To publish information on the ongoing processes
+* [Start.me](https://dothe.click/CCMYSAboutUs) page
+ * to publish a collection of relevant links
+
+Once the Chapter obtains its own website all this information will be migrated there.
+
+### Media Policy
+
+Another relevant policy that the Chapter will need to establish will be its Media Policy.
diff --git a/Documentation/imports/handbook-banking.md b/Documentation/imports/handbook-banking.md
new file mode 100644
index 0000000..b4a1f84
--- /dev/null
+++ b/Documentation/imports/handbook-banking.md
@@ -0,0 +1,9 @@
+# Handbook: Banking
+
+Structure:
+
+Bank accounts
+
+Cruptocurrencies\
+Coinbase Commerce\
+Ledger Nano
diff --git a/Documentation/imports/handbook-comms.md b/Documentation/imports/handbook-comms.md
new file mode 100644
index 0000000..3bdb9d2
--- /dev/null
+++ b/Documentation/imports/handbook-comms.md
@@ -0,0 +1,104 @@
+# Handbook: Comms
+
+
+
+***
+
+### Please note that this page is a Work in Progress. Sections that are being completed are marked with **\[WIP]**.
+
+Abstract
+
+A note on localization Each document may have been translated into different languages. Check the Language Marker in the file name. Structure
+
+This is the general document, which establishes the global guidelines of Comms in the whole organization.
+
+Project-Specific SOP Each Project has its own guidelines/SOP that are to be followed on top of the Global Guidelines and establish particular parameters that only apply to that Project.
+
+Adding new presence platforms Update the corresponding document (section “List of platforms”)
+
+## Tone & Voice
+
+Content Guidelines
+
+As Project Lockdown begins outreach to its target audience, it’s important for the voice and tone of the PL’s social media presence to be consistent and accurately convey the project’s values and objectives.
+
+What is Voice?
+
+“...voice is the purposeful, consistent expression of a brand through words and prose styles that engage and motivate. It’s true: The personality of your brand is determined, in large measure, by the words you use and the sentences you write.”
+
+Target Audience
+
+The target audience consists of users searching for clarity, objectivity, and reliability. The voice of PL on any platform should respond to these goals.
+
+***
+
+Voice & Tone
+
+The voice of Project Lockdown remains the same, while the tone can change a bit depending on the subject matter being addressed. To avoid confusing messaging, the following is what PL should not sound like, no matter the context:
+
+Playful: The subject matter of PL is serious, and social media communications should respect this. Witty: PL aims to provide information and empower users through knowledge - there’s no need to infuse messages with superfluous personality that doesn’t add to this objective. Persuasive: PL is a neutral, bi-partisan platform and it’s crucial that social media communications make this clear.
+
+When writing for Project Lockdown, we should sound:
+
+Helpful and responsive, but not overly personal Objective and matter-of-fact, but not cold or curt Honest and clear, but not blunt or robotic
+
+For Example:
+
+Helpful and Responsive
+
+Tweet this: Project Lockdown has updated the platform with several new features based on user feedback: (list features).
+
+Not this: Hurray! New features are up on Project Lockdown, check it out.
+
+Objective and Matter-of-Fact
+
+Tweet this: The latest data compiled shows a number of countries in Asia scaling back on COVID-19 lockdown measures including China, where the virus was first reported.
+
+Not this: Should China have scaled back lockdown measures so soon? Data shows restrictions already being lifted in the pandemic’s epicenter city of Wuhan.
+
+Honest and Clear
+
+Tweet this: South Africa, Nigeria, and Kenya have implemented martial law in the past 36 hours.
+
+Not this: Increased restrictions are being reported in Africa.
+
+***
+
+Twitter Best Practices
+
+“Brands come to Twitter to be what people are talking about right now. And because people are in a discovery mindset when they’re on Twitter, your brand or business is likely to leave a lasting impression.”
+
+Twitter is an ideal platform for communicating concise, relevant content to users in an approachable way that allows for maximum user engagement. To best utilize Twitter for Project Lockdown, we want to keep the following Do’s in mind:
+
+Do:
+
+Post consistent, relevant information Write out abbreviations. Ex. NPIs (Non-pharmaceutical Interventions) Respond in a timely matter to user questions or comments Incorporate the PL voice in each Tweet and response Tweet like you speak to others in a professional context to avoid being overly robotic or personal Always link to relevant information on the PL site Clarify questions or information when needed and redirect potentially biased responses to neutral data sources
+
+Don’t:
+
+Respond in a confrontational manner to user questions or comments Use confusing jargon or terminology without elaborating or clarifying Link tweets to unverified or potentially unreliable information Ignore communications regarding the potential in inaccuracy of information on the product: PL is open to suggestions and corrections Infuse tweets with the personality of the individual tweeting or replying Use emojis or humorous GIFs
+
+***
+
+Style Guide
+
+To ensure consistent and clear copy, adhere to the following grammar mechanics and best practices:
+
+Basic Rules
+
+Use active voice instead of passive Be mindful of all users, who have varying prior knowledge and come from different backgrounds Keep it simple and consistent Maintain a neutral, unbiased voice
+
+***
+
+Pass to Dooly Playbooks
+
+## Registering
+
+* Register data
+* Create necessary media, store in its own Channel folder in Repository > Project Identity
+* Always use the main account to be the Owner of the account.
+* Create Shortlink (@@@See Handbook)
+* Add Shortlink to AboutUs (@@@See Handbook)
+* Create corresponding Media Channel Procedures Wiki page when necessary (@@@See Handbook)
+
+***
diff --git a/Documentation/imports/handbook-devs.md b/Documentation/imports/handbook-devs.md
new file mode 100644
index 0000000..aeddadd
--- /dev/null
+++ b/Documentation/imports/handbook-devs.md
@@ -0,0 +1,58 @@
+# Handbook: Devs
+
+## TIOF general Dev Guidelines
+
+## Front-End
+
+## Back-End
+
+## Software lifecycle
+
+Useful Chrome extensions
+
+Find something similar: https://chrome.google.com/webstore/detail/hoverify/bbpokcagpggnekcmamgdieebhpkjmljm
+
+@@@ Link to TIOF' Repo
+
+@@@Add
+
+\- Package.json
+
+Comment using \
+"scriptsComments": {\
+"FIELD": "COMMENT"\
+},
+
+{\
+"name": "package name",\
+"version": "1.0",\
+"description": "package description",\
+"scripts": {\
+"start": "npm install && node server.js"\
+},\
+"scriptsComments": {\
+"start": "Runs development build on a local server configured by server.js"\
+},\
+"dependencies": {\
+"ajv": "^5.2.2"\
+},\
+"dependenciesComments": {\
+"ajv": "JSON-Schema Validator for validation of API data"\
+}\
+}
+
+Source: https://stackoverflow.com/questions/14221579/how-do-i-add-comments-to-package-json-for-npm-install
+
+\- TIOF Labels
+
+\Back to top\
+
+\# Project Lockdown specific Dev Guidelines
+
+\- PLD Labels
+
+\Back to top\
+
+\# Additional information
+
+\Back to top\
diff --git a/Documentation/imports/handbook-finance.md b/Documentation/imports/handbook-finance.md
new file mode 100644
index 0000000..e00766a
--- /dev/null
+++ b/Documentation/imports/handbook-finance.md
@@ -0,0 +1,37 @@
+# Handbook: Finance
+
+To add: Cryptocurrencies To add: Banking Handbook
+
+FROM LEN TEMPLATE:
+
+Note: Needs to be signed off by a Certified Public Accountant
+
+1. INTRODUCTION
+2. DIVISION OF RESPONSIBILITIES
+3. CHART OF ACCOUNTS AND GENERAL LEDGERS
+4. CASH REGISTRY
+
+* Include cards
+* Include cryptos (maybe use a general term as financial assets?)
+
+1. CASH DISBURSEMENTS AND EXPENSE ALLOCATIONS
+2. ACCRUALS
+3. BANK ACCOUNT RECONCILIATIONS
+4. PETTY CASH FUND AND REVOLVING FUND
+5. ASSET MANAGEMENT
+6. PERSONNEL RECORDS
+7. Kept in electronic format inside the CRM or whatever other storage medium used at the time. Access and rectification (following HR regulations) allowed.
+8. PAYROLL PROCESSING
+9. END OF THE MONTH AND FISCAL YEAR CLOSE
+10. FISCAL POLICY STATEMENTS
+11. APPENDICES
+
+Revenue Streams
+
+SI Labels:
+
+SII
+
+SIII
+
+SIV
diff --git a/Documentation/imports/handbook-human-resources.md b/Documentation/imports/handbook-human-resources.md
new file mode 100644
index 0000000..557998e
--- /dev/null
+++ b/Documentation/imports/handbook-human-resources.md
@@ -0,0 +1,82 @@
+# Handbook: Human Resources
+
+
+
+## Table of Contents
+
+
+
+Expand / Collapse
+
+
+
+1. Introduction
+ * Definitions
+ * About this document
+ * Scope
+2. Policy details
+ * Anti corruption and Anti bribery statement
+ * What is bribery?
+ * Gifts and hospitality
+ * Record keeping
+ * How to raise a concern
+ * Conduct outside of Work
+
+
+
+## Introduction
+
+### Definitions
+
+This document employs terms related to the [DCDR Advocacy](http://tiof.click/Advocacy) that can be found in the [TIOF terminology](http://tiof.click/Terminology).
+
+For a structure of The IO Foundation, please visit
+
+* The IO Foundation's [Organizational Chart](http://tiof.click/TIOFOrgChart)
+* The IO Foundation's [Organizational Nomenclature](http://tiof.click/OrgNomenclature)
+
+Back to top
+
+### About this document
+
+This document sets out the position maintained by TIOF in matters of Anti-corruption and Anti-bribery that you will need to be aware of while being a Member for TIOF. You should familiarize yourself with it and comply with it at all times. Any questions you may have with regard to its contents or what you have to do to comply with it should be referred to your corresponding Team Human Resources Coordinator.
+
+Any Member who breaches this Policy will face disciplinary action, which could result in dismissal for gross misconduct. Any non-employee who breaches this Policy may have their contract (or equivalent official relationship with TIOF) terminated with immediate effect.
+
+This document complements TIOF's [Code of Conduct](http://tiof.click/TIOFPolicyCoC)
+
+This document does not form part of any [Engagement Document](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#engagement-document) and we may amend it at any time.
+
+Back to top
+
+### Scope
+
+This document directly applies to:
+
+* All [TIOF Members](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#member)
+
+This document indirectly applies to:
+
+* All [TIOF Contributors](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors)
+
+The policies and/or procedures set out in this document apply to all TIOF Members unless otherwise indicated. They therefore apply to Directors, Advisers, Counselors, Staff, Volunteers and Interns; this is irrespective of their part-time, fixed-term or casual status. They equally apply to all [Contributors](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors) and will be used as part of the selection criteria when engaging with them.
+
+This document applies within all TIOF spaces, including (although not limited to) management activities, project contributions or events, and also applies when an individual is officially representing the broader community in public spaces. Examples of representing our community include (although not limited to) using an official e-mail address, posting via an official social media account or acting as an appointed representative at an event (online or offline).
+
+Back to top
+
+## Handbook
+
+When a submission/change is made on Qpage, a notification is sent to Slack to the corresponding #XXX-HR-Provisioning channel. Notifications will also reach the people involved in the position (their own personal email).
+
+Member Provisioning Stages Sourcing When: When we open a position and go through all the existing leads to offer it to them. Team: Notification (?) Applicant: You have been selected for a new position + Basic Info
+
+Applied When: When a new applicant applies for an open position. Team: Notification Applicant: Thx + Basic Info
+
+Screening When: A candidate made first cut. Team: Applicant: Informed + extra info
+
+Interview When: Team: Applicant:
+
+Offer When: Team: Applicant:
+
+Hired When: Team: Applicant:
diff --git a/Documentation/imports/handbook-initiatives.md b/Documentation/imports/handbook-initiatives.md
new file mode 100644
index 0000000..c137de0
--- /dev/null
+++ b/Documentation/imports/handbook-initiatives.md
@@ -0,0 +1,53 @@
+# Handbook: Initiatives
+
+
+
+***
+
+## Table of Contents
+
+1. Abstract
+2. TIOF general Dev Guidelines
+3. Project Lockdown specific Dev Guidelines
+4. Additional information
+
+## Project Organization
+
+### General considerations
+
+### Milestones
+
+Projects in TIOF use Milestones to establish relevant deadlines in order to structure their implementation.
+
+Milestones are created and maintained by:
+
+* TIOF Management
+* Project Managers
+
+Milestones are organized in 2 levels:
+
+* Organization-wide These Milestones apply across all the organization and are to be observed mainly by TIOF's organization core as well as Project Managers.
+* Project-wide These Milestones apply specifically to a given TIOF Project and are to be observed by all Project's Teams.
+
+### GitHub Issues
+
+* Templates
+* Labels
+* Pinned Issues
+
+When creating a new Feature
+
+* Create a Root Issue
+* List all subtasks as Tasks Markdown)
+* Create the necessary Issues for each task and populate them with the necessary information as per template.
+* Add the Issue # to the Root Issue (@@@ Look into automating this. Should be doable.)
+
+Pull Requests
+
+* Templates
+
+***
+
+## Abstract
+
+Back to top
diff --git a/Documentation/imports/handbook-organization-identity.md b/Documentation/imports/handbook-organization-identity.md
new file mode 100644
index 0000000..58249fe
--- /dev/null
+++ b/Documentation/imports/handbook-organization-identity.md
@@ -0,0 +1,63 @@
+# Handbook: Organization Identity
+
+## Project Identity
+
+This document defines all the necessary elements that conform TIOF's Project Identity at large. It is a reference document to which all TIOF productions, internal and external, need to refer and adhere. For any doubts, please contact Team Comms.
+
+Note: The [Media Kit](https://github.com/TheIOFoundation/TIOF/wiki/Media-Kit) is a subset of the Project Identity, focusing on productions that are generated for external outreach.
+
+Some working content to be moved here: https://docs.google.com/document/d/1\_BjdBtldAhO8seNjivXqKjnwzXRYCcVA-fc90h1Z2XM/edit#
+
+See reference document: https://github.com/TheIOFoundation/TIOF/blob/main/Project%20Identity/%5BTIOF%5D%20Comms%20%5BP%5D%20Branding%20Guidelines%20ENG%20v1.4.pdf
+
+## Font
+
+Montserrat, Calibri(?)
+
+Website data: DESKTOP TEXT (General - Apply at ROW level) Text 12px Line Height 20px Letter spacing 1px Note: Some pages will have their own custom settings as needed.
+
+## Main folder
+
+GH Repository: https://github.com/TheIOFoundation/TIOF/tree/main/Project%20Identity
+
+Google Drive: \[TIOF] Repository/Project Identity
+
+## QR Codes
+
+https://www.qrcode-monkey.com/#url
+
+### Procedure
+
+* Configuration
+
+
+
+https://{WEBSITE}
+
+
+
+You can Copy & Paste the following values:
+
+Foreground Color #4E5056
+
+Eye Color #66B5C5 #F79552
+
+Background Color #FFFFFF
+
+
+
+Add corresponding logo
+
+
+
+Select corresponding options
+
+* Set Quality to MAX (2000x2000 px)
+* Download ALL formats (PNG, EPS, SVG, PDF)
+* Name following TIOF’s file naming format. \[TIOF] Comms \[P] {Object} QR Code XXX v{version}
+
+## Channel-specific information
+
+### Website
+
+@@@Loading Hex
diff --git a/Documentation/imports/handbook-procurement.md b/Documentation/imports/handbook-procurement.md
new file mode 100644
index 0000000..17c9689
--- /dev/null
+++ b/Documentation/imports/handbook-procurement.md
@@ -0,0 +1,5 @@
+# Handbook: Procurement
+
+\[COVER PAGE]
+
+ABOUT THE ORGANIZATION ABOUT THIS POLICY CODE OF CONDUCT SOLICITATION AND COMPETITION SELECTION DOCUMENTATION CONTRACT ADMINISTRATION
diff --git a/Documentation/imports/handbook-staff.md b/Documentation/imports/handbook-staff.md
new file mode 100644
index 0000000..f071a6d
--- /dev/null
+++ b/Documentation/imports/handbook-staff.md
@@ -0,0 +1,94 @@
+# Handbook: Staff
+
+
+
+***
+
+## PLEASE NOTE THAT THIS IS A WORK IN PROGRESS DOCUMENT
+
+***
+
+## Staff's Handbook
+
+### Definitions
+
+This document employs terms related to the [DCDR Advocacy](http://tiof.click/Advocacy) that can be found in the [TIOF terminology](http://tiof.click/Terminology).
+
+For a structure of The IO Foundation, please visit
+
+* The IO Foundation's [Organizational Chart](http://tiof.click/TIOFOrgChart)
+* The IO Foundation's [Organizational Nomenclature](http://tiof.click/OrgNomenclature)
+
+### About this Handbook
+
+This Members' Handbook sets out the main policies and procedures that you will need to be aware of while being a Member for TIOF. You should familiarize yourself with it and comply with it at all times. Any questions you may have with regard to its contents or what you have to do to comply with it should be referred to your corresponding Team HR Coordinator.
+
+This Handbook does not form part of any Engagement Document and we may amend it at any time.
+
+### Scope
+
+This document directly applies to:
+
+* All \[TIOF Members] (https://github.com/TheIOFoundation/TIOF/wiki/Terminology#member)
+
+This document indirectly applies to:
+
+* All \[TIOF Contributors] (https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors)
+
+The policies and procedures set out in this document apply to all TIOF Members unless otherwise indicated. They therefore apply to Directors, Advisers, Counselors, Staff, Volunteers and Interns; this is irrespective of their part-time, fixed-term or casual status. They equally apply to all [Contributors](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors) and will be used as part of the selection criteria when engaging with them.
+
+This document applies within all TIOF spaces, including (although not limited to) management activities, project contributions or events, and also applies when an individual is officially representing the broader community in public spaces. Examples of representing our community include (although not limited to) using an official e-mail address, posting via an official social media account or acting as an appointed representative at an event (online or offline).
+
+### About The IO Foundation
+
+@@@\[Insert introduction e.g. details about the business]
+
+The IO Foundation and its members adhere to the following [Code of Conduct](http://tiof.click/TIOFPolicyCoC)
+
+### Responsibility for the Members' Handbook
+
+\[TIOF] Team Human Resources has overall responsibility for this Handbook and for ensuring that its policies and procedures comply with TIOF's legal obligations. This is carried out by:
+
+* Guidance of the Board of Directors
+* Advisory provided by the Board of Advisers and the Board of Counselors of each project
+* Supervision of \[TIOF] Team Management
+* Assistance by \[TIOF] Team Legal
+* Application by all \[TIOF XXX] Team Human Resources
+
+The Members' Handbook is reviewed regularly to ensure that its provisions continue to meet our legal obligations and reflect best practices.
+
+All Members should ensure that they take the time to read and understand the content of this Handbook and act in accordance with its aims and objectives. Managers and Coordinators must ensure all Members understand the standards of behavior expected of them and to take action when behavior falls below those requirements.
+
+### Personal data
+
+Whenever we process personal data about you in connection with our policies, we will process it in accordance with our @@@Data Protection Policy. We will only process your personal data if we have a lawful basis for doing so. We will notify you of the purpose or purposes for which we use it. Please see the Privacy Notice for further information.
+
+### Emergency contact details
+
+We retain details of your home address and the emergency contact telephone numbers of the person or persons you would like us to contact in the event of an emergency, for example if you have an accident. This information will be requested when you become and active TIOF Member and you should advise us of any changes straight away. This information is held in confidence and will only be used when needed.
+
+This information is mandatory for:
+
+* Directors
+* Advisers
+* Staff
+* Interns
+
+This information is optional for:
+
+* Counselors
+* Volunteers
+
+@@@Define Emergencies
+
+### Changes and application
+
+This Members' Handbook enters in effect at the time of publication.
+
+We reserve the right to revise, modify, delete or add to any and all policies, procedures, work rules or benefits stated in this handbook or in any other document.
+
+Any written changes to this Handbook will be made available to all Members to make them aware of the new policies or procedures. No verbal statements or representations can in any way alter the provisions of the Members Handbook.
+
+@@@Link to all Document Matrix & LMS.
+
+This handbook was last reviewed in @@@Should be date of last PR.
diff --git a/Documentation/imports/handbook-tags.md b/Documentation/imports/handbook-tags.md
new file mode 100644
index 0000000..4d67173
--- /dev/null
+++ b/Documentation/imports/handbook-tags.md
@@ -0,0 +1,19 @@
+# Handbook: Tags
+
+### Existing Tags
+
+https://docs.google.com/spreadsheets/d/1Q4CSDg3Vg-M7I5pENX1pxPDJckT8H0E2Rrxz2QTZb2g/edit#gid=0
+
+### Requesting a new Tag
+
+Link to Requisition form: https://docs.google.com/forms/d/e/1FAIpQLSfUOuTHpqLD1i7XDXmgvN1se1-9WfL\_FcNKwCCnQg9\_rzGqQQ/viewform
+
+### Creating a new Tag
+
+* Go to TIOF main repo Labels: https://github.com/TheIOFoundation/TIOF/labels
+* Create new Tag, following existing code convention (Naming, color, description)
+* Dry run Tag replication to all TIOF repos with github-sync.js
+* node github-sync.js labels -s TheIOFoundation/TIOF -t TheIOFoundation --token \[INSERT TOKEN] --dry-run
+* If all correct, execute Tag replication to all TIOF repos with github-sync.js
+* node github-sync.js labels -s TheIOFoundation/TIOF -t TheIOFoundation --token \[INSERT TOKEN]
+* Enjoy
diff --git a/Documentation/imports/handbook-terminology.md b/Documentation/imports/handbook-terminology.md
new file mode 100644
index 0000000..66b0a48
--- /dev/null
+++ b/Documentation/imports/handbook-terminology.md
@@ -0,0 +1,144 @@
+# Handbook: Terminology
+
+
+
+***
+
+## PLEASE NOTE THAT THIS IS A WORK IN PROGRESS DOCUMENT
+
+***
+
+## The IO Foundation
+
+### Human Rights (HR) advocacy
+
+The advocacy bringing forward the observance of the Human Rights that are conferred to people.
+
+### Physical Harm (PH)
+
+### Physical Harmful Action (PHA)
+
+### Physical Harmful Outcome (PHO)
+
+### Human Rights (HR)
+
+Human Rights: Always use “Human Rights” and not “human rights”.
+
+### Data-Centric Digital Rights (DCDR) advocacy
+
+The advocacy bringing forward the observance of the Digital Rights to be applied over data to protect it from its undue usage or extinction.
+
+### Digital Harm (DH)
+
+Any algorithmic action that may bring closer the extinction of a given data point.
+
+### Digital Harmful Action (DHA)
+
+Any algorithmic decision that will result in the occurrence of a Digital Harm.
+
+### Digital Harmful Outcome (DHO)
+
+The resulting damaging outcome, be it over the Representational Entity or its Source Entity, that will result in Digital or Physical Harm.
+
+### Digital Right (DR)
+
+An algorithmic action that proactively prevents the occurrence of a Digital Harm on a given data point.
+
+Digital Rights: Always use “Digital Rights” and not “digital rights”.
+
+### Harm
+
+Any harm applied, be it Physical (PH) or Digital (DH).
+
+### Harmful Action
+
+Any harmful action, be it Physical (PHA) or Digital (DHA).
+
+### Harmful Outcome
+
+Any harmful outcome, be it Physical (PHO) or Digital (DHO).
+
+### Endpoint ID
+
+A unique identifier that allows an emitter A to send a message to a receptor B unequivocally. Examples:
+
+* Email address
+* Telegram username
+* Mobile number
+* Physical address
+
+### Member
+
+Any person officially involved in the implementation of projects under The IO Foundation. This includes from staff to volunteers.
+
+#### Personal characteristic dimension (PCD)
+
+#### Staff
+
+#### volunteer
+
+#### Director
+
+#### Adviser
+
+#### Counselor
+
+### Contributors
+
+#### Individuals
+
+**Event Participants**
+
+**Project Contributors**
+
+#### Organizations
+
+**Partner**
+
+**Project "contractuals"**
+
+Ex GPD.
+
+**Media**
+
+## Documents, Handbooks and Policies
+
+### Engagement Document
+
+### Media Channel
+
+A list of Channels & their usage per Team can be found here: @@@
+
+### Share
+
+Any action that involves disseminating information. From publishing, posting online, forwarding 3rd party content, interacting with 3rd party content (likes, etc.), participating through Comments,
+
+### Content
+
+Any sort of posts + Comments + Reactions
+
+### 3rd Party Content
+
+Any Content, Comment or Reaction shared by an organization other than The IO Foundation.
+
+### #Tags
+
+There is a list of approved #Tags [here](https://tiof.click/Tags)
+
+### Update Mode
+
+#### Targeted::Crowd
+
+#### Targeted::101
+
+#### Cast::Global
+
+#### Cast::Segment
+
+## IT, Communications Systems and Infrastructure
+
+### Digital Credentials
+
+## Other
+
+### DataSet Layer (DSL)
diff --git a/Documentation/imports/handbooks.md b/Documentation/imports/handbooks.md
new file mode 100644
index 0000000..44a1306
--- /dev/null
+++ b/Documentation/imports/handbooks.md
@@ -0,0 +1,6 @@
+# Handbooks
+
+\\\
+!\[logo]\(https://user-images.githubusercontent.com/9198668/103214045-6c668e00-494a-11eb-94bb-4246857b8380.png)
+
+## Summary of Handbooks
diff --git a/Documentation/imports/hey-big-tech-declaration-1.md b/Documentation/imports/hey-big-tech-declaration-1.md
new file mode 100644
index 0000000..ace395e
--- /dev/null
+++ b/Documentation/imports/hey-big-tech-declaration-1.md
@@ -0,0 +1,17 @@
+# Hey Big Tech! declaration
+
+
+
+### To the citizen
+
+The IO Foundation has used this platform with the sole purpose of communicating information related to its advocacy and events. We understand that its usage may have become fundamental in your daily activities and needs. It is important to understand, however, that this platform may be collecting more information about you than you expect or wish or even consented to. We encourage you to take a stand on this matter and demand that the platform operates under the principle of Rights by Design. Should the platform not change in the way they operate, we encourage you to stop using it and move towards alternatives that focus on keeping your data secure and away from abuse.
+
+### To Big Tech
+
+The IO Foundation has used your platform with the sole purpose of communicating information related to its advocacy and events. We do not endorse in any way possible malpractices on collecting users' data as a result of their interaction with it and invite you to revisit your business model accordingly. In particular, we invite you to revise your technology stack and pivot towards the observance of the Rights by Design principle.
+
+### About general use TIOF of Social Media
+
+The IO Foundation believes that free, open communication is key to face and solve the challenges that digital societies are experiencing and therefore any technological means of communication should enable the discovery of solutions. We deplore "Cancel culture" and invite citizens and platforms to be more open and acceptant of both scientific facts (those that made possible the existence of technology to being with) and opinions that may not conform to mainstream ideologies.
+
+Back to top
diff --git a/Documentation/imports/hey-big-tech-declaration.md b/Documentation/imports/hey-big-tech-declaration.md
new file mode 100644
index 0000000..ace395e
--- /dev/null
+++ b/Documentation/imports/hey-big-tech-declaration.md
@@ -0,0 +1,17 @@
+# Hey Big Tech! declaration
+
+
+
+### To the citizen
+
+The IO Foundation has used this platform with the sole purpose of communicating information related to its advocacy and events. We understand that its usage may have become fundamental in your daily activities and needs. It is important to understand, however, that this platform may be collecting more information about you than you expect or wish or even consented to. We encourage you to take a stand on this matter and demand that the platform operates under the principle of Rights by Design. Should the platform not change in the way they operate, we encourage you to stop using it and move towards alternatives that focus on keeping your data secure and away from abuse.
+
+### To Big Tech
+
+The IO Foundation has used your platform with the sole purpose of communicating information related to its advocacy and events. We do not endorse in any way possible malpractices on collecting users' data as a result of their interaction with it and invite you to revisit your business model accordingly. In particular, we invite you to revise your technology stack and pivot towards the observance of the Rights by Design principle.
+
+### About general use TIOF of Social Media
+
+The IO Foundation believes that free, open communication is key to face and solve the challenges that digital societies are experiencing and therefore any technological means of communication should enable the discovery of solutions. We deplore "Cancel culture" and invite citizens and platforms to be more open and acceptant of both scientific facts (those that made possible the existence of technology to being with) and opinions that may not conform to mainstream ideologies.
+
+Back to top
diff --git a/Documentation/imports/home.md b/Documentation/imports/home.md
new file mode 100644
index 0000000..7b354fe
--- /dev/null
+++ b/Documentation/imports/home.md
@@ -0,0 +1,172 @@
+# Home
+
+
+
+### NOTE: Welcome to the TIOF wiki! This section will be used for technical reference on TIOF's projects and is currently a work in progress.
+
+## Table of Contents
+
+1. About TIOF
+ * Advocacy
+ * Mission
+ * Vision
+ * Values
+2. TIOF's Principles
+ * I Am My Data
+ * End Remedy
+ * Rights By Design
+3. Publications
+4. Events
+5. Engaged Individuals
+6. Partner Network
+7. Acknowledgments
+8. Attributions
+
+Pending:
+
+* Org Chart
+* Project structure
+
+***
+
+## About TIOF
+
+The IO Foundation (TIOF) is a global for-impact NGO advocating for Data-Centric Digital Rights. Born from a fundamental concern about the state of Digital Rights in the world, its mission is to promote, protect and provide solutions for Digital Rights, thus aiming to bridge technological and humanitarian perspectives. As data becomes an increasingly powerful economic, political, and social force, programmers are emerging as the next generation of Human and Digital Rights defenders. Following its vision of a world where Human Rights and Digital Rights are one and the same, TIOF aims to raise awareness of the importance of Digital Rights in collaboration with other organizations, both from civil society and bodies of governance.
+
+Back to top
+
+### Advocacy
+
+The IO Foundation's advocacy is Data-Centric Digital Rights.
+
+Back to top
+
+### Mission
+
+To promote, protect and provide solutions for Digital Rights.
+
+Back to top
+
+### Vision
+
+A world where Human Rights and Digital Rights are one and the same.
+
+Back to top
+
+### Values
+
+The IO Foundation delivers its mission through the observance of the following values:
+
+#### Community
+
+Because upholding Human and Digital Rights is a global endeavor that requires the active participation of everyone.
+
+#### Accountability
+
+#### Impact
+
+Because we recognize the importance of preserving and protecting our own Rights through public awareness by inspiring organizations and individuals to be active agents of change.
+
+## TIOF's Principles
+
+### I Am My Data
+
+### End Remedy
+
+### Rights By Design
+
+Back to top
+
+### Structure
+
+Org Structure
+
+Org Nomenclature
+
+Org Chart
+
+## Dhatham House Rule
+
+The DHATHAM v0.5 House Rule, which is an evolution from the CHATHAM House rule in response to the new digital realities, stipulates:
+
+When a digital interaction, or part of thereof, is held under the DHATHAM House Rule, participants are free to use the information received and to produce digital materials (audio, photos, video) yet neither the identity nor the affiliation of contributors or participants may be revealed, tagged or implied without their expressed consent.
+
+In other words, be considerate and ask for permission before capturing a digital representation of others or posting about them on social media or any other digital medium.
+
+Note: The Dhatam House Rule is a live statement that is open for adaptation and improvements.
+
+To participate in the next iteration of the rule, check the [Dhatam House Rule live discussion](http://tiof.click/DhathamBuild).
+
+## Publications
+
+The IO Foundation regularly publishes articles, research papers and other documents such as comments on public consultations related to its advocacy. You can access TIOF's publications [here](https://www.theiofoundation.org/publications)
+
+## Events
+
+The IO Foundation regularly organizes events and participates in international fora where the organization puts forward its advocacy and engages with all stakeholders. You can access TIOF's events [here](https://www.theiofoundation.org/events)
+
+## Engaged Individuals
+
+TIOF's advocacy is made possible by the collaboration of a number of organizations and individuals.
+
+Using a number of volunteer recruitment platforms, over 150 individuals have participated in the advocacy, of which more than 50 are currently active. A Credits page is under development.
+
+Back to top
+
+## Partner Network & Collaborating organizations
+
+Project Lockdown has created a network of partner organizations that actively collaborate in a diverse range of areas.
+
+###  The IO Foundation
+
+[The IO Foundation (TIOF)](https://www.theiofoundation.org)is a global non-profit organization advocating for Data-Centric Digital Rights. Born from a fundamental concern about the state of Digital Rights in the world, its mission is to promote, protect and provide solutions for Digital Rights, thus aiming to bridge technological and humanitarian perspectives. As data becomes an increasingly powerful economic, political, and social force, programmers are becoming the next generation of human rights defenders. There remains, however, a limited international understanding of the impact of technology on human rights. Following its vision of a world where Human Rights and Digital Rights are one and the same, TIOF aims to raise awareness of the importance of Digital Rights in collaboration with other organizations, both from civil society and bodies of governance.
+
+###  Code for All
+
+[Code for All](https://codeforall.org) is an international network of civic tech organizations that drive change through digital technology, citizen participation, collaborative decision-making and good governance to deliver solutions for social challenges while improving the relationship between governments and citizens.
+
+The network enables individual organizations to scale by leveraging international resources, sharing expertise and promoting shared funding to tackle social issues collectively. Our diversity allows for varied approaches and solutions, while motivating alternative and modern methods for government.
+
+### Code for NL
+
+[Code for NL](https://www.codefor.nl) is a member of the Code for All network and a key stakeholder in the initial development of Project Lockdown.
+
+###  Netmission
+
+Supported by [DotAsia Organisation](https://dot.asia), [NetMission.Asia](https://netmission.asia) is an initiative designed to empower young minds and to constructively contribute to the local, regional and global Internet governance discourse through organizing the Hong Kong Youth Internet Governance Forum (HKyIGF), international conferences and community projects. NetMission.Asia has been actively participating in various Internet conferences both regionally and globally, including ICANN meetings, IGF, APrIGF, Asia Pacific Internet Governance Academy (APIGA) and the Asia Pacific Next Generation Camp (APNG Camp) among others.
+
+###  Open Development Mekong
+
+[Open Development Initiative (ODI)](https://opendevelopmentmekong.net/en/), a project of [East-West Management Institute (EWMI)](http://ewmi.org), stimulates public demand, builds coalitions, and offers a constantly evolving platform to support the transparent sharing and analysis of data to improve and inform constructive dialogue and decision-making for sustainable and equitable development.
+
+Back to top
+
+## Acknowledgments
+
+The IO Foundation would like to thank the following organizations for their support in making our advocacy possible:
+
+|  |  |  |  |  |  |
+| :------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------: | :---------------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------: | :----------------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------------------------------: |
+| [Mapbox](https://www.mapbox.com) | [Netlify](https://www.netlify.com) | [Internews](https://internews.org) | [Figma](https://www.figma.com) | [Cloudflare](https://www.cloudflare.com) | [National Democratic Institute](https://www.ndi.org) |
+
+|  |  |  |  |  |  |  |
+| :-----------------------------------------------------------------------------------------------------------: | :--------------------------------------------------------------------------------------------------------------: | :------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------: | :------------------------------------------------------------------------------------------------------------: | :------------------------------------------------------------------------------------------------------------: |
+| [Kualo](https://www.kualo.com) | [Start.me](https://start.me) | [Zapier](https://zapier.com) | [Dataedo](https://dataedo.com) | [Postman](https://www.postman.com) | [BASAAS](https://www.basaas.com) | [hotjar](https://hotjar.com) |
+
+|  |  |  |  |  |
+| :------------------------------------------------------------------------------------------------------------------: | :------------------------------------------------------------------------------------------------------------: | :---------------------------------------------------------------------------------------------------------------------------------: | :--------------------------------------------------------------------------------------------------------------: | :------------------------------------------------------------------------------------------------------------------: |
+| [Time is Ltd.](https://www.timeisltd.com/org-chart) | [ZenHub](https://www.zenhub.com) | [European Innovation Council](https://ec.europa.eu/research/eic/index.cfm) | [POEditor](https://poeditor.com) | [Stoplight.io](https://stoplight.io) |
+
+Back to top
+
+## Attributions
+
+The following resources have been used across TIOF's projects.
+
+* Icons made by [Eucalyp](https://www.flaticon.com/authors/eucalyp) from [www.flaticon.com](https://www.flaticon.com).
+* Icons made by [Font Awesome](https://fontawesome.com) from [www.flaticon.com](https://www.flaticon.com).
+* Icons made by [Pixel perfect](https://www.flaticon.com/authors/pixel-perfect) from [www.flaticon.com](https://www.flaticon.com).
+* Images by [Unsplash](https://unsplash.com).
+* [Material Icons](https://material.io/resources/icons/?style=baseline) by Google.
+
+Back to top
diff --git a/Documentation/imports/infrastructure-calendar.com.md b/Documentation/imports/infrastructure-calendar.com.md
new file mode 100644
index 0000000..8533af0
--- /dev/null
+++ b/Documentation/imports/infrastructure-calendar.com.md
@@ -0,0 +1,17 @@
+# Infrastructure: Calendar.com
+
+
+
+## About
+
+## Usage
+
+* Booking of meetings
+
+## Information
+
+## Object Model
+
+This section describes the object model used in this App.
+
+See render here:
diff --git a/Documentation/imports/infrastructure-custom-fields.md b/Documentation/imports/infrastructure-custom-fields.md
new file mode 100644
index 0000000..85ba649
--- /dev/null
+++ b/Documentation/imports/infrastructure-custom-fields.md
@@ -0,0 +1,105 @@
+# Infrastructure: Custom Fields
+
+## IMPORTANT
+
+All field syncs follow the route
+
+App A >> SF >> App B
+
+In other words, 2 Apps won't be synchronizing data between themselves. Any sync MUST involve App A pushing the data to Salesforce and pulling it from it towards App B.
+
+## Salesforce
+
+### Accounts
+
+#### Segments
+
+### Contacts
+
+#### Time Zones
+
+Time Zones Source: https://msdn.microsoft.com/en-us/library/ms912391(v=winembedded.11).aspx Customization:
+
+* Joined fields
+* Added GMT >> UTC/GMT
+
+Time Zone Area
+
+#### Segments
+
+## Encharge
+
+Custom fields are organized in Folders whose name corresponds to TIOF project codes. \[TIOF] \[TIOF TU] etc.
+
+Inside each Folder are stored the corresponding Project's Custom Fields.
+
+Custom fields take the sane name as in Salesforce.
+
+### Segments
+
+### Field correspondance
+
+| Salesforce | Encharge.io | Notes |
+| --------------------------------------------- | --------------------------------------------- | --------------------------------------------------------------------------------------------- |
+| Email | email | |
+| ??? | firstName | |
+| ??? | lastName | |
+| Name | name | |
+| npsp\_\_Primary\_Affiliation\_\_c | company | |
+| TIOF\_Website\_\_c | website | |
+| ??? | salutation | |
+| Title | title | |
+| ??? | leadScore | |
+| ??? | userId | |
+| ??? | updatedAt | |
+| HasOptedOutOfEmail | unsubscribed | |
+| ??? | id | |
+| ??? | enchargeAnonymousId | |
+| ??? | segmentAnonymousId | |
+| ~~Phone~~ | phone | Do NOT sync |
+| ~~MailingAddress~~ | address | Do NOT sync |
+| ??? | country | |
+| ??? | city | |
+| ??? | state | |
+| ~~???~~ | postcode | Do NOT sync |
+| TIOF\_Time\_Zone\_\_c | timezone | |
+| ??? | groupId | |
+| ??? | referrer | |
+| ??? | firstReferrer | |
+| ??? | UTMSource | |
+| ??? | UTMMedium | |
+| ??? | UTMTerm | |
+| ??? | UTMContent | |
+| ??? | UTMCampaign | |
+| ??? | firstUTMSource | |
+| ??? | firstUTMMedium | |
+| ??? | firstUTMTerm | |
+| ??? | firstUTMContent | |
+| ??? | firstUTMCampaign | |
+| ??? | landingPage | |
+| N/A | ip | Do NOT sync |
+| N/A | platform | Do NOT sync |
+| N/A | browser | Do NOT sync |
+| N/A | deviceType | Do NOT sync |
+| N/A | device | Do NOT sync |
+| PENDING | unsubscribeReason | |
+| ??? | MRR | |
+| ??? | trialStart | |
+| ??? | trialEnd | |
+| ??? | deletedAt | |
+| ??? | validationResult | |
+| ??? | validationConfidence | |
+| ??? | isEmailDisposable | |
+| ??? | isEmailRole | |
+| N/A | TIOF\_Sync\_Status | This is an internal indicator for Encharge |
+| LeadSource | LeadSource | x |
+| ??? | Rolling | |
+| Title | Title | |
+| N/A | Airmeet\_Registration | To be updated to: TIOF\_Airmeet\_Registration / To be deprecated and introduced in LeadSource |
+| TIOF\_Segment\_TU\_Open\_Source\_Project\_\_c | TIOF\_Segment\_TU\_Open\_Source\_Project\_\_c | |
+| TIOF\_Segment\_TU\_Organization\_\_c | Segment\_Organization | To be updated to: TIOF\_Segment\_TU\_Organization\_\_c |
+| TIOF\_Segment\_TU\_Speaker\_\_c | Segment\_Speaker | To be updated to: TIOF\_Segment\_TU\_Speaker\_\_c |
+| TIOF\_Segment\_TU\_Audience\_\_c | Segment\_Audience | To be updated to: TIOF\_Segment\_TU\_Audience\_\_c |
+| TIOF\_Segment\_TIOF\_Newsletter\_\_c | Segment\_Newsletter | To be updated to: TIOF\_Segment\_TIOF\_Newsletter\_\_c |
+| TIOF\_Time\_Zone\_Area\_\_c | TIOF\_Time\_Zone\_Area\_\_c | |
+| | | |
diff --git a/Documentation/imports/infrastructure-encharge.io.md b/Documentation/imports/infrastructure-encharge.io.md
new file mode 100644
index 0000000..74857ed
--- /dev/null
+++ b/Documentation/imports/infrastructure-encharge.io.md
@@ -0,0 +1,25 @@
+# Infrastructure: Encharge.io
+
+
+
+## About
+
+## Usage
+
+Email automation.
+
+## Information
+
+### App Name
+
+### Logo
+
+### Description
+
+###
+
+## Object Model
+
+This section describes the object model used in this App.
+
+See render here:
diff --git a/Documentation/imports/infrastructure-funnels.md b/Documentation/imports/infrastructure-funnels.md
new file mode 100644
index 0000000..69ed03d
--- /dev/null
+++ b/Documentation/imports/infrastructure-funnels.md
@@ -0,0 +1,122 @@
+# Infrastructure: Funnels
+
+
+
+## Funnel Model
+
+See render here:
+
+http://www.plantuml.com/plantuml/png/fLdXSjku4VxFfy1bvdhEN6DVqavxun\_jqR9igsT7gcadwKndEX2v4d4X0HO0xNCwdUbhzFNw9CKIeBY2c4ZdymzXzyFtBK5W0H3m3yPoRTkwIapEAs2lltlpU\_Oe2bi6u8z\_-9wL8DQbJPAl2bW92KmPld0ILbhRcDEJ4yqVZzV2bksoDQ1p9Ir8Uvoh-cIYkIcXg8KiJXOLb\_R-vlgLQa0Qo5ijx1FNUIaivBRLyEQLS5fpKdDZGITV2PbNRR5vtCb4rRMInuspToll3UWJNbMVgRxYkdZa6hv0kH4c\_q9r1le1z9S8mfBmIV8DIulYr1LPnVEFB6qQmxvbPyeQXrqgjQw0dQlS84r91DylsA9grq8Qftxr2\_-SVYPNcXkhswuxsKKh9LGciMeDjWJD\_fKem\_zHWFbeLNDqcRN2mc\_P2s-yS5QMfXcMldKlNexmKnpCZOXrxcUb5MzGcV4Ap4hf79ysE4H6KIyLYr99EBhiqieHl44bDoBNogYLtLPqlOqqB0zvn1atd1j7y0QLU2JGJPS0H\_9xV7ttYuGhPImKBpnmB5JKPMVLiP3O66\_Gq1w9-E-LBXeD1bkpiQagRQsgkRKYZvGJBX-u8tGbKNWW8b-8TOraB0dP0p7P3-WD5nME0fPZmytOY6Z2Av05rniUwv6zoUR1SoqUO51txg5IbHkYTDw1mgm4i4Jg\_KF5bIY0Yj4\_L7oXT4sqw1ug\_H6W6PJe7IZy2w-NYkjY4FV8tW3pTxEvgyE2Sj6FcAdGDO1rbS6Y\_035CmUi1NtVM55Z0b2NYYaUHUXJ3VSXnwGkZK3nAC9KvYNNQpWMoX69H\_K4ZkH\_RVWQszwLHEA1CV9Shp6Ych750PAxfmRE5FQg-sMBYjkLqZLL1KQakqtFq\_JMLNk32ZmIZ\_C3w8e\_kUfWKKM0uhvN3m-GvLmwHcSpT8ZEev7AJT9pzOYQO551W2B95Voi7hdDIyVOs4I68C\_jYAhc5e88pRsQJAmbnssrmfuW7bKIECubRfucbMfnk3Rs82LW95meuuggwygDJOG4ZFQInU--UtqBXT2Gssv3MJ27i0r4Wtpuy67akNpDNLsmA3r0yJi-WBI0lHeiAWbGl1DL0FzqjLr9w1w8o3Fv80h0kHWiAWXGF6hODVZnwkSmTQcOuaT\_VZdI5RKV06zHQO1sLMTQFHhGcVMV8zIbUehl1kdWQI4iAdfxa1DmLtifx9bI-EnWKLs0TbLNBjxDkU-kZJqe2RYhlU5MrIZq1bLvPEG5bUGQyxv0CZgiywYMm6mtGhgOtK7TLDo6XPe2jEbnZO-5t-cJalilPHhtMiYFKCnms7jpzEipNfKV1Mv9ZX4iAWfGB84ArfhNI0Zc829OD7Lu3ai\_lhqvg0WMpo5ZUNZOnjwlmqJKzhW6P0PpK14iscgop5MwNyhjFsp9KD85PAdzgMHmY9YWSUu1sBPn36zGZKTsPqUk\_4d6MrGH8CmEp8yB8RdC8UeGBHfifpUesYFnSYmCih6WNFGZvltyp5MuNyf3DzvZXLpoBgWtIM22HIf\_ZCeQ9OtIPdEkOZroI8gVAwdqcVhPKNgJo0OiMW\_Rfnj89sgr0copSzaDi9HvX0QWJ9yaqUcYLFQdxbJX3QhrIDnLk7IiAgxnmOD3T0IDjEcdjfDrvI6zaxx7d7U\_b9pM\_9FQsQ5XYUT78TUEuHmMF2hyiUMLskd\_cWlvbjUmq0ftFVtQCJtA46OzJYDXHLu2RtvzDDAk9C71sKwnIYrvTSujdqghyMl98mmXrc5xpnPuL-IkYgx5KlCkH01OGAB9UjKkVQByEqd8DGLxzUfFpFkdx6usls0tK2z16rPpsV8A2xw66gGDiaunN1H4AlCaysIefU7t4yCvXp9n0gPj8K3YpSWyox2hV\_AVQtEzvb9yubOeEHvmkuzEsNrJS0jT-6zCNyigNqtUpzz7ZRIOSlooi8VahqVsaFoCt4EYzmKRSkyoRenOnwFKJSYniEJgOEjLCbV9BaG59l6GhntOMnHohjj9YecIbkVMiD-m3Bg6ZOyGYV454Pxj3acy\_eY8JAyvPNXMpDfbBOmHIYRHrDi9UWsy2D56fdr7too4s0RDfLc1Pcypvgy\_3ViMNsGbrYC1tloo0CFoXxBDTTSf2sZoh4lGool63MlyF6Avql2v-y\_vOdgRkcv-Y-irBYG347dHHyrqCSzcT\_FRlmNTBJJA2AlyilIQPQh5350hz\_wjBIFvz1or\_JE3Hyo8\_cusVJ\_Tq8D7JLpqXhPsGp2qq0q1Dn\_3a0ymaeXcY-MRiHi83nbiU5LMSCkZaA59f-oTW4VA5HAl9hgrx7cZwXFtMgmWVyghpmvfH\_FTRqAF8SG2X7u63w1vXRqS2zygU-lAfw0S9axaZKWd5N1vtpn3-TmdtXi8gdInoEYROKBGZi2HsNe\_lyvvZCraibN9a4xVwPHr1ciR3oUqSc3taS5w7sTXXoL3jIVxncyrOjxQ97bUPeHj3vTLJ3YDAyV-HF6YxKpnMFYdIPmgiTG\_QrlA0eZ80dI\_cO\_g9\_YvNGaqY-qWj0RXzwMgWCrlBwCu\_Q4rg7itpeIjD-s6Q-i5uboWbPHEMnLdn8YeRyreGkn6Z3KZcN4vVJkzdKtOtVHcSPtUJRFjqrYQuX99FmlZUmrbXgxsJc0boKef2vfzlH8LI5x3qKkcGHQWeM2FmfQi\_zSbmnrCACc-3iRHox\_BknBObR1vMOgFeF\_td\_yQTjcA0fXL6s7oWulNrjN\_0G00
+
+### 20 [Google Calendar](http://tiof.click/DocsInfrastructureGCalendar) >> \[Slack]\(http://TIOF.Click/DocsInfrastructureSlack
+
+)
+
+* When a meeting is rescheduled send notification to corresponding Slack Team channel or to involved users. Issues: # Status: Manual / Automatic
+
+### 30 MEC >> [Google Calendar](http://tiof.click/DocsInfrastructureGCalendar)
+
+* Create events as per sessions
+* Add all attendees & Speakers & Organizations
+
+### 40.1 [Github](http://tiof.click/DocsInfrastructureGithub) >> Reporting Channels
+
+* Central report (> Issues) (Weekly / Quarterly / Yearly)
+* Update Crowdfunding channels
+* Update Community channels
+
+### 40.2 [Github](http://tiof.click/DocsInfrastructureGithub) >> [Github](http://tiof.click/DocsInfrastructureGithub)
+
+* Action: Convert folder-based wiki pages to Repo Wiki https://github.com/marketplace?query=wiki
+* Action: Convert PlanUML diagrams https://github.com/marketplace/actions/render-plantuml-to-wiki https://github.com/marketplace/actions/generate-plantuml
+* Action: Auto generate Quickbar based on settings file
+* Action: Auto generate Wiki Table of Contents
+
+### 50 [LinkedIn](http://tiof.click/DocsInfrastructureLinkedIn) >> [Salesforce](https://tiof.click/DocsInfrastructureSalesforce)
+
+* Consolidate LinkedIn followers + connections to Salesforce
+* Update LinkedIn info to SF Contacts & Accounts
+
+### 51 Google Email >> [Salesforce](https://tiof.click/DocsInfrastructureSalesforce)
+
+* Consolidate leads to Salesforce
+
+### 51 Global Data Entry >> [Salesforce](https://tiof.click/DocsInfrastructureSalesforce)
+
+### 52 [Encharge.io](http://tiof.click/DocsInfrastructureEnchargeIO) >> [Salesforce](https://tiof.click/DocsInfrastructureSalesforce)
+
+* Sync Contacts
+
+### 60 [Salesforce](https://tiof.click/DocsInfrastructureSalesforce) >> [Encharge.io](http://tiof.click/DocsInfrastructureEnchargeIO)
+
+* Sync Contacts
+* Sync Segments
+
+### 60.1 [Salesforce](https://tiof.click/DocsInfrastructureSalesforce) >> [Salesforce](https://tiof.click/DocsInfrastructureSalesforce)
+
+* For every Account generate a Linked Contact
+ * Duplicate all basic information (Name, Channels, Address, etc.) to Linked Contact
+ * Make Linked Contact as Primary Contact for the Account
+
+### 70.1 [QPage](http://tiof.click/DocsInfrastructureQPage) >> [Github](http://tiof.click/DocsInfrastructureGithub)
+
+* Publish on Github the Jobs defined in QPage
+
+### 70.2 [QPage](http://tiof.click/DocsInfrastructureQPage) >> [Salesforce](https://tiof.click/DocsInfrastructureSalesforce)
+
+* Consolidate candidates to Salesforce
+
+### 80 [Calendar.com](http://tiof.click/DocsInfrastructureCalendarCOM) >> [Google Calendar](http://tiof.click/DocsInfrastructureGCalendar)
+
+* When slot is booked, ensure settings are as per SOP (Name, Meeting link, Time zone)
+
+### 90 ??? >> APITemplate.io
+
+* Generate banners for TechUp
+ * General Monthly event
+ * Speakers banners
+ * Orgs banners
+ * OSS banners
+
+### 90.1 [Salesforce](https://tiof.click/DocsInfrastructureSalesforce) >> APITemplate.io >> Google Drive
+
+* Generate Profile Pictures
+
+## 1000 Legal
+
+* When address changes
+ * Notify Accounts + Contacts
+ * Update Channels
+
+***
+
+## PlantUML diagram source.
+
+@startuml scale 1024 width scale 768 height
+
+!define osaPuml https://raw.githubusercontent.com/Crashedmind/PlantUML-opensecurityarchitecture2-icons/master !include osaPuml/Common.puml !include osaPuml/User/all.puml !include osaPuml/Hardware/all.puml !include osaPuml/Misc/all.puml !include osaPuml/Server/all.puml !include osaPuml/Site/all.puml
+
+!Add: ! Slack Apps + Bots ! Google Docs Addons ! WP Plugins
+
+'------------------------------------------------ ' Infrastructure Funnels together { osa\_desktop(GSuite, "GSuite", "SAAS", "Google") osa\_desktop(GSuiteAdmin, "GSuite Admin", "SAAS", "Google") osa\_laptop(Salesforce, "Salesforce", "SAAS", "Salesforce") osa\_iPhone(Github, "Github", "SAAS", "Microsoft") osa\_iPhone(Slack, "Slack", "SAAS", "Salesforce") osa\_iPhone(Basaas, "Basaas", "SAAS", "Basaas") osa\_server(n8n, "n8n", "Hosted", "n8n.io") osa\_desktop(Bl.ink, "Bl.ink", "SAAS", "Bl.ink") osa\_desktop(Wordpress, "Wordpress", "SAAS", "Automattic") osa\_desktop(Canva, "Canva", "SAAS", "Canva") osa\_desktop(Figma, "Figma", "SAAS", "Figma") osa\_desktop(GoogleMail, "GMail", "SAAS", "Google")\
+osa\_desktop(GoogleCalendar, "Google Calendar", "SAAS", "Google") osa\_desktop(GoogleDrive, "Google Drive", "SAAS", "Google") osa\_desktop(GoogleDocs, "Google Docs", "SAAS", "Google") osa\_desktop(GoogleSheets, "Google Sheets", "SAAS", "Google") osa\_desktop(GoogleSlides, "Google Slides", "SAAS", "Google") osa\_desktop(GoogleForms, "Google Forms", "SAAS", "Google") osa\_desktop(GoogleKeep, "Google Keep", "SAAS", "Google") osa\_desktop(GoogleJamboard, "Google Jamboard", "SAAS", "Google") osa\_desktop(OVIO, "OVIO", "SAAS", "OVIO") osa\_desktop(Airmeet, "Airmeet", "SAAS", "Airmeet") osa\_desktop(BetterUptime, "BetterUptime", "SAAS", "BetterUptime") osa\_desktop(Calendar.com, "Calendar.com", "SAAS", "Calendar.com") osa\_desktop(Encharge.io, "Encharge.io", "SAAS", "Encharge.io") osa\_desktop(Qpage, "Qpage", "SAAS", "Qpage") osa\_desktop(QpageOrg, "EoI Page", "SAAS", "Qpage") osa\_desktop(TypeBot, "Bot Platform", "SAAS", "TypeBot") osa\_desktop(RADAAR, "RADAAR", "SAAS", "RADAAR") osa\_desktop(Overlay, "Overlay", "SAAS", "Overlay") osa\_desktop(CovveScan, "Covve Scan", "SAAS", "Covve") osa\_desktop(DocDown, "DocDown", "SAAS", "DocDown") osa\_desktop(Hexowatch, "Hexowatch", "SAAS", "Hexact") osa\_desktop(Hexomate, "Hexomate", "SAAS", "Hexact") osa\_desktop(Signaturely, "Signaturely", "SAAS", "Signaturely") osa\_desktop(EasyClout, "EasyClout", "SAAS", "EasyClout") osa\_desktop(Postoplan, "Postoplan", "SAAS", "Postoplan") osa\_desktop(WP301Redirects, "WP 301 Redirects", "SAAS", "XXX") osa\_desktop(Postaga, "Postaga", "SAAS", "Postaga") osa\_desktop(Eventee, "Eventee", "SAAS", "Eventee") osa\_desktop(Fleeq, "Fleeq", "SAAS", "Fleeq") osa\_desktop(Invideo, "Invideo", "SAAS", "Invideo") osa\_desktop(Stoplight.io, "Stoplight.io", "SAAS", "Stoplight.io(?)") osa\_desktop(Postman, "Postman", "SAAS", "Postman(?)") osa\_desktop(BrowserStack, "BrowserStack", "SAAS", "BrowserStack(?)") osa\_desktop(StackEdit, "StackEdit", "SAAS", "StackEdit(?)") osa\_desktop(GitBook, "GitBook", "SAAS", "GitBook(?)") osa\_desktop(HackMD.io, "HackMD.io", "SAAS", "HackMD.io(?)") osa\_desktop(Matomo, "Matomo", "SAAS", "Matomo(?)") osa\_desktop(SonarCloud, "Sonar Cloud", "SAAS", "Sonar Cloud (?)") osa\_desktop(APITemplate.io, "APITemplate.io", "SAAS", "APITemplate.io (?)")
+
+' Channels osa\_desktop(LinkedIn, "LinkedIn", "SAAS", "Microsoft") osa\_desktop(Twitter, "Twitter", "SAAS", "Twitter") osa\_desktop(Telegram, "Telegram", "SAAS", "Telegram") osa\_desktop(Facebook, "Facebook", "SAAS", "Facebook") osa\_desktop(Instagram, "Instagram", "SAAS", "Facebook") osa\_desktop(Start.me, "Start.me", "SAAS", "Start.me") osa\_desktop(RSS, "RSS", "SAAS", "Wordpres(?)") osa\_desktop(Eventbrite, "Eventbrite", "SAAS", "Eventbrite") osa\_desktop(Meetup, "Meetup", "SAAS", "Meetup") osa\_desktop(Gitcoin, "Gitcoin", "SAAS", "Gitcoin")
+
+' Finance osa\_desktop(Stripe, "Stripe", "SAAS", "Stripe") osa\_desktop(Wise, "Wise", "SAAS", "Wise") osa\_desktop(UOB, "UOB", "SAAS", "UOB") osa\_desktop(Coinbase, "Coinbase", "SAAS", "Coinbase") osa\_desktop(GithubSponsors, "Github Sponsors", "SAAS", "Microsoft") osa\_desktop(DonorBox, "DonorBox", "SAAS", "DonorBox") osa\_desktop(BuyMeACoffee, "Buy Me A Coffee", "SAAS", "BuyMeACoffee(?)")
+
+osa\_desktop(hotjar, "hotjar", "SAAS", "hotjar") osa\_desktop(Cloudflare, "Cloudflare", "SAAS", "Cloudflare") osa\_desktop(Azure, "Azure", "SAAS", "Microsoft") osa\_desktop(AWS, "AWS", "SAAS", "Amazon") osa\_desktop(WebHosting, "Web Hosting", "SAAS", "Kualo") osa\_desktop(DomainNameProvider1, "Domain Name Provider", "SAAS", "Namecheap") osa\_desktop(DomainNameProvider1, "Domain Name Provider", "SAAS", "Kualo")
+
+osa\_desktop(GlobalDataEntry, "Global Data Entry", "SAAS", "Google") osa\_desktop(PlanUMLLibrary, "PlanUML Library", "SAAS", "GitHub(?)") }
+
+GSuiteAdmin --> GSuite: TIOF Members manual management GSuite --> Salesforce: TIOF Members sync Salesforce --> GSuite: TIOF Members sync Salesforce --> Airmeet: TIOF Members, Audience, OSS Projects, Organizations sync Salesforce --> PlanUMLLibrary: Update TIOF's PlanUML library GSuite --> Slack: TIOF Members sync GSuite --> Github: TIOF Members sync GSuite --> Basaas: TIOF Members sync GSuite --> hotjar: TIOF Members sync GSuite --> GoogleCalendar: TIOF Calendar assigment GSuite --> Azure: TIOF Members sync GoogleDrive --> Github: Sync Files Github --> GoogleDrive: Sync Files Encharge.io --> Salesforce: Contacts & Segments sync Salesforce --> Encharge.io: Contacts & Segments sync Qpage --> Salesforce: TIOF Members sync QpageOrg--> Qpage : EoI Submission GlobalDataEntry --> Salesforce: Leads sync DomainNameProvider1 --> Cloudflare: Transfer NS Servers + Config DomainNameProvider2 --> Cloudflare: Transfer NS Servers + Config WebHosting--> Wordpress: Hosting
+
+'------------------------------------------------ 'GH as project core together { osa\_desktop(OPERATIONS, "", "OPERATIONS", "OPERATIONS") osa\_desktop(REPOSITORY, "", "Repository", "1 Source of Truth") osa\_desktop(EDITORS, "", "EDITORS", "EDITORS") osa\_desktop(VIEWERS, "", "VIEWERS", "VIEWERS") } OPERATIONS --> REPOSITORY: Tasks sync REPOSITORY--> OPERATIONS : Tasks sync EDITORS --> REPOSITORY: Edit Repository data REPOSITORY--> VIEWERS: View Repository information
+
+'------------------------------------------------ 'Leads Lifecycle together { osa\_desktop(LeadsSources, "", "Lead Sources", "Several") osa\_desktop(LeadsNotReady, "", "Salesforce", "Salesforce") osa\_desktop(LeadsCleanUp, "", "Salesforce", "Salesforce") osa\_desktop(LeadsReady, "", "Salesforce", "Salesforce") osa\_desktop(LeadsUse, "", "APPS", "Several") } LeadsSources--> LeadsNotReady: Sync Leads In LeadsNotReady --> LeadsCleanUp: Clean up Leads LeadsCleanUp --> LeadsReady: Set Leads as Ready LeadsReady--> LeadsUse: Sync Leads Out
+
+'------------------------------------------------ ' Updates & Reporting Lifecycle together { osa\_desktop(UpdateSources, "", "UpdateFunnels", "Several") osa\_desktop(UpdateReports, "", "Update Reports", "Per Project") osa\_desktop(UpdateConsolidated, "", "Update Consolidated", "Whole ORG") osa\_desktop(Channels, "", "Channels", "Several") } UpdateSources --> UpdateReports: Sync Leads In UpdateReports --> UpdateConsolidated: Clean up Leads UpdateReports --> Channels: Set Leads as Ready UpdateConsolidated --> Channels: Sync Leads Out
+
+'GENERIC TEMPLATES osa\_desktop(SAAS, "", "SAAS", "") osa\_desktop(Hosted, "", "Hosted", "")
+
+footer %filename() rendered with PlantUML version %version()\nThe Hitchhiker’s Guide to PlantUML @enduml
diff --git a/Documentation/imports/infrastructure-github.md b/Documentation/imports/infrastructure-github.md
new file mode 100644
index 0000000..3facdd9
--- /dev/null
+++ b/Documentation/imports/infrastructure-github.md
@@ -0,0 +1,21 @@
+# Infrastructure: Github
+
+
+
+## About
+
+## Usage
+
+* Store repositories for all TIOF Projects
+* Project Management Back End
+* Code Management
+
+## Information
+
+See also: Github Sponsors
+
+## Object Model
+
+This section describes the object model used in this App.
+
+See render here:
diff --git a/Documentation/imports/infrastructure-google-calendar.md b/Documentation/imports/infrastructure-google-calendar.md
new file mode 100644
index 0000000..68c355f
--- /dev/null
+++ b/Documentation/imports/infrastructure-google-calendar.md
@@ -0,0 +1,17 @@
+# Infrastructure: Google Calendar
+
+
+
+## About
+
+## Usage
+
+* Keep track of tasks & events
+
+## Information
+
+## Object Model
+
+This section describes the object model used in this App.
+
+See render here:
diff --git a/Documentation/imports/infrastructure-linkedin.md b/Documentation/imports/infrastructure-linkedin.md
new file mode 100644
index 0000000..6cd5888
--- /dev/null
+++ b/Documentation/imports/infrastructure-linkedin.md
@@ -0,0 +1,17 @@
+# Infrastructure: LinkedIn
+
+
+
+## About
+
+## Usage
+
+Organization promotion and Media Channel.
+
+## Information
+
+## Object Model
+
+This section describes the object model used in this App.
+
+See render here:
diff --git a/Documentation/imports/infrastructure-qpage.md b/Documentation/imports/infrastructure-qpage.md
new file mode 100644
index 0000000..2c1bb25
--- /dev/null
+++ b/Documentation/imports/infrastructure-qpage.md
@@ -0,0 +1,19 @@
+# Infrastructure: QPage
+
+
+
+## About
+
+## Usage
+
+* Manage HR enrollment
+* Manage Partnerships
+* Manage other submissions
+
+## Information
+
+## Object Model
+
+This section describes the object model used in this App.
+
+See render here:
diff --git a/Documentation/imports/infrastructure-salesforce.md b/Documentation/imports/infrastructure-salesforce.md
new file mode 100644
index 0000000..132c98f
--- /dev/null
+++ b/Documentation/imports/infrastructure-salesforce.md
@@ -0,0 +1,61 @@
+# Infrastructure: Salesforce
+
+
+
+## About
+
+## Usage
+
+## Information
+
+## Object Model
+
+This section describes the object model used in this App.
+
+See render here: http://www.plantuml.com/plantuml/png/bP3HYnCn4CRVyrVCzULESBjwY4eVv4hXyC1YeTwpp2MpJJ2RXCd4KiJ\_tVJSdgwbnSlB9j\_C\_BxvzYOBifJUgwpH4xn-TVq6jiw87OHtRz-39RUnejI5eSu5WfXnLKV0YgGyQrl6xNJZn9Q7aebr3491fZhsxO8nMpAz2wPTUGnol\_pKn4GXaoxiP8UihHFIKfYk6rTdSzjZ5c9ruOBsnJpPjOlOzp5CKxqV5--hSulUdoX\_H3PRP3hJidHPdoclYR-VjLWx-Gklr6NppACkuIvqZ5cuFFuGk2qXaCzAueR44iCFLTs-6ihV9AQhkTQn17a9a-4sgTVrVBv-\_AAdt4NMD7ancbfYIcGMCGZg\_UplDmp2MOJ7j2UisFN8kp-8GVWlXblP6EXgtdNEEvIdJN9jFXPFedugfORKq3GVO9Hg1eSIKsBA52eI7dOmpZeT4SQfPeSc48i2srXy9L1z4LHS3Pk8SmnG5wgYomVBCVGuKTtDUpYyWCdlgo3n7qezNOn235-gvTrdkAswGN4nA7L3mPJU\_m80
+
+### Contacts
+
+Contacts are at the core of the SF Object Model.
+
+All App syncs are done based on SF Contacts.
+
+### Accounts
+
+Accounts are considered as "Groups of Contacts". They are related using the following associations:
+
+#### Mapped Contact
+
+Quantity: Only one
+
+Usage: This Contact is the necessary "twin" Contact that contains all the data relative to an Account.
+
+Rationale: Accounts are not synchronized with certain Apps (such as Google Contacts or Encharge.io) so there needs to be a Contact that carries all the necessary information. This approach also allows for a standard approach when treating SF data.
+
+#### Primary Contact
+
+Quantity: Zero or one
+
+Usage: This Contact indicates who would be the primary person to reach out when attempting to reach out to this Account.
+
+#### Affiliated Contacts
+
+Quantity: Zero or more
+
+Usage: These Contacts represent all the members that belong to this Account.
+
+***
+
+## PlantUML diagram source.
+
+@startuml scale 1024 width scale 768 height
+
+!define osaPuml https://raw.githubusercontent.com/Crashedmind/PlantUML-opensecurityarchitecture2-icons/master !include osaPuml/Common.puml !include osaPuml/User/all.puml !include osaPuml/Hardware/all.puml !include osaPuml/Misc/all.puml !include osaPuml/Server/all.puml !include osaPuml/Site/all.puml
+
+'------------------------------------------------ ' Infrastructure Funnels together { osa\_desktop(Account, "Account", "SAAS", "Salesforce") osa\_desktop(MappedContact, "Mapped Contact", "SAAS", "Salesforce") osa\_laptop(PrimaryContact, "Primary Contact", "SAAS", "Salesforce") osa\_iPhone(AffiliatedContacts, "AffiliatedContacts", "SAAS", "Salesforce") }
+
+Account --> MappedContact: Account represented by Mapped Contact. Account --> PrimaryContact: Contact that would be the entry person for this Account. Account --> AffiliatedContacts: All Contacts related to this Account.
+
+footer The IO Foundation
+
+@enduml
diff --git a/Documentation/imports/infrastructure-slack.md b/Documentation/imports/infrastructure-slack.md
new file mode 100644
index 0000000..be8e423
--- /dev/null
+++ b/Documentation/imports/infrastructure-slack.md
@@ -0,0 +1,18 @@
+# Infrastructure: Slack
+
+
+
+## About
+
+## Usage
+
+* Communications between Members
+* Community
+
+## Information
+
+## Object Model
+
+This section describes the object model used in this App.
+
+See render here:
diff --git a/Documentation/imports/media-kit.md b/Documentation/imports/media-kit.md
new file mode 100644
index 0000000..61b3c7e
--- /dev/null
+++ b/Documentation/imports/media-kit.md
@@ -0,0 +1,470 @@
+# Media Kit
+
+
+
+## Table of Contents
+
+
+
+Expand / Collapse
+
+
+
+1. Introduction
+ * Definitions
+ * About this document
+ * Scope
+2. Concepts
+ * Name
+ * Mission & Vision
+ * Values
+ * The advocacy
+ * DCDR Principles
+ * TIOF Members
+3. Contents
+ * Descriptions
+ * Logos
+ * Fonts (Typeface)
+ * Color palette
+ * QR Codes
+ * \#Tags
+4. Official Channels
+ * Official Website
+ * Summary of links
+ * URL Shorteners
+ * Email
+ * Internal Communications
+ * Initiatives' Repositories
+ * Social Media
+ * Events
+ * Donations & Crowdfunding
+ * Human Resources
+5. TIOF Initiatives
+
+
+
+## Introduction
+
+### Definitions
+
+This document employs terms related to the [DCDR Advocacy](http://tiof.click/Advocacy) that can be found in the [TIOF terminology](http://tiof.click/Terminology).
+
+Back to top
+
+### About this document
+
+This document defines all the necessary elements that conform The IO Foundation's Project Identity (Branding Guidelines) and their usage rules on Media Channels, by either TIOF members or external parties. It is a reference document to which all TIOF productions, either for internal or external use, must refer and adhere. You should familiarize yourself with this it and comply with it at all times. Any questions you may have with regard to its contents or what you have to do to comply with it should be referred to the corresponding project's Team Comms.
+
+A document summarizing The IO Foundation's [Branding Guidelines](https://github.com/TheIOFoundation/TIOF/raw/master/Project%20Identity/\[TIOF]%20Comms%20\[P]%20Branding%20Guidelines%20ENG%20v1.4.pdf) is also available.
+
+This document does not form part of any Engagement Document and we may amend it at any time.
+
+Back to top
+
+### Scope
+
+This document directly applies to:
+
+* All \[TIOF Members] (https://github.com/TheIOFoundation/TIOF/wiki/Terminology#member)
+
+This document indirectly applies to:
+
+* All \[TIOF Contributors] (https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors) that may produce any type of content related to The IO Foundation.
+
+The policies and procedures set out in this document apply to all TIOF Members unless otherwise indicated. They therefore apply to anyone involved in the sharing of productions through any official channel, irrespective of their part-time, fixed-term or casual status.
+
+This document applies within all TIOF spaces, including (although not limited to) management activities, project contributions or events, and also applies when an individual is officially representing the broader community in public spaces. Examples of representing our community include (although not limited to) using an official e-mail address, posting via an official social media account or acting as an appointed representative at an event (online or offline).
+
+Back to top
+
+## Concepts
+
+### Name
+
+The following forms are authorized when referring to The IO Foundation:
+
+> Please note the capitalization
+
+* The IO Foundation
+* TIOF
+
+Back to top
+
+### Mission & Vision
+
+The following are the official formulations of The IO Foundation's Mission & Vision:
+
+> **Mission:** To promote, protect and provide solutions for Data-Centric Digital Rights.
+
+> **Vision:** A world where Human Rights and Digital Rights are one and the same.
+
+Back to top
+
+### Values
+
+The IO Foundation delivers its mission through the observance of the following values:
+
+> **Community:** Digital Rights is a global endeavor that requires the active participation of everyone, from policy makers to users, businesses and the people who will architect and build digital societies.
+
+> **Accountability:** We recognize the critical importance of operating under procedures and methodologies that are transparent in order to generate the necessary trust in our DCDR principles and the advocacy at large.
+
+> **Impact:** Our programs and projects are designed and implemented only to serve the broader advocacy and to help, step by step, generate practical outcomes that make technology better and safer transparently for digital citizens.
+
+Back to top
+
+### The advocacy
+
+The IO Foundation's advocacy is labelled as Data-Centric Digital Rights. The following forms are to be used internally in TIOF and highly encouraged when referring to the advocacy:
+
+> Please note the capitalization
+
+* Data-Centric Digital Rights
+* DCDR
+
+Data-Centric Digital Rights advocates to establish the necessary technical standards to transparently implement Digital Rights and enable technologists to create better and safer digital societies by embracing their role as Rights defenders.
+
+The IO Foundation focuses its efforts towards programmers and in the proclamation of a Universal Declaration of Digital Rights.
+
+Back to top
+
+#### Iconography
+
+While there is currently no agreed-upon iconography for the Data-Centric Digital Rights, The IO Foundation uses the following assets: **\[WIP]**
+
+Back to top
+
+### DCDR Principles
+
+The following are the official formulations of 3 Principles that The IO Foundation puts forward to guide technologist in their role as NextGen Rights defenders.
+
+> I Am My Data: _Treat their data as you'd want to be treated._
+>
+> 
+
+\
+\
+
+
+> End Remedy: _Adopt designs that minimize grievances._
+>
+> 
+
+\
+\
+
+
+> Rights By Design: _Leave no policy uncoded behind._
+>
+> 
+
+\
+\
+
+
+For more information on the DCDR Principles please visit the [DCDR Principles page](https://tiof.click/DCDRPrinciples).
+
+Back to top
+
+### TIOF Members
+
+The following is the official information about [the Humans](http://tiof.click/Profiles) composing The IO Foundation. For all other relevant information on this subject, please refer to the [Summary of Links](https://tiof.click/TIOFAboutUs).
+
+Back to top
+
+## Contents
+
+### Descriptions
+
+The following are the official definitions to be used when describing or referencing The IO Foundation and its advocacy. A number of variations are provided in an attempt to fit different character limitations.
+
+Back to top
+
+#### Full version
+
+The IO Foundation (TIOF) is a global for-impact NGO advocating for Data-Centric Digital Rights. Born from a fundamental concern about the state of Digital Rights in the world, its mission is to promote, _protect and provide solutions for Digital Rights_, thus aiming to bridge technological and humanitarian perspectives.
+
+As data becomes an increasingly powerful economic, political, and social force, _programmers are emerging as the next generation of Human and Digital Rights defenders_. There remains, however, a limited international understanding of the impact of technology on Human and Digital Rights.
+
+Following its vision of _a world where Human Rights and Digital Rights are one and the same_, TIOF aims to raise awareness of the importance of Data-Centric Digital Rights in collaboration with all stakeholders ranging from civil society, programmer communities, bodies of governance and corporate.
+
+Back to top
+
+#### Mini 1
+
+TIOF is a nonprofit advocating for Data-Centric Digital Rights (DCDR) aiming to ensure a more transparent and solid approach to Rights from a technical standards perspective.
+
+Back to top
+
+#### Mini 2
+
+The IO Foundation (TIOF) is a for-impact NGO advocating for Data-Centric Digital Rights to establish a more solid approach from a technical standards perspective and to raise awareness on the critical role of programmers as the next generation of Human and Digital Rights defenders.
+
+Back to top
+
+#### Mini 3
+
+The IO Foundation (TIOF) is a for-impact NGO advocating for Data-Centric Digital Rights (DCDR) to establish a more solid approach from a technical standards perspective and seek to prevent misuse of citizen's data in our digital societies.
+
+Back to top
+
+#### Mini 4
+
+The IO Foundation (TIOF) is a global nonprofit advocating for Data-Centric Digital Rights, born out of a fundamental concern on the future of digital communities, both in their governance and implementation, and the critical role of programmers as digital architects.
+
+Back to top
+
+#### X < 160 characters
+
+The IO Foundation (TIOF) is a for-impact NGO advocating for Data-Centric Digital Rights (DCDR) to establish a more solid approach from a technical standards perspective.
+
+Back to top
+
+#### Micro
+
+The IO Foundation is a nonprofit advocating for Data-Centric Digital Rights (DCDR).
+
+Back to top
+
+### Logos
+
+The following are the official logos of The IO Foundation:
+
+#### Category: Organization
+
+| **Name** | TIOF Full Logo | | | |
+| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Sample** |  |  |  |  |
+| **Format** | PNG | SVG | PNG | SVG |
+| **Code** | | | | |
+| **Features** | Hi Resolution / Full Color / Transparent Background / English | Hi Resolution / Full Color / Transparent Background / English | Hi Resolution / White / Transparent Background / English | Hi Resolution / White / Transparent Background / English |
+| **Usage** | | | | |
+
+| **Name** | TIOF Hex Logo | | | |
+| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| **Sample** |  |  |  |  |
+| **Format** | PNG | SVG | PNG | SVG |
+| **Code** | | | | |
+| **Features** | Hi Resolution / Full Color / Transparent Background / English | Hi Resolution / Full Color / Transparent Background / English | Hi Resolution / White / Transparent Background / English | Hi Resolution / White / Transparent Background / English |
+| **Usage** | | | | |
+
+For more information, please refer to [TIOF's Branding Guidelines](https://tiof.click/BrandingKit).
+
+Back to top
+
+### Fonts (typeface)
+
+The official font for The IO Foundation content is Montserrat.
+
+Note: Only in the event that the official font is not available (and only if), the following fonts can be used as backup:
+
+* Helvetica
+* Arial
+
+For more information, please refer to [TIOF's Branding Guidelines](https://tiof.click/BrandingKit).
+
+Back to top
+
+### Color palette
+
+The following are the official colors composing The IO Foundation's color palette:
+
+| **Color** | **Light gray** | **Dark gray** | **Light blue** | **Dark blue** | **Orange** |
+| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Code** | LG | DG | LB | DB | O |
+| **Sample** |  |  |  |  |  |
+| **R** | 137 | 78 | 102 | 80 | 247 |
+| **G** | 137 | 80 | 181 | 145 | 149 |
+| **B** | 142 | 86 | 197 | 158 | 82 |
+| **H** | 240 | 225 | 190 | 190 | 24 |
+| **S** | 2.2 | 4.9 | 45.0 | 32.8 | 91.2 |
+| **L** | 54.7 | 32.2 | 58.6 | 46.7 | 64.5 |
+| **Hex** | #89898E | #4E5056 | #66B5C5 | #50919F | #F79552 |
+
+**Note:** Due to Google Calendar limitations, the [\[TIOF\] Public Calendar](https://tiof.click/EventsCal) uses their _Graphite_ color coding.
+
+For more information, please refer to [TIOF's Branding Guidelines](https://tiof.click/BrandingKit).
+
+Back to top
+
+### QR Codes
+
+The following are the official QR Codes to link The IO Foundation's online resources:
+
+**\[WTI]**
+
+To generate any new QR Codes, please refer to the [QR Codes Reference](https://github.com/TheIOFoundation/TIOF/wiki/Project-Identity#qr-codes)
+
+Back to top
+
+### Tags
+
+The following are the official #Tags used by The IO Foundation in all of its Media Channels (as well as internally):
+
+* \#TIOF
+* \#TheIOFoundation
+* \#DCDR
+* \#DigitalHarms
+* \#DigitalRights
+* \#IamMyData
+* \#EndRemedy
+* \#RightsByDesign
+* \#RightsTech
+
+Note: Each TIOF initiative has its own set of #Tags. Please refer to the corresponding initiative's Media Kit for their #Tags list.
+
+Back to top
+
+## Official Channels
+
+The following are the official, sanctioned, Media Channels for The IO Foundation. Any other Media Channel not listed here is to be considered not affiliated with TIOF and any opinions expressed are not to be associated with TIOF.
+
+### Official Website
+
+The following is the official website for The IO Foundation:
+
+| **URL** | [https://TheIOFoundation.org](https://theiofoundation.org) |
+| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Alternative URLs** | [.com](https://theiofoundation.com) [.net](https://theiofoundation.net) [.eu](https://theiofoundation.eu) [.asia](https://theiofoundation.asia) |
+| **Short URL** | https://TIOF.Click/TIOFWeb |
+| **Status** | Active - Planning for a major overhaul |
+| **Contents** | Publishing of general information about TIOF and its advocacy + Initiatives Presentation + Publications + Events |
+| **Usage** | Primary reference to The IO Foundation |
+
+Back to top
+
+### Summary of links
+
+The following is the official summary of links page:
+
+| **URL** | [https://TIOF.Click/TIOFAboutUs](https://tiof.click/TIOFAboutUs) |
+| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Alternative URLs** | None |
+| **Full URL** | [https://theiofoundation.start.me/aboutus](https://theiofoundation.start.me/aboutus) |
+| **Status** | Active |
+| **Contents** | Collection of principal links of information about The IO Foundation such as advocacy, events, Media Kit, Media Channels and others. |
+| **Usage** | Provide quick access to condensed information in scenarios where quick access to information is relevant. Example: Media quick introduction, Event booths |
+
+Back to top
+
+### URL Shorteners
+
+The following are the official URL shortener domains used by The IO Foundation:
+
+| **URL** | [http://TIOF.Click](http://tiof.click) | [http://DoThe.Click](http://dothe.click) |
+| -------------------- | ------------------------------------------------ | -------------------------------------------------------------------------- |
+| **Alternative URLs** | None | None |
+| **Short URL** | None | None |
+| **Full URL** | None | None |
+| **Status** | Active | Active |
+| **Usage** | Shorten URLs related to TIOF and its initiatives | Shorten URLs related to other organizations or projects that TIOF supports |
+
+Back to top
+
+### Email
+
+The following are the official email domains used by The IO Foundation: Note: Only email received from these domains are to be considered originated by TIOF or its members.
+
+| **Domains** | @TheIOFoundation.org |
+| ----------------------- | ------------------------------------------------------------------------ |
+| **Alternative Domains** | None |
+| **Status** | Active |
+| **Usage** | Official communications from TIOF members both internally and externally |
+
+The following are the official public email domains used by The IO Foundation:
+
+| **Email** | [Contact@TheIOFoundation.org](mailto://Contact@TheIOFoundation.org) | [Media@TheIOFoundation.org](mailto://Media@TheIOFoundation.org) |
+| ---------- | ------------------------------------------------------------------- | --------------------------------------------------------------- |
+| **Status** | Active | Active |
+| **Usage** | Official communications and inquiries | Media related communications and inquiries |
+
+Back to top
+
+### Internal Communications
+
+WIP
+
+* Email
+* Slack
+
+Back to top
+
+### Initiatives' Repositories
+
+The following are the official initiative's repositories used by The IO Foundation:
+
+| **Type** | [TIOF Profile on GH](http://tiof.click/TIOFGitHub) | [TIOF Repository on GH](http://tiof.click/TIOFRepo) |
+| -------------------- | -------------------------------------------------- | ----------------------------------------------------------------------- |
+| **Alternative URLs** | None | None |
+| **Short URL** | http://TIOF.Click/TIOFGitHub | http://TIOF.Click/TIOFRepo |
+| **Full URL** | https://github.com/TheIOFoundation/ | https://github.com/TheIOFoundation/TIOF |
+| **Status** | Active | WIP |
+| **Content** | Official profile of TIOF in GitHub | Public repository showcasing TIOF's advocacy work |
+| **Usage** | Consolidation of all GH presence for TIOF | Initiative Management + Community Collaboration + Transparency platform |
+
+Back to top
+
+### Social Media
+
+The following are the official social media platforms where The IO Foundation has some sort of presence. For a full list of all social media (and other platforms) where The IO Foundation has presence, please refer to the [Summary of Links](https://tiof.click/TIOFAboutUs).
+
+> Note: For more information on TIOF's position respective to mainstream social media, please consult our [Media Policy](https://github.com/TheIOFoundation/TIOF/wiki/Media-Policy#about-social-media).
+
+| **Platform** | LinkedIn | Twitter | Facebook | Instagram |
+| ------------- | -------------------------------------------------- | ------------------------------------------------------ | ----------------------------------- | ----------------------------------------- |
+| **Short URL** | http://TIOF.Click/TIOFLinkedIn | https://TIOF.Click/TIOFTwitter | http://tiof.click/TIOFFacebook | http://tiof.click/TIOFInstagram |
+| **Full URL** | https://www.linkedin.com/company/the-io-foundation | https://github.com/TheIOFoundation/TIOF | https://twitter.com/TheIOFoundation | https://www.facebook.com/TheI0Foundation/ |
+| **Status** | Active | Active | Dormant | Dormant |
+| **Content** | Updates on Advocacy + Events | PUpdates on Advocacy + Events / Comments not responded | None | None |
+| **Usage** | Postings - Comments not responded | Postings - Comments not responded | Impersonation protection | Impersonation protection |
+
+Back to top
+
+### Events
+
+The following are the official links through which The IO Foundation manages events (organized by TIOF + those it may participate in + recommended):
+
+| **Platform** | Events | Public Calendar | Live Events | Events RSVP |
+| ------------- | --------------------------------------------------------- | ---------------------------------------- | ----------------------------------- | ----------------------------- |
+| **Short URL** | http://TIOF.Click/Events | http://TIOF.Click/EventsCal | https://TIOF.Click/EventsLive | https://TIOF.Click/EventsRSVP |
+| **Status** | Active | Active | Active | Active |
+| **Content** | Events listing | Events calendar | Events access | TIOF Events RSVP |
+| **Usage** | Communicate events from TIOF and those it participates in | Public events calendar that can be added | Access to the current running event | RSVP for TIOF events |
+
+Back to top
+
+### Donations & Crowdfunding
+
+The following are some of the platforms where The IO Foundation has official presence. A selected list of Goals is made available to invite the broader community to participate and support. For more information, explore TIOF's [CrowdShape](https://github.com/TheIOFoundation/CrowdShape) initiative. \[WIP]
+
+For a full list of all crowdfunding platforms where The IO Foundation has presence, please refer to the [Summary of Links](https://tiof.click/TIOFAboutUs).
+
+Currently, The IO Foundation accepts financial donations on both Fiat and Cryptocurrencies.
+
+| **Platform** | TIOF Donation Page | GitHub Sponsors | Open Collective | Patreon |
+| ------------- | ----------------------------------- | --------------------------------------- | ------------------------------------------ | --------------------------------------- |
+| **Short URL** | https://TIOF.Click/Donate | http://TIOF.Click/TIOFGHSponsors | http://TIOF.Click/TIOFOpenCollective | http://TIOF.Click/TIOFPatreon |
+| **Full URL** | https://TheIOFoundation.org/Donate/ | https://GitHub.com/TheIOFoundation/TIOF | https://OpenCollective.com/TheIOFoundation | https://www.Patreon.com/TheIOFoundation |
+| **Status** | Active | Active | WIP | WIP |
+| **Content** | General Donations | Goals | Goals | Goals |
+| **Usage** | Facilitate donations to TIOF global | List Goals for support | List Goals for support | List Goals for support |
+
+Back to top
+
+### Human Resources
+
+WIP
+
+Back to top
+
+## TIOF Initiatives
+
+The following is a list of TIOF's initiatives and a quick link to their corresponding Media Kit.
+
+| UDDR | TechUp | Project Lockdown | BHR in Tech |
+| --------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|  |  |  |  |
+| [Media Kit](https://github.com/TheIOFoundation/UDDR/wiki/Media-Kit) | [Media Kit](https://github.com/TheIOFoundation/TechUp/wiki/Media-Kit) | [Media Kit](https://github.com/TheIOFoundation/ProjectLockdown/wiki/Media-Kit) | [Media Kit](https://github.com/TheIOFoundation/BiT/wiki/Media-Kit) |
+
+Back to top
+
+***
diff --git a/Documentation/group-1/page-1.md b/Documentation/imports/page-1.md
similarity index 100%
rename from Documentation/group-1/page-1.md
rename to Documentation/imports/page-1.md
diff --git a/Documentation/handbooks/page-5.md b/Documentation/imports/page-5.md
similarity index 100%
rename from Documentation/handbooks/page-5.md
rename to Documentation/imports/page-5.md
diff --git a/Documentation/imports/policies.md b/Documentation/imports/policies.md
new file mode 100644
index 0000000..8058247
--- /dev/null
+++ b/Documentation/imports/policies.md
@@ -0,0 +1,5 @@
+# Policies
+
+
+
+## Summary of Policies
diff --git a/Documentation/imports/policy-children-protection.md b/Documentation/imports/policy-children-protection.md
new file mode 100644
index 0000000..d3801ec
--- /dev/null
+++ b/Documentation/imports/policy-children-protection.md
@@ -0,0 +1,4 @@
+# Policy: Children Protection
+
+\
+
diff --git a/Documentation/imports/policy-data-and-privacy.md b/Documentation/imports/policy-data-and-privacy.md
new file mode 100644
index 0000000..cd0fa58
--- /dev/null
+++ b/Documentation/imports/policy-data-and-privacy.md
@@ -0,0 +1,77 @@
+# Policy: Data & Privacy
+
+
+
+## Table of Contents
+
+
+
+Expand / Collapse
+
+
+
+1. Introduction
+ * Definitions
+ * About this document
+ * Scope
+2. Policy details
+ * What is bribery?
+ * Gifts and hospitality
+ * Record keeping
+ * How to raise a concern
+ * Conduct outside of Work
+
+
+
+## Introduction
+
+### Definitions
+
+This document employs terms related to the [DCDR Advocacy](http://tiof.click/Advocacy) that can be found in the [TIOF terminology](http://tiof.click/Terminology).
+
+For a structure of The IO Foundation, please visit
+
+* The IO Foundation's [Organizational Chart](http://tiof.click/TIOFOrgChart)
+* The IO Foundation's [Organizational Nomenclature](http://tiof.click/OrgNomenclature)
+
+Back to top
+
+### About this document
+
+This document sets out the position maintained by TIOF in matters of Anti-corruption and Anti-bribery that you will need to be aware of while being a Member for TIOF. You should familiarize yourself with it and comply with it at all times. Any questions you may have with regard to its contents or what you have to do to comply with it should be referred to your corresponding Team Human Resources Coordinator.
+
+The IO Foundation is committed to conducting its advocacy and all of its business in an honest and ethical manner. We take a zero-tolerance approach to bribery and corruption and are committed to acting professionally, fairly, with integrity and under the observance of the law in all our operations, business dealings and relationships.
+
+Any Member who breaches this Policy will face disciplinary action, which could result in dismissal for gross misconduct. Any non-employee who breaches this Policy may have their contract (or equivalent official relationship with TIOF) terminated with immediate effect.
+
+This document complements TIOF's [Code of Conduct](http://tiof.click/TIOFPolicyCoC)
+
+This document does not form part of any [Engagement Document](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#engagement-document) and we may amend it at any time.
+
+Back to top
+
+### Scope
+
+This document directly applies to:
+
+* All [TIOF Members](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#member)
+
+This document indirectly applies to:
+
+* All [TIOF Contributors](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors)
+
+The policies and/or procedures set out in this document apply to all TIOF Members unless otherwise indicated. They therefore apply to Directors, Advisers, Counselors, Staff, Volunteers and Interns; this is irrespective of their part-time, fixed-term or casual status. They equally apply to all [Contributors](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors) and will be used as part of the selection criteria when engaging with them.
+
+This document applies within all TIOF spaces, including (although not limited to) management activities, project contributions or events, and also applies when an individual is officially representing the broader community in public spaces. Examples of representing our community include (although not limited to) using an official e-mail address, posting via an official social media account or acting as an appointed representative at an event (online or offline).
+
+Back to top
+
+## Policy details
+
+### Data & Privacy statement
+
+##
+
+### Cookies Policy
+
+Back to top
diff --git a/Documentation/imports/policy-data-protection.md b/Documentation/imports/policy-data-protection.md
new file mode 100644
index 0000000..aa5f54e
--- /dev/null
+++ b/Documentation/imports/policy-data-protection.md
@@ -0,0 +1,112 @@
+# Policy: Data Protection
+
+
+
+## Table of Contents
+
+
+
+Expand / Collapse
+
+
+
+1. Introduction
+ * Definitions
+ * About this document
+ * Scope
+2. Policy details
+ * What is bribery?
+ * Gifts and hospitality
+ * Record keeping
+ * How to raise a concern
+ * Conduct outside of Work
+
+
+
+## Introduction
+
+### Definitions
+
+This document employs terms related to the [DCDR Advocacy](http://tiof.click/Advocacy) that can be found in the [TIOF terminology](http://tiof.click/Terminology).
+
+For a structure of The IO Foundation, please visit
+
+* The IO Foundation's [Organizational Chart](http://tiof.click/TIOFOrgChart)
+* The IO Foundation's [Organizational Nomenclature](http://tiof.click/OrgNomenclature)
+
+Back to top
+
+### About this document
+
+This document sets out the position maintained by TIOF in matters of Anti-corruption and Anti-bribery that you will need to be aware of while being a Member for TIOF. You should familiarize yourself with it and comply with it at all times. Any questions you may have with regard to its contents or what you have to do to comply with it should be referred to your corresponding Team Human Resources Coordinator.
+
+The IO Foundation is committed to conducting its advocacy and all of its business in an honest and ethical manner. We take a zero-tolerance approach to bribery and corruption and are committed to acting professionally, fairly, with integrity and under the observance of the law in all our operations, business dealings and relationships.
+
+Any Member who breaches this Policy will face disciplinary action, which could result in dismissal for gross misconduct. Any non-employee who breaches this Policy may have their contract (or equivalent official relationship with TIOF) terminated with immediate effect.
+
+This document complements TIOF's [Code of Conduct](http://tiof.click/TIOFPolicyCoC)
+
+This document does not form part of any [Engagement Document](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#engagement-document) and we may amend it at any time.
+
+Back to top
+
+### Scope
+
+This document directly applies to:
+
+* All [TIOF Members](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#member)
+
+This document indirectly applies to:
+
+* All [TIOF Contributors](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors)
+
+The policies and/or procedures set out in this document apply to all TIOF Members unless otherwise indicated. They therefore apply to Directors, Advisers, Counselors, Staff, Volunteers and Interns; this is irrespective of their part-time, fixed-term or casual status. They equally apply to all [Contributors](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors) and will be used as part of the selection criteria when engaging with them.
+
+This document applies within all TIOF spaces, including (although not limited to) management activities, project contributions or events, and also applies when an individual is officially representing the broader community in public spaces. Examples of representing our community include (although not limited to) using an official e-mail address, posting via an official social media account or acting as an appointed representative at an event (online or offline).
+
+Back to top
+
+## Policy details
+
+### Data Protection statement
+
+## WARNING: OC comment: A copy of this policy should be extracted and provided to your volunteers to sign.
+
+## Data Protection Policy
+
+### Definitions
+
+This document employs terms related to the [DCDR Advocacy](http://tiof.click/Advocacy) that can be found in the [TIOF terminology](http://tiof.click/Terminology).
+
+For a structure of The IO Foundation, please visit
+
+* The IO Foundation's [Organizational Chart](http://tiof.click/TIOFOrgChart)
+* The IO Foundation's [Organizational Nomenclature](http://tiof.click/OrgNomenclature)
+
+### About this Policy
+
+The IO Foundation's IT and communications systems are intended to promote effective communication, working practices and an effective way to advance its advocacy.
+
+This Policy outlines the standards you must observe when using these systems, when we will monitor their use, and the action we will take if you breach these standards that you will need to be aware of while being a Member for TIOF. You should familiarize yourself with it and comply with it at all times. Any breach of this Policy may be dealt with under our [Disciplinary Procedures](http://tiof.click/ProcedureDisciplinary) and, in serious cases, may be treated as gross misconduct leading to summary dismissal. Any questions you may have with regard to its contents or what you have to do to comply with it should be referred to your corresponding Team HR Coordinator.
+
+This Policy complements TIOF's [Code of Conduct](http://tiof.click/TIOFPolicyCoC)
+
+This Policy does not form part of any Engagement Document and we may amend it at any time.
+
+### Scope
+
+This document directly applies to:
+
+* All \[TIOF Members] (https://github.com/TheIOFoundation/TIOF/wiki/Terminology#member)
+
+This document does not apply to:
+
+* All \[TIOF Contributors] (https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors)
+
+The policies and procedures set out in this document apply to all TIOF Members unless otherwise indicated. They therefore apply to Directors, Advisers, Counselors, Staff, Volunteers and Interns; this is irrespective of their part-time, fixed-term or casual status. They equally apply to all [Contributors](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors) and will be used as part of the selection criteria when engaging with them.
+
+This document applies within all TIOF spaces, including (although not limited to) management activities, project contributions or events, and also applies when an individual is officially representing the broader community in public spaces. Examples of representing our community include (although not limited to) using an official e-mail address, posting via an official social media account or acting as an appointed representative at an event (online or offline).
+
+***
+
+Interpretation Automated Decision-Making (ADM): when a decision is made which is based solely on Automated Processing (including profiling) which produces legal effects or significantly affects an individual. The UK GDPR prohibits Automated Decision-Making (unless certain conditions are met) but not Automated Processing. Automated Processing: any form of automated processing of Personal Data consisting of the use of Personal Data to evaluate certain personal aspects relating to an individual, in particular to analyse or predict aspects concerning that individual's performance at work, economic situation, health, personal preferences, interests, reliability, behaviour, location or movements. Profiling is an example of Automated Processing. Company name: The IO Foundation MTU. Company Personnel: all employees, workers contractors, agency workers, consultants, directors, volunteers and others. Consent: agreement which must be freely given, specific, informed and be an unambiguous indication of the Data Subject's wishes by which they, by a statement or by a clear positive action, signify agreement to the Processing of Personal Data relating to them. Controller: the person or organisation that determines when, why and how to process Personal Data. It is responsible for establishing practices and policies in line with the UK GDPR. We are the Controller of all Personal Data relating to our Company Personnel and Personal Data used in our business for our own commercial purposes. Criminal Convictions Data: means personal data relating to criminal convictions and offences and includes personal data relating to criminal allegations and proceedings. Data Subject: a living, identified or identifiable individual about whom we hold Personal Data. Data Subjects may be nationals or residents of any country and may have legal rights regarding their Personal Data. Data Privacy Impact Assessment (DPIA): tools and assessments used to identify and reduce risks of a data processing activity. DPIA can be carried out as part of Privacy by Design and should be conducted for all major system or business change programmes involving the Processing of Personal Data. Data Protection Officer (DPO): the person required to be appointed in specific circumstances under the UK GDPR. Where a mandatory DPO has not been appointed, this term means a data protection manager or other voluntary appointment of a DPO or refers to the Company data privacy team with responsibility for data protection compliance. EEA: the 28 countries in the EU, and Iceland, Liechtenstein and Norway. Explicit Consent: consent which requires a very clear and specific statement (that is, not just action). UK General Data Protection Regulation (GDPR): the General Data Protection Regulation ((EU) 2016/679) as it forms part of the law of England and Wales by virtue of section 3 of the European Union (Withdrawal) Act 2018. Personal Data is subject to the legal safeguards specified in the UK GDPR. Personal Data: any information identifying a Data Subject or information relating to a Data Subject that we can identify (directly or indirectly) from that data alone or in combination with other identifiers we possess or can reasonably access. Personal Data includes Special Categories of Personal Data and Pseudonymised Personal Data but excludes anonymous data or data that has had the identity of an individual permanently removed. Personal data can be factual (for example, a name, email address, location or date of birth) or an opinion about that person's actions or behaviour. Personal Data Breach: any act or omission that compromises the security, confidentiality, integrity or availability of Personal Data or the physical, technical, administrative or organisational safeguards that we or our third-party service providers put in place to protect it. The loss, or unauthorised access, disclosure or acquisition, of Personal Data is a Personal Data Breach. Privacy by Design: implementing appropriate technical and organisational measures in an effective manner to ensure compliance with the UK GDPR. Privacy Notices (also referred to as Fair Processing Notices) or Privacy Policies: separate notices setting out information that may be provided to Data Subjects when the Company collects information about them. These notices may take the form of general privacy statements applicable to a specific group of individuals (for example, employee privacy notices or the website privacy policy) or they may be stand-alone, one-time privacy statements covering Processing related to a specific purpose. Processing or Process: any activity that involves the use of Personal Data. It includes obtaining, recording or holding the data, or carrying out any operation or set of operations on the data including organising, amending, retrieving, using, disclosing, erasing or destroying it. Processing also includes transmitting or transferring Personal Data to third parties. Pseudonymisation or Pseudonymised: replacing information that directly or indirectly identifies an individual with one or more artificial identifiers or pseudonyms so that the person, to whom the data relates, cannot be identified without the use of additional information which is meant to be kept separately and secure. Special Categories of Personal Data: information revealing racial or ethnic origin, political opinions, religious or similar beliefs, trade union membership, physical or mental health conditions, sexual life, sexual orientation, biometric or genetic data, and Personal Data. INTRODUCTION The Data Protection Policy sets out how The IO Foundation MTU ("we", "our", "us", "the Company") handle the Personal Data of our customers, suppliers, employees, workers and other third parties. This Data Protection Policy applies to all Personal Data we Process regardless of the media on which that data is stored or whether it relates to past or present employees, workers, customers, clients or supplier contacts, website users or any other Data Subject. This Data Protection Policy applies to all Company Personnel ("you", "your"). You must read, understand and comply with this Data Protection Policy when Processing Personal Data on our behalf and attend training on its requirements. This Data Protection Policy sets out what we expect from you for the Company to comply with applicable law. Your compliance with this Data Protection Policy is mandatory. Any breach of this Data Protection Policy may result in disciplinary action. This Data Protection Policy is an internal document and cannot be shared with third parties, clients or regulators without prior authorisation from the DPO. Scope We recognise that the correct and lawful treatment of Personal Data will maintain confidence in the organisation and will provide for successful business operations. Protecting the confidentiality and integrity of Personal Data is a critical responsibility that we take seriously at all times. The Company is exposed to potential fines of up to EUR20 million or 4% of total worldwide annual turnover, whichever is higher and depending on the breach, for failure to comply with the provisions of the UK GDPR. All departments are responsible for ensuring all Company Personnel comply with this Data Protection Policy and need to implement appropriate practices, processes, controls and training to ensure that compliance. The DPO is responsible for overseeing this Data Protection Policy. That post is held by \[insert name]. Please contact the DPO with any questions about the operation of this Data Protection Policy or the UK GDPR or if you have any concerns that this Data Protection Policy is not being or has not been followed. In particular, you must always contact the DPO in the following circumstances: if you are unsure of the lawful basis which you are relying on to process Personal Data (including the legitimate interests used by the Company) (see paragraph 5.1); if you need to rely on Consent and/or need to capture Explicit Consent (see paragraph 6); if you need to draft Privacy Notices (see paragraph 7); if you are unsure about the retention period for the Personal Data being Processed (see paragraph 11); if you are unsure about what security or other measures you need to implement to protect Personal Data (see paragraph 12.1); if there has been a Personal Data Breach (see paragraph 13); if you are unsure on what basis to transfer Personal Data outside the EEA (see paragraph 14); if you need any assistance dealing with any rights invoked by a Data Subject (see paragraph 15); whenever you are engaging in a significant new, or change in, Processing activity which is likely to require a DPIA (see paragraph 19) or plan to use Personal Data for purposes other than what it was collected for; if you plan to undertake any activities involving Automated Processing including profiling or Automated Decision-Making (see paragraph 20); if you need help complying with applicable law when carrying out direct marketing activities (see paragraph 21); or if you need help with any contracts or other areas in relation to sharing Personal Data with third parties (including our vendors) (see paragraph 22). Personal data protection principles We adhere to the principles relating to Processing of Personal Data set out in the UK GDPR which require Personal Data to be: processed lawfully, fairly and in a transparent manner (Lawfulness, Fairness and Transparency); collected only for specified, explicit and legitimate purposes (Purpose Limitation); adequate, relevant and limited to what is necessary in relation to the purposes for which it is Processed (Data Minimisation); accurate and where necessary kept up to date (Accuracy); not kept in a form which permits identification of Data Subjects for longer than is necessary for the purposes for which the data is Processed (Storage Limitation); processed in a manner that ensures its security using appropriate technical and organisational measures to protect against unauthorised or unlawful Processing and against accidental loss, destruction or damage (Security, Integrity and Confidentiality); not transferred to another country without appropriate safeguards being in place (Transfer Limitation); and made available to Data Subjects and allow Data Subjects to exercise certain rights in relation to their Personal Data (Data Subject's Rights and Requests). We are responsible for and must be able to demonstrate compliance with the data protection principles listed above (Accountability). Lawfulness, fairness, transparency Personal data must be Processed lawfully, fairly and in a transparent manner in relation to the Data Subject. You may only collect, Process and share Personal Data fairly and lawfully and for specified purposes. The UK GDPR restricts our actions regarding Personal Data to specified lawful purposes. These restrictions are not intended to prevent Processing, but ensure that we Process Personal Data fairly and without adversely affecting the Data Subject. The UK GDPR allows Processing for specific purposes, some of which are set out below: the Data Subject has given his or her Consent; the Processing is necessary for the performance of a contract with the Data Subject; to meet our legal compliance obligations; to protect the Data Subject's vital interests; to pursue our legitimate interests for purposes where they are not overridden because the Processing prejudices the interests or fundamental rights and freedoms of Data Subjects. The purposes for which we process Personal Data for legitimate interests need to be set out in applicable Privacy Notices; or \[insert other UK GDPR processing grounds]. You must identify and document the legal ground being relied on for each Processing activity in accordance with any Company guidelines on Lawful Basis for Processing Personal Data, in force from time to time. Consent A Controller must only process Personal Data on the basis of one or more of the lawful bases set out in the UK GDPR, which include Consent. A Data Subject consents to Processing of their Personal Data if they indicate agreement clearly either by a statement or positive action to the Processing. Consent requires affirmative action so silence, pre-ticked boxes or inactivity are unlikely to be sufficient. If Consent is given in a document which deals with other matters, then the Consent must be kept separate from those other matters. Data Subjects must be easily able to withdraw Consent to Processing at any time and withdrawal must be promptly honoured. Consent may need to be refreshed if you intend to Process Personal Data for a different and incompatible purpose which was not disclosed when the Data Subject first consented. When processing Special Category Data or Criminal Convictions Data, we will usually rely on a legal basis for processing other than Explicit Consent or Consent if possible. Where Explicit Consent is relied on, you must issue a Privacy Notice to the Data Subject to capture Explicit Consent. You will need to evidence Consent captured and keep records of all Consents so that the Company can demonstrate compliance with Consent requirements. Transparency (notifying Data Subjects) The UK GDPR requires Data Controllers to provide detailed, specific information to Data Subjects depending on whether the information was collected directly from Data Subjects or from elsewhere. The information must be provided through appropriate Privacy Notices which must be concise, transparent, intelligible, easily accessible, and in clear and plain language so that a Data Subject can easily understand them. Whenever we collect Personal Data directly from Data Subjects, including for human resources or employment purposes, we must provide the Data Subject with all the information required by the UK GDPR including the identity of the Controller and DPO, how and why we will use, Process, disclose, protect and retain that Personal Data through a Privacy Notice which must be presented when the Data Subject first provides the Personal Data. When Personal Data is collected indirectly (for example, from a third party or publicly available source), we must provide the Data Subject with all the information required by the UK GDPR as soon as possible after collecting or receiving the data. We must also check that the Personal Data was collected by the third party in accordance with the UK GDPR and on a basis which contemplates our proposed Processing of that Personal Data. If you are collecting Personal Data from Data Subjects, directly or indirectly, then you must provide Data Subjects with a Privacy Notice. You must comply with any Company guidelines on drafting Privacy Notices, in force from time to time. Purpose limitation Personal Data must be collected only for specified, explicit and legitimate purposes. It must not be further Processed in any manner incompatible with those purposes. You cannot use Personal Data for new, different or incompatible purposes from that disclosed when it was first obtained unless you have informed the Data Subject of the new purposes and they have provided Consent where necessary. Data minimisation Personal Data must be adequate, relevant and limited to what is necessary in relation to the purposes for which it is Processed. You may only Process Personal Data when performing your job duties requires it. You cannot Process Personal Data for any reason unrelated to your job duties. You may only collect Personal Data that you require for your job duties: do not collect excessive data. Ensure any Personal Data collected is adequate and relevant for the intended purposes. You must ensure that when Personal Data is no longer needed for specified purposes, it is deleted or anonymised in accordance with the Company's data retention guidelines. Accuracy Personal Data must be accurate and, where necessary, kept up to date. It must be corrected or deleted without delay when inaccurate. You will ensure that the Personal Data we use and hold is accurate, complete, kept up to date and relevant to the purpose for which we collected it. You must check the accuracy of any Personal Data at the point of collection and at regular intervals afterwards. You must take all reasonable steps to destroy or amend inaccurate or out-of-date Personal Data. Storage limitation Personal Data must not be kept in an identifiable form for longer than is necessary for the purposes for which the data is processed. The Company will maintain retention policies and procedures to ensure Personal Data is deleted after a reasonable time for the purposes for which it was being held, unless a law requires that data to be kept for a minimum time. You must comply with any Company guidelines on data retention in force from time to time. You must not keep Personal Data in a form which permits the identification of the Data Subject for longer than needed for the legitimate business purpose or purposes for which we originally collected it including for the purpose of satisfying any legal, accounting or reporting requirements. You will take all reasonable steps to destroy or erase from our systems all Personal Data that we no longer require in accordance with all the Company's applicable records retention schedules and policies. This includes requiring third parties to delete that data where applicable. You will ensure Data Subjects are informed of the period for which data is stored and how that period is determined in any applicable Privacy Notice. Security integrity and confidentiality Personal Data must be secured by appropriate technical and organisational measures against unauthorised or unlawful Processing, and against accidental loss, destruction or damage. We will develop, implement and maintain safeguards appropriate to our size, scope and business, our available resources, the amount of Personal Data that we own or maintain on behalf of others and identified risks (including use of encryption and Pseudonymisation where applicable). We will regularly evaluate and test the effectiveness of those safeguards to ensure security of our Processing of Personal Data. You are responsible for protecting the Personal Data we hold. You must implement reasonable and appropriate security measures against unlawful or unauthorised Processing of Personal Data and against the accidental loss of, or damage to, Personal Data. You must exercise particular care in protecting Special Categories of Personal Data and Criminal Convictions Data from loss and unauthorised access, use or disclosure. You must follow all procedures and technologies we put in place to maintain the security of all Personal Data from the point of collection to the point of destruction. You may only transfer Personal Data to third-party service providers who agree to comply with the required policies and procedures and who agree to put adequate measures in place, as requested. You must maintain data security by protecting the confidentiality, integrity and availability of the Personal Data, defined as follows: Confidentiality means that only people who have a need to know and are authorised to use the Personal Data can access it; Integrity means that Personal Data is accurate and suitable for the purpose for which it is processed; and Availability means that authorised users are able to access the Personal Data when they need it for authorised purposes. You must comply with and not attempt to circumvent the administrative, physical and technical safeguards we implement and maintain in accordance with the UK GDPR and relevant standards to protect Personal Data. Reporting a Personal Data Breach The UK GDPR requires Controllers to notify any Personal Data Breach to the applicable regulator and, in certain instances, the Data Subject. We have put in place procedures to deal with any suspected Personal Data Breach and will notify Data Subjects or any applicable regulator where we are legally required to do so. If you know or suspect that a Personal Data Breach has occurred, do not attempt to investigate the matter yourself. Immediately contact the DPO. You should preserve all evidence relating to the potential Personal Data Breach. Transfer limitation The UK GDPR restricts data transfers to countries outside the EEA to ensure that the level of data protection afforded to individuals by the UK GDPR is not undermined. You transfer Personal Data originating in one country across borders when you transmit, send, view or access that data in or to a different country. You may only transfer Personal Data outside the EEA if one of the following conditions applies: the European Commission has issued a decision confirming that the country to which we transfer the Personal Data ensures an adequate level of protection for the Data Subject's rights and freedoms; appropriate safeguards are in place such as binding corporate rules (BCR), standard contractual clauses approved by the European Commission, an approved code of conduct or a certification mechanism, a copy of which can be obtained from the DPO; the Data Subject has provided Explicit Consent to the proposed transfer after being informed of any potential risks; or the transfer is necessary for one of the other reasons set out in the UK GDPR including the performance of a contract between us and the Data Subject, reasons of public interest, to establish, exercise or defend legal claims or to protect the vital interests of the Data Subject where the Data Subject is physically or legally incapable of giving Consent and, in some limited cases, for our legitimate interest. You must comply with any Company guidelines on cross-border data transfers in force from time to time. Data Subject's rights and requests Data Subjects have rights when it comes to how we handle their Personal Data. These include rights to: withdraw Consent to Processing at any time; receive certain information about the Data Controller's Processing activities; request access to their Personal Data that we hold; prevent our use of their Personal Data for direct marketing purposes; ask us to erase Personal Data if it is no longer necessary in relation to the purposes for which it was collected or Processed or to rectify inaccurate data or to complete incomplete data; restrict Processing in specific circumstances; challenge Processing which has been justified on the basis of our legitimate interests or in the public interest; request a copy of an agreement under which Personal Data is transferred outside of the EEA; object to decisions based solely on Automated Processing, including profiling (ADM); prevent Processing that is likely to cause damage or distress to the Data Subject or anyone else; be notified of a Personal Data Breach which is likely to result in high risk to their rights and freedoms; make a complaint to the supervisory authority; and in limited circumstances, receive or ask for their Personal Data to be transferred to a third party in a structured, commonly used and machine-readable format. You must verify the identity of an individual requesting data under any of the rights listed above (do not allow third parties to persuade you into disclosing Personal Data without proper authorisation). You must immediately forward any Data Subject request you receive to DPO and comply with any Company Data Subject response process in force from time to time. Accountability The Controller must implement appropriate technical and organisational measures in an effective manner, to ensure compliance with data protection principles. The Controller is responsible for, and must be able to demonstrate, compliance with the data protection principles. The Company must have adequate resources and controls in place to ensure and to document UK GDPR compliance including: appointing a suitably qualified DPO (where necessary) and an executive accountable for data privacy; implementing Privacy by Design when Processing Personal Data and completing DPIAs where Processing presents a high risk to rights and freedoms of Data Subjects; integrating data protection into internal documents including this Data Protection Policy or Privacy Notices; regularly training Company Personnel on the UK GDPR, this Data Protection Policy and data protection matters including, for example, Data Subject's rights, Consent, legal bases, DPIA and Personal Data Breaches. The Company must maintain a record of training attendance by Company Personnel; and regularly testing the privacy measures implemented and conducting periodic reviews and audits to assess compliance, including using results of testing to demonstrate compliance improvement effort. Record-keeping The UK GDPR requires us to keep full and accurate records of all our data Processing activities. You must keep and maintain accurate corporate records reflecting our Processing including records of Data Subjects' Consents and procedures for obtaining Consents in accordance with any Company record-keeping guidelines in force from time to time. These records should include, at a minimum, the name and contact details of the Controller and the DPO, clear descriptions of the Personal Data types, Data Subject types, Processing activities, Processing purposes, third-party recipients of the Personal Data, Personal Data storage locations, Personal Data transfers, the Personal Data's retention period and a description of the security measures in place. To create the records, data maps should be created which should include the detail set out above together with appropriate data flows. Training and audit We are required to ensure all Company Personnel have undergone adequate training to enable them to comply with data privacy laws. We must also regularly test our systems and processes to assess compliance. You must undergo all mandatory data privacy related training and ensure your team undergo similar mandatory training \[in accordance with any Company mandatory training guidelines in force from time to time. You must regularly review all the systems and processes under your control to ensure they comply with this Data Protection Policy and check that adequate governance controls and resources are in place to ensure proper use and protection of Personal Data. Privacy By Design and Data Protection Impact Assessment (DPIA) We are required to implement Privacy by Design measures when Processing Personal Data by implementing appropriate technical and organisational measures (like Pseudonymisation) in an effective manner, to ensure compliance with data privacy principles. You must assess what Privacy by Design measures can be implemented on all programmes, systems or processes that Process Personal Data by taking into account the following: the state of the art; the cost of implementation; the nature, scope, context and purposes of Processing; and the risks of varying likelihood and severity for rights and freedoms of Data Subjects posed by the Processing. Data controllers must also conduct DPIAs in respect to high-risk Processing. You should conduct a DPIA (and discuss your findings with the DPO) when implementing major system or business change programs involving the Processing of Personal Data including: use of new technologies (programs, systems or processes), or changing technologies (programs, systems or processes); automated Processing including profiling and ADM; large-scale Processing of Special Categories of Personal Data or Criminal Convictions Data; and large scale, systematic monitoring of a publicly accessible area. A DPIA must include: a description of the Processing, its purposes and the Data Controller's legitimate interests if appropriate; an assessment of the necessity and proportionality of the Processing in relation to its purpose; an assessment of the risk to individuals; and the risk mitigation measures in place and demonstration of compliance. You must comply with any Company guidelines on DPIA and Privacy by Design in force from time to time. Automated Processing (including profiling) and Automated Decision-Making Generally, ADM is prohibited when a decision has a legal or similar significant effect on an individual unless: a Data Subject has given Explicit Consent; the Processing is authorised by law; or the Processing is necessary for the performance of or entering into a contract. If certain types of Special Categories of Personal Data or Criminal Convictions Data are being processed, then grounds (b) or (c) will not be allowed but the Special Categories of Personal Data and Criminal Convictions Data can be Processed where it is necessary (unless less intrusive means can be used) for substantial public interest like fraud prevention. If a decision is to be based solely on Automated Processing (including profiling), then Data Subjects must be informed when you first communicate with them of their right to object. This right must be explicitly brought to their attention and presented clearly and separately from other information. Further, suitable measures must be put in place to safeguard the Data Subject's rights and freedoms and legitimate interests. We must also inform the Data Subject of the logic involved in the decision making or profiling, the significance and envisaged consequences and give the Data Subject the right to request human intervention, express their point of view or challenge the decision. A DPIA must be carried out before any Automated Processing (including profiling) or ADM activities are undertaken. Where you are involved in any data Processing activity that involves profiling or ADM, you must comply with any Company guidelines on profiling or ADM in force from time to time. Direct marketing We are subject to certain rules and privacy laws when marketing to our customers. For example, a Data Subject's prior consent is required for electronic direct marketing (for example, by email, text or automated calls). The limited exception for existing customers known as "soft opt in" allows organisations to send marketing texts or emails if they have obtained contact details in the course of a sale to that person, they are marketing similar products or services, and they gave the person an opportunity to opt out of marketing when first collecting the details and in every subsequent message. The right to object to direct marketing must be explicitly offered to the Data Subject in an intelligible manner so that it is clearly distinguishable from other information. A Data Subject's objection to direct marketing must be promptly honoured. If a customer opts out at any time, their details should be suppressed as soon as possible. Suppression involves retaining just enough information to ensure that marketing preferences are respected in the future. You must comply with any Company guidelines on direct marketing to customers in force from time to time. Sharing Personal Data Generally we are not allowed to share Personal Data with third parties unless certain safeguards and contractual arrangements have been put in place. You may only share the Personal Data we hold with another employee, agent or representative of our group (which includes our subsidiaries and our ultimate holding company along with its subsidiaries) if the recipient has a job-related need to know the information and the transfer complies with any applicable cross-border transfer restrictions. You may only share the Personal Data we hold with third parties if: they have a need to know the information for the purposes of providing the contracted services; sharing the Personal Data complies with the Privacy Notice provided to the Data Subject and, if required, the Data Subject's Consent has been obtained; the third party has agreed to comply with the required data security standards, policies and procedures and put adequate security measures in place; the transfer complies with any applicable cross border transfer restrictions; and a fully executed written contract that contains UK GDPR-approved third party clauses has been obtained. You must comply with any Company guidelines on sharing data with third parties in force from time to time. Changes to this Data Protection Policy We keep this Data Protection Policy under regular review. This version was last updated in \[January] 2021. This Data Protection Policy does not override any applicable national data privacy laws and regulations in countries where the Company operates. Acknowledgement of receipt and review I, \[insert name], acknowledge that on \[insert date], I received and read a copy of the Company's Data Protection Policy and understand that I am responsible for knowing and abiding by its terms. I understand that the information in this Data Protection Policy is intended to help Company Personnel work together effectively on assigned job responsibilities and assist in the use and protection of Personal Data. This Data Protection Policy does not set terms or conditions of employment or form part of an employment contract. Signed ………………………………………………………. Printed Name ………………………………………………. Date ………………………………………………………….
diff --git a/Documentation/imports/policy-donations.md b/Documentation/imports/policy-donations.md
new file mode 100644
index 0000000..773d0f0
--- /dev/null
+++ b/Documentation/imports/policy-donations.md
@@ -0,0 +1,224 @@
+# Policy: Donations
+
+
+
+## Table of Contents
+
+
+
+Expand / Collapse
+
+
+
+1. Introduction
+ * Definitions
+ * About this document
+ * Scope
+2. Policy details
+ * IT and Communications Systems statement
+ * Organization infrastructure and services
+ * Platform Requirements
+ * Bring Your Own Device (BYOD)
+ * Equipment security and Digital Credentials
+ * Renewal of Digital Credentials
+ * MFA/2FA
+ * Systems and data security
+ * Using Channels
+ * Using the Internet
+ * Blocking of information
+ * Personal use of our systems
+ * Prohibited use of our systems
+ * Monitoring
+
+
+
+## Introduction
+
+### Definitions
+
+This document employs terms related to the [DCDR Advocacy](http://tiof.click/Advocacy) that can be found in the [TIOF terminology](http://tiof.click/Terminology).
+
+For a structure of The IO Foundation, please visit
+
+* The IO Foundation's [Organizational Chart](http://tiof.click/TIOFOrgChart)
+* The IO Foundation's [Organizational Nomenclature](http://tiof.click/OrgNomenclature)
+
+Back to top
+
+### About this document
+
+This document sets out the standards established by TIOF in matters of Information Technologies and Communication Systems you will need to be aware of while being a Member for TIOF. It establishes the facilities that you are provided of, when we will monitor their use and the actions the organization will take if you breach these standards. You should familiarize yourself with them and comply with them at all times. Any questions you may have with regard to its contents or what you have to do to comply with it should be referred to your corresponding Team HR Coordinator.
+
+Any Member who breaches this Policy will face disciplinary action, which could result in dismissal for gross misconduct. Any non-Member who breaches this Policy may have their contract (or equivalent official relationship with TIOF) terminated with immediate effect.
+
+This document complements TIOF's [Code of Conduct](http://tiof.click/TIOFPolicyCoC)
+
+This document does not form part of any [Engagement Document](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#engagement-document) and we may amend it at any time.
+
+Back to top
+
+### Scope
+
+This document directly applies to:
+
+* All [TIOF Members](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#member)
+
+This document indirectly applies to:
+
+* All [TIOF Contributors](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors)
+
+The policies and/or procedures set out in this document apply to all TIOF Members unless otherwise indicated. They therefore apply to Directors, Advisers, Counselors, Staff, Volunteers and Interns; this is irrespective of their part-time, fixed-term or casual status. They equally apply to all [Contributors](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors) and will be used as part of the selection criteria when engaging with them.
+
+This document applies within all TIOF spaces, including (although not limited to) management activities, project contributions or events, and also applies when an individual is officially representing the broader community in public spaces. Examples of representing our community include (although not limited to) using an official e-mail address, posting via an official social media account or acting as an appointed representative at an event (online or offline).
+
+Back to top
+
+## Policy details
+
+### IT and Communications Systems statement
+
+The IO Foundation's IT and communications systems are intended to promote effective communication, working practices and an effective way to advance its advocacy. The organization is committed to provide with all necessary tools for Members to perform their tasks and to work jointly to ensure their responsible and safe use.
+
+Back to top
+
+### Organization infrastructure and services
+
+The IO Foundation has designed and implemented an infrastructure that enables the organization, its Members and Contributors, to perform their assigned responsibilities and move forward TIOF's advocacy.
+
+To facilitate remote collaboration, most of this infrastructure is built around online platforms that are made available through a single working interface.
+
+Back to top
+
+#### Platform Requirements
+
+This is the current list of requirements for any service or platform adopted by The IO Foundation:
+
+Mandatory
+
+* [x] GDPR Compliant
+
+Desirable
+
+* [x] Open Source
+
+Back to top
+
+### Bring Your Own Device (BYOD)
+
+Because of it's global orientation, The IO Foundation heavily relies on a strong base of Members that are distributed across the globe. In order to facilitate this distributed and remote structure, we encourage Members to use their own devices to perform their tasks. The organization will do all possible efforts to provide with the online tools necessary to implement those tasks and will assist Members in configuring and securing their devices ot the extend of its possibilities.
+
+Back to top
+
+### Equipment security and Digital Credentials
+
+Members will be provided with a number of [Digital Credentials](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#digital-credentials) to access the different online platforms and services. While the organization will make all efforts to assist Members, including training, to secure their [Digital Credentials](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#digital-credentials), the responsibility to protect them ultimately lies in them.
+
+You are responsible for the security of the equipment allocated to or used by you (BYOD) and you must not allow it to be used by anyone other than in accordance with this Policy. You should use your [Digital Credentials](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#digital-credentials) on all IT equipment, particularly items that you take out of the office, keep them confidential and update them regularly.
+
+You must only log on to our systems using your own [Digital Credentials](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#digital-credentials). Under no circumstance you should use another Member's or allow anyone else to log on using yours.
+
+If you are away from your desk you should log out or lock your computer. You must log out and shut down your computer, or alternatively send it to hibernation, at the end of each working day.
+
+Back to top
+
+#### Renewal of Digital Credentials
+
+Back to top
+
+#### MFA/2FA
+
+As an additional layer of security, the organization encourages, and sometimes mandates, the use of MFA/2FA techniques to further secure the Members' [Digital Credentials](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#digital-credentials). Suitable training is provided to understand how to configure and use these techniques.
+
+Back to top
+
+## Systems and data security
+
+You should not delete, destroy or modify existing systems, programs, information or data (except as authorized in the proper performance of your duties).
+
+You must not download or install software from external sources without authorization. Downloading unauthorized software may interfere with our systems and may introduce viruses or other malware. Failure to comply may result in facing compensation charges.
+
+You must not attach any device or equipment including mobile phones, tablet computers or USB storage devices to our systems without authorization. We monitor all e-mails passing through our system for viruses. You should exercise particular caution when opening unsolicited e-mails from unknown sources. If an e-mail looks suspicious do not reply to it, open any attachments or click any links in it. Inform someone immediately if you suspect your computer may have a virus.
+
+Back to top
+
+## Using Channels
+
+Members are provided with a number of [Official Channels](http://tiof.click/TIOFChannels) to communicate among themselves and with third parties. Any sharing of information using any of these is considered a _communication_.
+
+When communicating with third parties by means on any of the available Channels, you must at all times adopt a professional tone and observe appropriate etiquette under the guidance of the [Media Policy](http://tiof.click/PolicyMedia).
+
+Remember that such communications can be used in legal proceedings and that even when deleted these may remain on the system and be capable of being retrieved.
+
+You must not send abusive, obscene, discriminatory, racist, harassing, derogatory, defamatory, pornographic or otherwise inappropriate communications. All such behaviors will be treated according to our [Anti harassment and Anti bullying Policy](http://tiof.click/PolicyAHAB).
+
+You should not:
+
+* send or forward private communications at work which you would not want a third party to read;
+* send or forward chain communications, junk communications, cartoons, jokes or gossip;
+* contribute to system congestion by sending trivial communications or unnecessarily copying or forwarding communications to others who do not have a real need to receive them; or
+* send communications from on behalf of another Member (unless authorized) or under an assumed name/identity.
+
+Do not use your own personal channels (such as e-mail, instant messaging applications, etc.) to send or receive communications for the purposes of your responsibilities with TIOF. Only use the accounts we have provided for you.
+
+We do not permit access to web-based personal e-mail such as Gmail or Hotmail on our computer systems at any time due to additional security risks.
+
+Back to top
+
+## Using the Internet
+
+When specifically provided, Internet access is provided primarily to perform your responsibilities in TIOF. Occasional personal use may be permitted as set out in below.
+
+You should not access any web page or download any image or other file from the Internet which could be regarded as illegal, offensive, in bad taste or immoral. Be always mindful of possible extra limitations set forward by your local jurisdiction. As a general rule, actions (or lack of thereof) that result in accessing information or files that might be a source of embarrassment if made public will be a breach of this Policy.
+
+Back to top
+
+### Blocking of information
+
+We may block or restrict access to some websites at our discretion. These will always be reasoned as a security measure and never as an attempt to curtail freedom of information or expression.
+
+Back to top
+
+## Personal use of our systems
+
+We permit the incidental use of our systems to send personal communications, browse the Internet and make personal phone calls subject to certain conditions. _Personal use is a consideration and not a right_. It must not be overused or abused. We may withdraw permission for it at any time or restrict access at our discretion.
+
+Personal use must meet the following conditions:
+
+* it must be minimal and take place substantially outside of normal working hours (that is, during your lunch break and before or after work);
+* it must never make use of [official TIOF channels](http://tiof.click/TIOFChannels);
+* should the above not be possible, and in matters of extreme urgency, personal communications should prefix the term "Personal - " in the subject header;
+* it must not affect your work or interfere with the TIOF's advocacy;
+* it must not commit TIOF to any marginal costs and
+* it must comply with our all of our Policies and Procedures, including but not limited to the [Equal Opportunities Policy](http://tiof.click/TIOFPolicyEqualOpportunity), [Anti-harassment and Anti-Bullying Policy](http://tiof.click/TIOFPolicyAHAB), [Anti-corruption and Anti-bribery Policy](http://tiof.click/PolicyACAB), [Data Protection Policy](http://tiof.click/PolicyDataProtection) and [Disciplinary Procedures](http://tiof.click/ProcedureDisciplinary).
+
+Back to top
+
+## Prohibited use of our systems
+
+Misuse or excessive personal use of our Channels or inappropriate Internet use will be dealt with under our [Disciplinary Procedure](http://tiof.click/ProcedureDisciplinary). Bear in mind that misuse of the Internet can in some cases be a criminal offense.
+
+Creating, viewing, accessing, transmitting or downloading any of the following material will usually amount to gross misconduct (this list is not exhaustive):
+
+* pornographic material (that is, writing, pictures, films and video clips of a sexually explicit or arousing nature);
+* offensive, obscene or criminal material or material which is liable to cause embarrassment to us or to any of Members or Contributors;
+* a false and defamatory statement about any person or organization;
+* material which is discriminatory, offensive, derogatory or may cause embarrassment to others (including material which breaches our [Equal Opportunities Policy](http://tiof.click/TIOFPolicyEqualOpportunity), [Anti-harassment and Anti-Bullying Policy](http://tiof.click/TIOFPolicyAHAB));
+* confidential information about TIOF or any of our Members or Contributors (except as authorized in the proper performance of your responsibilities);
+* unauthorized software;
+* any other statement which is likely to create any criminal or civil liability (for you or TIOF); or
+* music or video files or other material in breach of copyright.
+
+Back to top
+
+## Monitoring
+
+Our systems enable us to monitor telephone, e-mail, Internet and other communications methods. In order to carry out legal obligations in our role as an employer (when applicable), your use of our systems including (but not limited to) the telephone and computer systems (including any personal use) may be continually monitored by automated software or otherwise.
+
+We reserve the right to retrieve the contents of communications or check Internet usage (including pages visited and searches made) as reasonably as necessary in the interests of the organization, including for the following purposes (this list is not exhaustive):
+
+* to monitor whether the use of the communication channels or the Internet is legitimate and in accordance with this Policy;
+* to find lost communications or to retrieve communications lost due to computer failure;
+* to assist in the investigation of alleged wrongdoing; or
+* to comply with any legal obligation.
+
+Back to top
diff --git a/Documentation/imports/policy-health-and-safety.md b/Documentation/imports/policy-health-and-safety.md
new file mode 100644
index 0000000..aa664a7
--- /dev/null
+++ b/Documentation/imports/policy-health-and-safety.md
@@ -0,0 +1,142 @@
+# Policy: Health and Safety
+
+
+
+## Table of Contents
+
+
+
+Expand / Collapse
+
+
+
+1. Introduction
+ * Definitions
+ * About this document
+ * Scope
+2. Policy details
+ * Health and Safety statement
+ * Health and Safety Officer
+ * Health and Safety is a collective effort
+ * Information and consultation
+ * Training
+ * Equipment
+ * Accidents and first aid
+ * Fire safety
+ * Risk assessments and measures to control risk
+ * Computers and display screen equipment
+
+
+
+## Introduction
+
+### Definitions
+
+This document employs terms related to the [DCDR Advocacy](http://tiof.click/Advocacy) that can be found in the [TIOF terminology](http://tiof.click/Terminology).
+
+For a structure of The IO Foundation, please visit
+
+* The IO Foundation's [Organizational Chart](http://tiof.click/TIOFOrgChart)
+* The IO Foundation's [Organizational Nomenclature](http://tiof.click/OrgNomenclature)
+
+Back to top
+
+### About this document
+
+This document sets out the necessary arrangements for ensuring TIOF meets its health and safety obligations towards Members and anyone visiting its premises or affected by our advocacy that you will need to be aware of while being a Member for TIOF. You should familiarize yourself with it and comply with it at all times. Any questions you may have with regard to its contents or what you have to do to comply with it should be referred to your corresponding Team HR Coordinator.
+
+Any Member who breaches this Policy will face disciplinary action, which could result in dismissal for gross misconduct. Any non-employee who breaches this Policy may have their contract (or equivalent official relationship with TIOF) terminated with immediate effect.
+
+This document complements TIOF's [Code of Conduct](http://tiof.click/TIOFPolicyCoC)
+
+This document does not form part of any [Engagement Document](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#engagement-document) and we may amend it at any time.
+
+Back to top
+
+### Scope
+
+This document directly applies to:
+
+* All [TIOF Members](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#member)
+
+This document indirectly applies to:
+
+* All [TIOF Contributors](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors)
+
+The policies and/or procedures set out in this document apply to all TIOF Members unless otherwise indicated. They therefore apply to Directors, Advisers, Counselors, Staff, Volunteers and Interns; this is irrespective of their part-time, fixed-term or casual status. They equally apply to all [Contributors](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors) and will be used as part of the selection criteria when engaging with them.
+
+This document applies within all TIOF spaces, including (although not limited to) management activities, project contributions or events, and also applies when an individual is officially representing the broader community in public spaces. Examples of representing our community include (although not limited to) using an official e-mail address, posting via an official social media account or acting as an appointed representative at an event (online or offline).
+
+Back to top
+
+## Policy details
+
+## Health and Safety statement
+
+The IO Foundation values, above anything, the wellbeing of its Members. Health is a critical matter and we will always strive to ensure a healthy and safe environment for our Members and Contributors. Likewise, the organization expects its Members to actively participate in such commitment. The organization will not tolerate deliberate actions make use of their absences in a judicious manner and will not tolerate abuses.
+
+Back to top
+
+## Health and Safety Officer
+
+You should report any health and safety concerns immediately to the \[TIOF] Team Human Resources Coordinator.
+
+Back to top
+
+## Health and Safety is a collective effort
+
+All Members share responsibility for achieving safe working conditions. You must take care of your own health and safety and that of others, observe applicable safety rules and follow instructions for the safe use of equipment. You must co-operate with Management on health and safety matters, including the investigation of any incident.
+
+Failure to comply with this policy may be treated as misconduct and dealt with under our [Disciplinary Procedure](http://tiof.click/ProcedureDisciplinary).
+
+Back to top
+
+## Information and consultation
+
+We will inform and consult the Health and Safety Officer or directly with all staff regarding health and safety matters.
+
+Back to top
+
+## Training
+
+We will ensure that you are given adequate training and supervision to perform your responsibilities competently and safely. Members will be given a Health and Safety Induction and provided with appropriate safety training.
+
+Back to top
+
+## Equipment
+
+You must use equipment in accordance with any instructions given to you. Any equipment fault or damage must immediately be reported to the Health and Safety Officer. Do not attempt to repair equipment unless trained to do so.
+
+Back to top
+
+## Accidents and first aid
+
+Details of first aid facilities and the names of trained first aiders are made available on our [TIOF internal communication Channels](https://github.com/TheIOFoundation/TIOF/wiki/Media-Kit#Internal-Communications).
+
+All accidents and injuries at work, however minor, should be reported to
+
+* the Health and Safety Officer or,
+* your corresponding Team Coordinator or,
+* your corresponding Team Human Resources Coordinator.
+
+All incidents are to be recorded in the [Accident Book](http://tiof.click/TIOFAccidentBook).
+
+Back to top
+
+## Fire safety
+
+All Members should familiarize themselves with the fire safety instructions in their physical offices (when applicable), which are displayed on notice boards and near fire exits in the workplace.
+
+This should also be considered should the Member perform duties remotely.
+
+If you hear a fire alarm, leave the building immediately by the nearest fire exit and go to the fire assembly point outside of the premises.
+
+For physical offices, fire drills will be held at least every 12 months and must be taken seriously; we also carry out regular fire risk assessments and regular checks of fire extinguishers, fire alarms, escape routes and emergency lighting.
+
+Back to top
+
+## Risk assessments and measures to control risk
+
+We carry out general workplace risk assessments periodically, both in physical offices and remotely. The purpose is to assess the risks to health and safety of Members, visitors and other third parties as a result of our activities and to identify any measures that need to be taken to control those risks.
+
+Back to top
diff --git a/Documentation/packages/page-7.md b/Documentation/infrastructure/basic-needs.md
similarity index 100%
rename from Documentation/packages/page-7.md
rename to Documentation/infrastructure/basic-needs.md