Salesforce Education Cloud Consultant

You cannot design for a school you do not understand. This module covers how colleges and schools are organized, how terms, programs and courses fit together, and who holds a say in a project.

• K–12 and higher education compared
• Departments, offices and decision makers
• Academic terms, programs and courses
• Registrar, admissions, advising and advancement
• Seasonality in the academic calendar
• Common vocabulary and how to use it

You build A stakeholder and process summary for an institution, in its own language.

Data that fits the institution makes every feature easier. You see how students, applicants, families, programs, terms and affiliations are represented, and how to extend the model without breaking what is standard.

• People: applicants, students, guardians and staff
• Programs, terms and courses as records
• Affiliations and relationships
• Extending the model with custom fields and objects
• Keeping the model aligned across teams

You build A data model diagram for an institution, marking what is standard and what is added.

Configuration turns requirements into a working system. You choose settings, record types, layouts and permissions that match how the institution works, and record why each choice was made.

• Reading configuration against requirements
• Record types and page layouts for each team
• Apps and navigation for staff
• Permission sets by role
• Settings that change behavior across the org
• Configuration documentation

You build A configured sandbox for one office, with a record of each setting and its reason.

Admissions is where most institutions begin. You design how inquiries are captured, applications progress, communication keeps applicants engaged, and decisions turn into enrolled students.

• Capturing inquiries from forms and events
• Application stages and checklists
• Communication plans for applicants
• Reviewing and deciding applications
• From admitted to enrolled
• Measuring the funnel

You build An admissions process design from inquiry to enrollment, with its stages and records.

Retention depends on timely help. You design advising appointments, success plans, early alerts and outreach so that staff can see which students need attention and act while it still helps.

• Advising appointments and notes
• Success plans and goals
• Early alerts and referrals
• Outreach campaigns to students
• Cases for student services
• Handing a student between offices

You build A student success process with alerts, referrals and an advisor view.

A good design weighs options honestly. You turn an institution’s requirements into a fit-and-gap view, choose between configuration, code and third-party tools, and describe the solution so that others can build it.

• Eliciting requirements across offices
• Fit-and-gap analysis
• Configuration, code and third-party options
• Designing process and data together
• Writing a solution design others can build from
• Reviewing a design with stakeholders

You build A fit-and-gap analysis and solution design for one office’s requirements.

Student records are sensitive, and the law protects them. You apply privacy rules such as FERPA to the design, control who may see which records, and plan consent where guardians and minors are involved.

• Education privacy rules in outline
• Who may see which student records
• Sharing and field security by office
• Consent for minors and guardians
• Handling data requests
• Reviewing a design for privacy risk

You build A privacy and access design that shows what each office may see and why.

Education Cloud rarely stands alone. You plan how it connects to student information, learning and payment systems, choose how data moves and how often, and plan migration so that history is not lost.

• Systems on a typical campus
• Integration patterns and their trade-offs
• Choosing how often data moves
• Migrating historical student data
• Duplicate and quality management
• Keeping integrations observable

You build An integration and migration plan linking three campus systems.

Leaders ask whether programs work. You choose between standard reports and dashboards and more advanced analytics, and design measures for enrollment, engagement and retention that the institution can trust.

• Reports and dashboards for institutional questions
• When advanced analytics is justified
• Enrollment and funnel measures
• Engagement and retention measures
• Dashboards for different audiences
• Defining a measure the same way everywhere

You build A dashboard design for a provost or head of school, with each measure defined.

Delivery decides whether a design is used. You plan testing and acceptance, train staff in their own tasks, schedule rollout around the academic calendar, and prepare support for the first weeks.

• Test planning and acceptance
• Training staff by role
• Rollout timing against the academic calendar
• Cutover and early support
• Gathering staff feedback after launch

You build A rollout plan for a single office, with its test, training and support steps.

Work a full engagement on paper. You take an institution’s goals, design configuration, data, integration and analytics, and present a plan that covers privacy, delivery and the choices you rejected.

• Framing the institution’s goals
• Designing the solution end to end
• Planning delivery and rollout
• Documenting rejected options
• Presenting to institution leaders

You build A solution design for a university project, with data, integration and rollout plans.