Partner Training: Student Community
Take a look at the student community video below that is shared publicly for an overview of the student community and the modules that we have available to deploy.
Typical Modules deployed in the student community:
Application Form(s) - These are the flows that were described in the applications training module.
Profile - This is fairly standard salesforce profile information. #NOTE The profile information for RIO is stored in the Students contact record. There is also a "User" record. If a user edits the profile in the standard profile tab in communities, e.g. changes a phone number, then a trigger will need to also update that to the contact. RIO has some pre-defined triggers to do this.
-
Programs. RIO comes with a pre-configured programs lightning component that can be used in the community. This component covers:
Program Enrollment (through the pathway tab).
Fees.
Session Calendar - The session calendar inside the programs component is filtered to just that program. The one available outside the component shows bookings for all programs.
Results.
Selecting and viewing the status of Disciplines (Majors).
Groups: This is just an implementation of Chatter groups. NOTE# we share a community for faculty and students so that they can be in the same chatter groups. If you are using SAL, and faculty are not using the community, then they will not be able to join the same groups as the students.
Cases: RIO uses standard case functionality also. Case types can be configured with the standard types of EDU cases, such as: Request to Defer, Request for Credit Transfer, Request for Withdrawal etc. We have some demo process builder automation and approval process in the standard demo environment that can be copied for implementations.
Community users
Students require a login for the community. This may have already been generated in the application process if the school requires the applicants to self-register. In this case, the users will have a personal email address as the username, and a trigger should run to change the login to a school-based email address. This is not a standard trigger in v2.9 but may be available in the future. We have done this for customers, and can provide the trigger code on request.
For applicants who did not have a community login prior to be accepted into a program, there is a standard RIO trigger that is based on the Program Application object that can create the user, and email them to set a password.
Single Sign On : Salesforce support SSO for communities. As this is a standard Salesforce offering for communities we will not cover that here. If you are interested there is a great trailhead here: Use Salesforce Identity Beyond Your Internal Org
Salesforce Customer Community or Customer Community +? RIO Education natively works with Customer Community. Recall in the scheduling module, we use our bookings object that is available to customer community users. If you are also introducing SAL to the school, then you will need CC+ users. This is primarily to support the use of Events for advisor appointment bookings.
Groups
In our demo environment, we often show community groups, using chatter. We use the standard Salesforce features for chatter groups, and are subject to the same limitations between internal users and community users. E.g. they cannot be in the same chatter groups. This is important to note for internal users such as registrars who may want to post messages to groups of students. Automation will need to be developed if you want them to be able to do this without "switching" views into the community. A simpler approach may to create a custom community view (APP) and allow internal users to switch to post into groups.