- 28 Jan 2025
- 6 minute read
- Print
- DarkLight
- PDF
Configuring the 2 Year/Community College Model Database
- Updated 28 Jan 2025
- 6 minute read
- Print
- DarkLight
- PDF
When your Slate for Admission database was provisioned, it came from one of two templates:
the 2 Year/Community College model
This article serves as a reference for each pre-configured object in your database.
Some of these objects must be configured before they can be used. Asterisks *
denote action is required.
Test record
We've set up Alexander Hamilton for testing purposes.
β¨ Tip: Create additional test records with different data configurations. Use your test environment first before moving to production.
Applications
Slate-hosted application pages*
Enrollment Information Page*: This page can be customized in any way to meet your institutional needs.
The following prompt-based fields have been pre-configured. You must modify and add the prompt list that mirror your institutional options:
Preferred Start Term
Application creation form
π Location: Forms β Folders β Application Creation
An application creation form has been pre-configured to include round and pin. These must be updated prior to going live. Communications have been configured and need to be customized. You will need to customize the "Sender" field to reflect your institutional email.
π Further reading: Application Creation Form
Status portal
π Location: Database β Portals β Application Status Portal
The application status portal has been pre-configured. However, this portal can be enhanced based on institutional needs at any time.
π Further reading: Custom Applicant Status Portal
Submission requirements
π Location: Database β Application Logic
All common submission requirements have been pre-configured based on historical knowledge of other institutional expectations. These can all be modified or removed. You can also create any additional requirements at any time.
π Further reading: Application Logic Settings
Rounds & periods*
π Location: Database β Application Periods / Application Rounds
*Placeholder periods and rounds have been pre-configured. These must be updated prior to going live.
π Further reading: Period and round structure
Reader & workflows
Your database includes two workflows:
Application Review
Early Alert Review
π Location: Database β Workflows
π Further reading: Workflows
Bins
Bins and columns have been created based on historical knowledge of general institutional needs. They can be configured or renamed to reflect your process.
π Further reading: Bins
Bin & queue rules
A Do Nothing rule, Awaiting Submission and Awaiting Materials automations have been configured. Automation within the reader can increase efficiency of your review process. Further configuration is recommended.
π Further reading: Bin & queue automations
Reader tabs
Basic reader tabs have been created for:
Dashboard (General Applicant Information)
Personal Information
Application Information
Application
Academic History
Employment History
Additional Tabs and Materials should be configured to reflect your process.
π Further reading: Reader Tabs
Review form
A generic Reader Review form has been created and configured for the Review Bin.
π Further reading: Workflow review forms, Reader review form calculations
Dashboard portal
π Location: Database β Portals β Reader dashboard
A Workflow Dashboard has been pre-configured and can be modified as necessary.
Decision management
The Slate decision management system is streamlined and comprehensive, allowing for the release of electronic decisions to application records on an individual or batch basis. The system uses reader evaluations, rankings, and other inputs to make decisions that can be released immediately or scheduled for future release.
Decision codes
π Location: Database β Decision Codes
Best practice Decision Codes have been pre-configured and can be customized to meet your institutional process.
π Further reading: Decision codes
Decision Letters*
π Location: Database β Letter Templates
Three example placeholder letters have been pre-configured that can be customized to meet your institutional language and branding.
π Further reading: Decision letters
Automation
π Location: Database β Rules β Folders β Checklists
The following rule has been pre-configured in an inactive status. It must be activated when ready to use:
Add Decision Reply Form to Checklist
π Further reading: Decision automations
Reply form
π Location: Forms β Folders β Decisions
A reply to offer of admission letter has been pre-configured.
The following rules have been pre-configured using the best practice decision codes:
Add Enrollment Deposit Payment Due: This rule is inactive and should only be activated if your institution receives payment
Add Accepted Offer Decision
Add Declined Offer Decision
Deliver
Campaign
π Location: Deliver β Campaigns
Two example templates, Applicants and Prospects, exist in your database and are mobile responsive.
You will need to customize the "Sender" field to reflect your institutional email.
π Further reading: Build a drip marketing campaign
Templates
π Location: Deliver β Folders β Templates
An example Call to Action button template has been pre-configured. This template has not been added to any communications.
Application System Emails
π Location: Deliver β Folders β System
The most common system mailings have been pre-configured. You can edit these at any time. Additional system mailings can be created.
The following System emails have been generally configured with your {{System-Database-Friendly-Name}}
:
Application Created
Application Submission
Account Password Reset
Account Email Migration
Recommendation Request (To Recommender)
Recommendation Submission (To Recommender)
Recommendation Submission (To Applicant)
Mailings may need additional customization to reflect your branding/style guide. You will need to customize the "Sender" field to reflect your institutional email.
π Further reading: System emails, Customize System Emails
Events
Templates*
π Location: Events β Folders β Templates
Three event templates have been created equipped with event communications. Event details must be customized.
The following must be updated in order to use these templates:
Location
Description
Registration Settings
Rescheduling (if applicable)
π Further reading: Events
Template Communications
π Location: Event template β Edit Communications
The following emails have been configured for each event. You will need to customize the "Sender" field to reflect your institutional email. You will also need to Activate each mailing in order for them to function.
Confirmation Page
Confirmation Email
Reminder Email
Reminder SMS
Thank You for Attending Email
Sorry We Missed You Email
π Further reading: Form and Event Communications, Form and Event Communications Merge Fields, Text Messaging (SMS) Overview, SMS to Impress
Forms
Request for Information communications*
π Location: Forms β Folders β Recruitment β Request for Information β Edit Communications
The following communications have been preconfigured but must be modified further in order to activate and use. These communications do not include the pre-configured template.
Confirmation Page Only*
Email Only*
Queries / Reports
Query: Data Export - SFTP (Slate to SIS)
π Location: Queries / Reports β Data Export - SFTP (Slate to SIS)
This query has been pre-configured but must be modified further in order to activate and use.
π Further reading: Exporting data
Voyager: Document export
π Location: Queries / Reports β Document Export
This query has been preconfigured. You may customize filtering.
π Further reading: Document Export Query
Custom Tabs
More Information tab
π Location: Database β Tabs β Person Tabs
Update the form to include any additional institutional-specific person-scoped fields, as necessary.
Application Details Tab
π Location: Database β Tabs β Application Tabs
Update the form to include any additional institutional-specific application-scoped fields, as necessary.
π Further reading: Custom tabs
Origin Groups & Sources
Groups
π Location: Database β Origin Groups
Common groups have been pre-configured. Add any additional groups as necessary.
Sources
π Location: Database β Origin Sources
Common sources have been pre-configured. Add any additional groups as necessary.
π Further reading: Origin sources
Rules
Staff Assignments
π Location: Database β Rules β Folders β Staff Assignments
The staff assignment exclusively group has been pre-configured. The remainder of these rules commonly are unique to each institutions. Be sure to update the filter criteria and all users associated. Alternatively, use these as a reference and delete them all / create your own from scratch.
π Further reading: Staff assignments
Populations
π Location: Database β Rules β Folders β Populations
Two sample populations have been configured that can be used throughout drip marketing campaigns.
Applicant
Prospects & Inquiries
π Further reading: Creating populations
Fields & prompts
Fields
π Location: Database β Fields
Staff Assigned: The prompt list is directly associated with users created in your database. This prompt list will automatically update as users are or customized.
π Further reading: Field settings
Prompts
π Location: Database β Prompts
The following prompt lists have been pre-configured, are associated with standard fields and can be customized:
degree
education_level
ferpa_access
ferpa_info
ferpa_who
high_school_grad
major
minitary_branch
reference_type
sex
visa
The following prompt lists have been pre-configured, are associated with standard fields and can be customized:
enrollment_status
entrance_status
*The following prompt lists have been pre-configured with placeholder values, are associated with custom fields, and must be customized:
term
*
π Further reading: Prompt settings
Users & Access
Role Groups & Permissions
π Location: Database β User Permissions
The following roles have been pre-configured and can be updated to remove or add permissions that make sense for your users. These roles can be granted to any new user that you create that meet that criteria:
Academic Advisor
Admission Counselor
Admissions Inbox
π Further reading: Role settings, Custom permissions