--- title: "Configuring the 2 Year/Community College Model Database" slug: "customizing-your-turnkey-2-yearcommunity-college-database" description: "Maximize your 2-year/community college database with our detailed guide on customizing preconfigured features and functionalities for a tailored user experience." tags: ["Database Setup"] updated: 2026-04-14T16:23:26Z published: 2026-04-14T16:23:26Z canonical: "knowledge.technolutions.net/customizing-your-turnkey-2-yearcommunity-college-database" --- > ## Documentation Index > Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt > Use this file to discover all available pages before exploring further. # Configuring the 2 Year/Community College Model Database When your Slate for Admission database was provisioned, it came from one of three templates: - the [4 Year & Graduate Admissions model](/v1/docs/customizing-your-turnkey-4-year-graduate-admissions-database), - the **2 Year/Community College model**, or - the [K-12 School Admission model](/v1/docs/configuring-the-k-12-school-admission-model-database) 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 πŸ“ **Location:** Records β†’ β€œAlexander Hamilton” We've set up **Alexander Hamilton** for testing purposes. > [!TIP] > ✨ **Tip:** Create additional test records with different data configurations. Use your [test environment](/v1/docs/test-environments-test-environments) first before moving to production. ## Applications #### Slate-hosted application pages* πŸ“ **Location:** Forms β†’ 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: - Start Term πŸ“– **Further reading:** [The Application Editor](/v1/docs/introduction-application-editor) #### 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](https://knowledge.technolutions.net/v1/docs/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](/v1/docs/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](/v1/docs/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](/v1/docs/period-and-round-structure) ## Reader & workflows Your database includes two workflows: - **Application Review** - **Early Alert Review** πŸ“ **Location:** Database β†’ Workflows πŸ“– **Further reading:** [Workflows](/v1/docs/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](/v1/docs/workflows#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](/v1/docs/workflows#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](/v1/docs/workflows#reader-tabs) #### Review form A generic Reader Review form has been created and configured for the Review Bin. πŸ“– **Further reading:** [Workflow review forms](/v1/docs/workflow-review-forms), [Reader review form calculations](/v1/docs/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](/v1/docs/decision-release-overview) 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](/v1/docs/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](/v1/docs/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](https://knowledge.technolutions.net/docs/decisions-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](/v1/docs/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](/v1/docs/system-emails), [Customize System Emails](/v1/docs/creating-a-system-email) ## 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](/v1/docs/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](/v1/docs/form-and-event-communications-triggers-groups), [Form and Event Communications Merge Fields](/v1/docs/form-and-event-communications-merge-fields), [Text Messaging (SMS) Overview](/v1/docs/text-messaging-sms-overview), [SMS to Impress](/v1/docs/sms-to-impress#summary-0-0) ## 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](/v1/docs/exporting-data-overview) #### Voyager: Document export πŸ“ **Location:** Queries / Reports β†’ Document Export This query has been pre-configured. You may customize filtering. πŸ“– **Further reading:** [Document Export Query](/v1/docs/creating-a-document-export-query-with-configurable-joins) ## 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](/v1/docs/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](/v1/docs/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](/v1/docs/getting-started-with-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](/v1/docs/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](/v1/docs/fields-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](/v1/docs/prompts-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](/v1/docs/user-accounts#roles), [Custom permissions](/v1/docs/custom-permissions) ## Related - [Configuring the 4 Year & Graduate Admission Model Database](/customizing-your-turnkey-4-year-graduate-admissions-database.md)