Clear answers before you join or partner with GOB.

Service development should follow recurring member needs, available capacity, risk, and the ability to define a responsible delivery process. A useful service is prioritized before a decorative feature.

The 2030 framework focuses on continental coordination, dependable member services, digital infrastructure, high-quality partnerships and measurable institutional value.

No. A priority is a direction for development. The website should separately identify what is active, what is being built and what remains a future objective.

Growth should consider credible member participation, service use, programme quality, cooperation and operational readiness rather than relying only on country or follower counts.

Organizations are more likely to use partnerships and opportunities responsibly when they have clear governance, records, contacts, digital systems and decision processes.

Yes. Priorities can be reviewed when member needs, institutional capacity, risks or the external environment change.

No. Member organizations keep their own mission and governance. GOB provides shared infrastructure and cooperation pathways rather than taking over their planning.

GOB is presented as a governed project network. Membership does not transfer the legal identity or governing authority of participating organizations to GOB.

The role is intended to develop the member network, support Country Coordinators, identify cooperation opportunities, maintain regional relationships and report through the central project structure.

Appointments should follow the applicable appointment and delegation framework. A continental role does not create unlimited authority to create titles or commitments.

Country priorities should reflect actual member needs, local context, programme opportunities, partner availability and the wider continental plan.

A country can have member activity before a formal coordinator exists, but the public website should not invent an office holder.

Central GOB structures can continue administrative coordination until a formal appointment is made. The page should state the vacancy accurately.

The coordinator represents GOB only within an authorized project mandate. Member organizations retain their own representatives and legal leadership.

Approved public profiles can be grouped by continent and country using the central member directory or the relevant continental page.

Regional procedures can support local delivery, but they should remain consistent with central GOB policies and the authority formally delegated to the continental structure.

Onboarding confirms the institutional record, explains policies, connects the member to the relevant network structure and identifies the first useful services or programmes.

Potentially yes. Public directory publication is separate from the private administrative membership record and should follow the applicable publication basis or consent process.

Material changes can include legal status, leadership, primary contact, organization name, website, public profile information or other facts relevant to eligibility and communication.

Not necessarily. However, persistent unreachability, obsolete records or failure to respond to material administrative issues can trigger review.

Yes. A proportionate response can restrict a specific programme, public listing or partner benefit when the issue does not justify broader action.

The organization remains responsible for its own records and information. GOB processes submitted information for defined project purposes under the privacy framework.

Yes, but a recommendation does not replace the normal application and review process.

No. Membership is linked to the approved legal or institutional entity and cannot simply be transferred to an unrelated organization.

The project should assess the provider, the actual member need, eligibility, pricing or access conditions, support model, material exclusions and reputational or security concerns.

Any exclusivity would require careful review and clear justification. GOB should protect member choice and avoid hidden restrictions that do not serve the network.

Only where there is an appropriate and transparent process. Member data should not be handed to a partner simply because a commercial relationship exists.

A knowledge partner can contribute expertise, research, training, guidance or institutional learning rather than a commercial product.

A technology partner can support digital infrastructure, software, cloud services, hosting, security or related tools under documented terms.

A partnership can have its own commercial or sponsorship terms without changing the current free core organization membership model, provided the arrangement is transparent and appropriate.

The project should avoid presenting exploratory relationships as active partnerships. Public logos should follow the appropriate approval or agreement.

Benefits should be reviewed for availability, usage, support quality, member feedback, changes in partner terms and continued strategic fit.

The Trust Center groups the policies and controls that explain how GOB handles governance, privacy, safeguarding, complaints, representation and related institutional risks.

The public framework does not present consequential membership decisions as fully automated. Material decisions should remain under appropriate human oversight.

Private review information should not automatically become public. Publication must have a clear purpose and respect privacy, fairness and record controls.

The record should be corrected promptly and the underlying appointment register should be checked so public information and administrative records remain aligned.

References can help distinguish approved records from informal copies and make appointments, policies or institutional documents easier to trace.

A member portal can be developed as the digital system matures. Any authenticated system should be introduced with appropriate security, privacy and access controls.

Applicable rights depend on the data and legal context. Some information may need to be retained for legal, security, safeguarding, dispute or institutional record purposes.

Members should use secure accounts, protect credentials, handle shared documents carefully and follow any security requirements attached to project systems or partner services.

No. A GOB public profile shows participation in the project under its rules and should not be interpreted as governmental accreditation.

GOB can request correction when a statement misrepresents GOB, MYCDIC, a project role, a benefit or an institutional relationship.

Requests involving institutional positions, partnerships, appointments or sensitive issues should be directed to the appropriate authorized contact rather than answered informally.

Unsupported numbers can weaken trust. The project should publish metrics only when the measurement basis is defined and the underlying records support the claim.

A Continental President is the appointed GOB leader responsible for coordinating project development across a continent. The role includes member-network development, country coordination, recruitment, partnership development, opportunity circulation and reporting through the GOB project structure.

No. A role should only display a name and portrait after formal appointment. Until then, the relevant continental page identifies the position as appointment pending rather than publishing an invented or informal office holder.

Continental leadership can identify, approach and support prospective organizations, but admission remains subject to the central GOB review process, applicable policies and any required documentation or due diligence.

Country Coordinators support local network development under the relevant continental structure. They help maintain local relationships and recruitment while escalating institutional, policy or cross-border matters through the Continental President and central GOB offices.

No. GOB titles are project-governance roles. They do not create governmental, diplomatic, consular or public-authority status and must not be presented as such.

Each continental page includes a controlled directory area. Organizations are shown only after admission and approval for public listing. Empty or developing regions are displayed honestly rather than filled with invented members.

Potentially yes. Membership is linked to the organization, while programme eligibility can be geographic or thematic. Cross-continental participation depends on the relevant programme, capacity, partner conditions and the organization’s role.

Use the Leadership Appointments page and the relevant leadership or continental page. GOB publishes a person as active only after formal appointment. Pending roles remain visibly pending rather than being filled with an informal or unconfirmed name.

Official Notices are reserved for changes that matter to the public record, such as appointments, policy changes, programme status or partnership activation. They help external institutions distinguish a formal status change from a routine news update.

No. A country page should appear when there is enough leadership, member participation or real activity to justify a public structure. GOB does not create empty country pages simply to claim broader geographic reach.

The Country Coordination Directory is designed to publish current country-level appointments when they are formally confirmed. A coordinator title does not create diplomatic, consular or governmental status.

News and Updates explain current activity. Official Notices record changes that affect institutional or public status. A programme story can be news; the formal appointment of a Continental President should be an official notice.

Companies and service providers can use the Offer a Member Benefit pathway. GOB reviews the usefulness, eligibility, provider terms, public wording and verification method before an offer is presented as active.

No. GOB separates activity, outputs and outcomes. Impact and Results pages should explain the evidence method and avoid presenting targets, intended outcomes or incomplete records as established results.

The Policies & Standards page provides a central route to membership, privacy, safeguarding, representation, brand, conflict-of-interest, partnership and trust documents.

Yes, where the purpose is relevant and the research relationship is properly defined. University cooperation may include applied research, training, student engagement and knowledge exchange, subject to privacy, ethics and data requirements.

It identifies the institutional relationship: GOB is a strategic project of the Moroccan Youth Council for Diplomatic and International Cooperation. It does not mean that a GOB member organization becomes a MYCDIC branch or governmental body.

The file gives search and generative systems a concise map of the project’s main entity, membership, network, policy and knowledge pages. It complements, rather than replaces, normal website content and structured data.

Yes, public pages may be cited as sources. For appointments, policies, partnership status or institutional identity, use the current page or official notice and avoid relying on old screenshots or third-party summaries when a primary GOB source exists.