To test the configuration of any given community, you will need to register as a new student, ensuring that the system creates a new Community user record, and related Contact record, sends the welcome email, allows the successful creation of a password, and redirects the user to the correct landing page.
After logging in, you will see a landing page dependent on the type of Digital Experience you have configured. Below you will find example screenshots from each type of Experience. Once you have confirmed it is correct, you can move forward with additional configurations, ensuring that you have tested the student-facing experience to ensure all permissions are correct for the Customer Community User (TargetX) profile.
This page means that you have successfully completed the configuration steps and you can now move forward with adding branding and configuring the Online Application and/or Application Requirements Manager (Checklist Items).
This message means you’ve successfully completed the configuration steps and you can now create a new Dynamic Portal and publish it to this Digital Experience.
This page means that you have successfully completed the configuration steps and you can now move forward with adding branding and building Organization Events.
This page means that you have successfully completed the configuration steps and you can now move forward with adding advisor availability to the scheduler, or create Organization Events with a type of Interview selected on creation.
If you are unable to complete any one of the above steps, it is recommended that you use the TargetX Permission Scanner as a starting point for troubleshooting. If you are unable to register for your new Digital Experience, you should validate permissions for the Site User of the community. If you are unable to view options or take actions (i.e. start an application, schedule an appointment, register for an event or view portal content), then you should validate permissions for the Customer Community User (TargetX) profile. In either case, make sure that you remove the TXStandardPageStopper and grant access to the Apex Class and Visualforce page detailed in the instructions linked above.
Proceed to: Additional Recommended Configurations