Partnerships, Teams, and Employer Use

A partnership enquiry, discovery call, demonstration, quote request, email exchange, or page visit does not create a binding partnership, reseller relationship, endorsement, agency, joint venture, franchise, exclusivity, or authority to represent Daskerel.

A partnership exists only when Daskerel and the other party agree written commercial terms or a statement of work. Those written terms control scope, pricing, seats, support, reporting, lab usage, data handling, branding, confidentiality, renewal, and termination.

Partnership enquiries should use partnerships@cloudforgeacademy.co.uk. Legal notices should use legal@cloudforgeacademy.co.uk.

Teams access is designed for organisations, cohorts, employers, training providers, mentors, and workforce readiness programmes that need named learner seats, certification paths, team materials, cohort visibility, lab governance, manager reporting, and evidence workflows.

Teams starts with a quote request. Daskerel reviews seat count, country or region, billing interval, procurement or invoice needs, support requirements, onboarding scope, learning path, reporting expectations, and live-cloud lab usage before checkout or invoice payment.

After an approved Teams checkout is paid and the payment webhook provisions the Team account, the billing owner receives the agreed visibility. Named learners must be invited to the Team. Each invitation consumes one paid seat and grants Teams materials only to the invited learner email for the subscription period.

If Teams materials are missing, Daskerel checks the signed-in email, billing owner email, invited learner email, paid seat allowance, Team account, Stripe subscription, current subscription period, and any support or security restriction.

Daskerel is responsible for making the agreed platform features available, applying reasonable security controls, operating support and billing workflows, providing access to agreed materials, and maintaining management workflows for quotes, invitations, support, evidence review, and feedback.

Depending on the plan or statement of work, Daskerel may provide learning paths, mock exams, study planners, dashboards, lab guidance, portfolio prompts, evidence review, cohort reporting, or manager reporting.

Daskerel does not guarantee exam passes, job offers, hiring decisions, salary outcomes, employer evidence acceptance, uninterrupted third-party services, every cloud region, every vendor lab, or every external provider system.

Partners and employers must provide accurate organisation details, billing owner details, seat counts, learner emails, country or region information, procurement requirements, onboarding needs, reporting requirements, and compliance constraints.

Partners and employers must invite only authorised learners, keep learner lists current, request removals or seat changes promptly, avoid sharing accounts, ensure acceptable use, and report errors, security issues, billing issues, or support needs through the correct route.

Partners and employers remain responsible for their own employment, recruitment, training, safeguarding, HR, procurement, tax, regulatory, and internal compliance decisions. Daskerel readiness signals support learning review but do not replace assessment, supervision, or hiring judgement.

A specialist reviewer, curriculum creator, instructor, facility operator, technology provider, or accreditation organisation must work only within the scope approved in a signed agreement or statement of work. The document should identify the Daskerel school, activity risk class, deliverables, acceptance criteria, competent personnel, insurance, intellectual-property position, data handling, payment model, review date, and termination rights.

Physical or regulated activity requires responsibility for facilities, equipment, risk assessment, supervision, safeguarding where applicable, emergency response, incidents, maintenance, learner induction, and competence checks to be allocated before access opens. A commercial agreement cannot override a prohibited activity or missing safety, ethics, privacy, or facility approval.

Partners must warrant that contributed content is accurate to the agreed standard, lawfully supplied, does not infringe third-party rights, and does not make unauthorised accreditation, clinical, diagnostic, vendor, employment, or safety claims. Daskerel may audit, correct, suspend, or withdraw content or delivery when evidence expires or a material quality, safety, legal, data, or reputation concern arises.

Learners must use their own named account and email address. Credential sharing, access bypass, redistribution, lab misuse, secrets upload, attacks, unsafe evidence, incomplete proof, and misrepresentation are not allowed.

Learners remain responsible for official exam booking, vendor rules, study effort, lab cleanup, safe portfolio evidence, and lawful use of any third-party cloud, tool, or exam system.

Evidence, readiness dashboards, and proof packs are learning and review signals. They are not guarantees of competence, exam success, job readiness, employment, promotion, or employer acceptance.

Evidence submissions must not include passwords, API keys, unnecessary personal data, private customer data, confidential employer data, unsafe screenshots, proprietary infrastructure details, or unauthorised third-party material.

Evidence approval should be performed by authorised evidence-reviewer roles and kept separate from general learner support where possible. Unreviewed uploads are learner submissions and are not independently verified by Daskerel.

Live-cloud and sandbox labs are subject to the selected plan, fair-use limits, provider availability, regions, risk profile, budgets, cleanup requirements, and any written lab-governance agreement. Higher usage, larger cohorts, or specialised regions may require approval before access is expanded.

Learners, partners, and employers must follow lab instructions, cleanup steps, security rules, and cost-control rules. Daskerel may pause or restrict lab access for security, cost, policy, credential, provider-abuse, or operational-risk reasons.

Cloud, certification, and tooling providers are independent. Their outages, prices, region availability, quotas, exam rules, account policies, or API changes may affect platform workflows and lab availability.

Daskerel, partners, and employers should agree what learner, billing, cohort, reporting, support, and evidence data is needed. Daskerel processes personal data under the Privacy and GDPR Policy and any agreed data processing terms.

Partners and employers must not send unnecessary sensitive data, secrets, production credentials, confidential records, regulated information, or special category data through ordinary platform workflows unless an approved secure route has been agreed.

Reports, dashboards, exports, and evidence summaries must be used only for the agreed purpose. Learner-level sharing may require notice, lawful basis, consent, or a separate written agreement depending on context.

Daskerel owns the platform, brand, course structure, study plans, lessons, mock questions, explanations, lab instructions, dashboards, reports, templates, and original materials unless a separate written licence says otherwise.

Partners, employers, instructors, reviewers, and learners must not copy, resell, white-label, scrape, republish, train models on, redistribute, or commercially exploit Daskerel materials without written permission. Branding, logos, screenshots, public claims, and reports require approval before public use.

Partner or employer materials remain the responsibility of the party providing them. That party must have the rights needed to share, use, adapt, or publish those materials through Daskerel workflows.

Vendor names are used descriptively. AWS, Microsoft Azure, Google Cloud, CompTIA, Docker, Cisco, HashiCorp, CNCF, Red Hat, Linux Foundation, and other names or trademarks belong to their respective owners.

No partner, employer, learner, reviewer, instructor, or team member may describe official vendor endorsement, accreditation, sponsorship, certification-vendor status, or commercial partnership unless Daskerel has approved the exact wording in writing and the relevant vendor relationship exists.

Case studies, success stories, testimonials, employer logos, cohort outcomes, pass-rate claims, hiring claims, and readiness claims require permission, evidence, and approval before publication.

Changes to seats, billing, support scope, labs, reporting, content, onboarding, evidence review, or delivery expectations must follow the agreed operational route and may require a revised quote, written approval, or statement of work.

Support, billing, Teams, partnership, privacy, legal, and security issues should be routed to the relevant Daskerel mailbox. Partnership and employer-success enquiries should use partnerships@cloudforgeacademy.co.uk. Incidents involving data, unsafe evidence, payment risk, public claims, or security should be escalated to owner, legal, security, and operations management as appropriate.

Daskerel may suspend, limit, or end access for failed payment, seat misuse, account sharing, security risk, legal requirements, confidentiality or data mishandling, or material breach of the applicable terms.