Overview

This article will cover how Users are created for students, faculties, and admins (not system admin).

• See also: RIO Education User Profile, Custom Permission, and Permission Sets‍.

Student User

Method 1 - Self register via the Student Community

When a new applicant signs up as new Community users (to apply for a program), a User record will be automatically created with the profile and permission set mentioned above.

This is provided that this function is set up correctly as follows: RIO Ready: Login/Self-Registration Functionality Setup‍.

Method 2 - Approving the Program Application

For some institutions, new applicants will not be signing up on the portal (as seen above).

Some institutions will use a web form to collect applications, and convert the Leads into Contacts.

Then, when the admin approves a Program Application / Application (EDA) for new applicants (on their behalf), this will automatically create User records for the applicants, which are also registered in the Student Community.

This will allow the students to log in to the Student Community.

This is provided that:

• The trigger handler PRAP_StudentCommunity_TDTM (if you are using Program Application) or APP_StudentCommunity_TDTM (if you are using Application (EDA)) is active.
  
  
  
  
• The 'Auto Student Community Registration' custom setting is enabled (and the correct student profile and permission set are populated).
  
  

Method 3 - Manual creation

1. Create a Contact.
   
   
   • If it is for a student, set the Contact Type = Student.
     
     
     
     
2. On the top right side of the page, click on 'Enable Customer User'.
   
   
   
   
3. Add the required User License and Profile.
   
   The User License should be 'Customer Community Login', and the Profile should be 'REDU - Student'.
   
   
   Ensure that the student user is given the 'REDU - Student' Permission Set Assignment.
   If you have other Permission Set Assignments for students, ensure that a Permission Set Group containing those are assigned.
   
   
   
   
4. An email will be sent to the Student user to verify their account.

Faculty User

1. Create a Contact record for the Faculty.
   
   Ensure that the 'Faculty Member?' is checked, and an email address is included.
   
   
   
   
2. Check the 'Create Community User' checkbox, which will automatically create a User for the Contact.
   
   ** Note:
   
   
   • After checking the checkbox, you will need to link the User to the Contact. Populate the 'User' field to lookup to the User record. 
     
     
     
   • If no User has been automatically created, see the 'Note' section below to resolve this.
     
     
     
3. Make sure that the newly created User's profile and permission set are correct (as seen above in the table).
   You can head to Setup > Users to check these.
   
   
4. Under Setup, head to Public Groups, and add the User to the REDU - Faculty Public Group.
   
   
   

Note

The 'Create Community User' checkbox on the Contact will automatically create a User for the Faculty, provided that:

• The trigger handler CON_FacultyCommunity_TDTM (for Contact) is active.
  
  
  
  
• The 'Auto Faculty  Community Registration' custom setting is enabled.
  Also, ensure that the correct faculty profile and permission set are populated ( ** the profile will depend on your User License).
  
  

Admin User (not System Admin)

1. Head to Setup > Users.
   Create a new user.
   
   
   
   
   
2. Assign 'Salesforce' as the User License, and 'REDU - Admin' as the Profile.
   
   The Admin must have a Role, in order to own records created by Guest Users (i.e. files uploaded by Community Guest Users). If there are no Roles, you can create one via Setup > Roles.
   
   
   
   
3. Ensure that the User is given the 'REDU - Admin' Permission Set Assignment.
   If you have other Permission Set Assignments for that User, ensure that a Permission Set Group containing those are assigned.
   
   
   
   
4. An email will be sent for the admin to verify their account.

See also

RIO Education User Profile, Custom Permission, and Permission Sets‍.