Speak Slate fluently.
Short, plain-English definitions for the terms you'll hear all day — with examples and common misconceptions.
The single entity Slate tracks — usually a person.
The central place for information and activity associated with an individual.
A defined place where one specific piece of information is stored.
The actual information stored in a field on one particular record.
The starting point of a query — the type of thing you're asking about.
A saved question you ask of your Slate data.
A condition used to narrow which records are included in a query.
A piece of information returned in the query results.
A controlled way to bring in related rows from another base.
A standalone data structure that lives outside the person record.
An individual item within a dataset.
Logic that allows Slate to evaluate conditions and perform an action.
What causes Slate to check whether a rule applies.
The conditions that must be true for a rule to apply.
What Slate does when a rule's conditions are met.
Using configured logic to reduce repetitive manual work or consistently support a process.
A structured process that moves records through defined steps.
Slate's email and communications module.
The people or records selected to receive a communication.
The person or identity a communication appears to come from.
Using available data to tailor a communication to the recipient.
The action or next step a communication asks the recipient to take.
A reusable audience defined by a query.
Slate's application review module.
A user-facing way to collect data into Slate.
A question or input presented on a form to collect information.
The information submitted through a form.
A scheduled experience or activity managed through Slate.
A person's connection to an event.
How a student has interacted with the institution through activities such as visits, programs, or events.
A Slate area used to receive and manage responses to supported communications.
A communication received from or sent to a student.
Information sent to a student through Slate, and the responses that can come back.
A form used within Reader to record notes, ratings, recommendations, or other review information.
A way Reader records are organized into groups or stages for review.
The process of examining information before determining a next step, action, or outcome.
A branded interface for an external audience.
How Slate confirms who a user is so the experience can be tailored to their record.
The outcome recorded on an application.
A communication associated with a decision that notifies the student of the outcome.
A student's submission to a process, and the record a decision is usually attached to.
An item or document stored in Slate and associated with a record or process.
A Material type delivered or commonly used within Slate.
A Material type created by an institution for its own processes.
A way to track what is required, received, or still outstanding in a process.
One individual requirement or task being tracked on a checklist.
Something the student or institution expects to be satisfied before or during a process.
The current state of a requirement, such as complete or outstanding.
A group of applications evaluated together.
The term or cycle an application targets.
A person who has access to the Slate environment.
Access that determines what a user can see, use, change, or manage.
The work a user is expected to perform in Slate.
What a user is able to reach or do inside Slate.
A configured connection that moves data between Slate and another system.
The structure and instructions Slate uses to interpret incoming data.
The logic used to determine which Slate record incoming data belongs to.
The relationship between incoming values and Slate fields or structures.
The process of bringing external data into Slate.
The system or process receiving data sent out of Slate.
The authoritative place a value should be maintained.
The record or structure that logically owns a piece of information.
Information that may occur more than once and may need multiple related records or entries.
The practice of making access and configuration decisions intentionally and explainably.