ccc_id

cccId

The user’s unique CCCID for Federated Identity.

The unique identifier for a single user’s account. This identifier is assigned during account creation in OpenCCC.

VarChar 8

The format of the ccc_id is:

Positions 1 - 3:   AAA thru ZZZ (Sequentially assigned beginning with AAA)

Positions 4 – 7:  0001 thru 9999 (Sequentially assigned beginning with 0001 for each value in positions 1-3)

Position 8:  For future expansion if all values become exhausted.

Note:  In positions 1-3, “I” and “O” are not used to avoid confusion with “0” and “1”.

No.  This is a system assigned field and is not entered by the user.

System assigned.

Populates the CCCApply applications from the applicant's OpenCCC Account at the time of submission.

System-generated unique identifier.

System will support expansion of CCCID to 8 characters (XXXXNNNN).

This field is passed as part of a submitted application to each college and is stored in the college Student Information System (SIS).  This field can be used for student authentication when a student signs in at a college.  It can be passed as an attribute to student statewide services so the service can verify the student has an OpenCCC account and perform automatic sign in.  This field will also be passed as an MIS field. 

accepted_terms

acceptedTerms

Acknowledgment by the user of acceptance of the OpenCCC student account Terms of Use.

Boolean

True / False

If email address is verified during account creation, then display the terms disclaimer that pertains to contact by email.

If mobile phone is verified during account creation, then display the terms disclaimer that pertains to contact by phone and/or text message.

No

Default = True

Stored with date and timestamp in database at time of account creation.

Required response; else error message, ”You must agree to the Terms of Use.”
ES: “Debe aceptar los Términos de uso.”

Acknowledge Terms of Use

[ checkbox ] (Email): “I agree to the Terms of Use and to receive emails at any email address I have provided or may provide in the future, from any entity associated with my application process, including but not limited to my designated schools and programs.”

(Phone): “I agree to the Terms of Use and to receive calls and/or texts and emails at any phone number and/or email I have provided or may provide in the future, including any wireless number, from any entity associated with my application process, including but not limited to my designated schools and programs.”

Terms of Use

DELIVERED via SuperGlue for Apply.

accepted_terms_timestamp

acceptedTermsTimestamp

Date and time of user’s acceptance of the Terms of Use.

date timestamp with time zone

 No

Stored with <accepted_terms> at time of account creation.  SuperGlue delivery only.

DELIVERED via SuperGlue for Apply.

address_validation_override

addressValidationOverride

Indicates that the USPS address validation service. does not recognize the address as provided by the user and has suggested an alternative to the user.

VarChar 20

True / False

Yes

If no suggested address is returned by the USPS address validation service, a null value is stored.

Address override is stored as True or False.

IF user accepts a USPS “suggested address” displayed, then <addressValidationOverride> is stored as True; otherwise it is stored as False.

If USPS address validation returns a notice of Invalid address, then user must override the response (True) or return to the address fields and edit their entry (False).

Invalid Address message box:
“We are unable to validate your address with the USPS Postal Service. Please review the address below and review or edit.”
[Button] “I verify my address”
[Button] “Edit my address”

Verify Address message box:
”To ensure an accurate address we suggest the one below. Would you like to use the suggested address?”
[Button] “Yes”
[Button] “No”

For a Suggested Address: “To ensure an accurate address we suggest the one below. Would you like to use the suggested address?”

After all required address fields have been entered in the Contact Information section of the Account Profile, the USPS address verification service is run to check if the address exists, and whether the address meets USPS address standards.

Indicates that the user has accepted an address alternative provided by the USPS address validation service does not recognize the address as provided by the user and has suggested an alternative to the user.

DELIVERED via SuperGlue for Apply.

address_validation_override_timestamp

addressValidationOverrideTimestamp

Date and time that the user chose to override a suggested address that meets USPS format, or s of the address validation override.

date and time with time zone

 Stored with <address_validation_override> at time of account creation. SuperGlue delivery only.

Yes

DELIVERED via SuperGlue for Apply.

birthdate

birthdate

User’s date of birth.

date, 10

Provided in this format: yyyy-mm-dd

Valid date

No

None

Storage: Stored in database (with leading zeros as appropriate) for use in auto-population. Included in Account Profile.

Usage: Birthdate is used in the admission application to calculate age, to identify applicants who are too young to transact business online per COPPA (Child Online Privacy Protection Act —under age 13), and to identify minors for residency calculation and collection of parent or guardian contact information. OCR acknowledges that collection of birth date is allowed under California State law.

For residency and minor identification, the applicant’s age is calculated as of the day before the term_start date <ResidencyDeterminationDate>.

Used for residency and minor identification, the applicant’s age is calculated as of the day before term_start date <ResidencyDeterminationDate>.

Date of birth is required; else error message, “Valid date of birth is required.”

Confirm date of birth is required; else error message, “Valid Confirm Date of Birth is required.”

Both entries must match exactly; else error message, “Date of Birth entries do not match.”
(ES: “Las entradas de la fecha de nacimiento no coinciden.”)

Must be a valid date (‘dd’ must be appropriate for ‘mm’ and ‘yyyy’, for example, 02/29/2009 would not be a valid date); else error message, “Invalid date. Please enter the date in the format MM/DD/YYYY.”

Date must be after 01/01/1901; else error message, “Must be on or after 01/01/1901.”

Date must be before <current_date>; else error message, “Must be before <current_date>.”

Must not edit or update birthdate and full legal name at the same time; else error message, “Do not update your name (first, middle or last) and birth date at the same time.”
ES: “No actualice su Nombre (primer, segundo o apellido) y fecha de naciemiento a la mismo tiempo.”

“Please enter your birth date”.

Date of Birth* [textbox + calendar widget]
(ES: “Fecha de Nacimiento”)

Confirm Date of Birth* [textbox + calendar widget]
(ES: “Confirmar fecha de nacimiento”)

MIS DED SB03

Birthdate is sensitive information protected by federal law and the Office of Civil Rights (with regards to age discrimination). Any change to the text, prompt, access, or transmission of this data item must be approved by the Legal Counsel of the CCC Chancellor’s Office and the Office of Civil Rights.

Date of birth information may not be provided to staff in the capacity of making a decision to admit an applicant until after the applicant is admitted—that is, uniformly enabled to register for classes.

Users cannot change their legal name and date of birth at the same time to ensure two or more users cannot share an account (prevent duplicate accounts).

OCR acknowledges that collection of date of birth is allowed under California State law.

email

User’s email address.

Character varying, 254

Two fields; each up to 254 characters, alphanumeric plus ‘@’ and ‘.’

Text string in valid email address format.

No

No

Used in account creation as a method to verify identity. Can be set as the user’s preferred method of contact by the California Community Colleges or an authorized partner.

Only one field is stored in database. Included in Edit Account Profile.

Must contain one ‘@’ symbol and one “.” (the “@” symbol cannot be the first character).

Required user response. Must be unique.
Email address and Confirm Email inputs must be identical and must meet validation checks; else error message, “Your Email Address is invalid or absent. You must enter a valid Email Address”.

Create Account:

Required response else error message: “Email address is required.”
(ES: “Se requiere Correo Electrónico.”)

Must meet validation check; else error message,“Please enter a valid email address.” (ES: “Por favor, introduzca una dirección de correo electrónico válida.”)

Must be unique; else error message: “Your email address is already in use. Please enter a different Email Address.”

Sign In:

Required response unless phone number is entered; else error message, “Email or mobile phone required.” (ES: Se requiere correo electrónico o teléfono móvil.)

Must meet validation check; else error message, “Your mobile number, email or password is not recognized by our system. Need Help? Contact Support”
ES: “Nuestro sistema no reconoce su número de teléfono móvil, correo electrónico o contraseña.”

Legacy User Sign In:

Email address must be unique and meet format validation checks; else error message, “Your Email address is already in use. Please enter a different Email address, or contact a support representative.”

Create & Verify Account:

Email [textbox]

Create Account (Contact Information):

Email Address [textbox]

Confirm Email Address [textbox]

Sign In: Email or mobile phone* [textbox]

”Enter your email address to begin creating your California Community Colleges student account. You will receive a code via email to verify your identity and keep your account secure.

ES: “Entra tu dirección de correo electrónico para comenzar a crear su cuenta. Recibirás un código a través de correo electrónico para verificar su identidad y mantener su cuenta segura.”

A valid email address is required from each user and must be unique.

If the email address is verified during account creation, the system will pre-populate the <email> field in the Contact Information section and it doesn’t need to be entered again in Confirm Email). The pre-populated field will be disabled to prevent edits until the account creation process is complete.

Edits or changes to Email Address must go through verification process again.

If a mobile phone is verified during account creation, the user is required to enter their Email address on the Contact Information page; else error message, “Your Email Address is invalid or absent. You must enter a valid Email Address.”

DELIVERED via SuperGlue for Apply.

email_verified

emailVerified

Indicates that a valid email address has been verified with security code.

Boolean

True / False

Value stored in Account database with timestamp.

Email verified

ES: Correo Electrónico ha sido Verificado

If email address has been verified, an asterisk is displayed on the Email field label in the user’s Account Profile.

At least one method of contact must be verified.

DELIVERED via SuperGlue for Apply.

email_verified_timestamp

emailVerifiedTimestamp

Date and time of the verification of user’s email address.

date timestamp with time zone

Stored with <email_verified> at time of account creation.

DELIVERED via SuperGlue for Apply.

ssn

ssn

Applicant’s Social Security number or Taxpayer Identification Number.

text, 2147483647

Two fields; each 11 characters, numeric plus: format nnn-nn-nnnn Hyphens are not required in input but will be inserted in stored value.

Null or numeric string with hyphens. Encrypted

Yes. If applicant selects the check box indicating they do not have a social security number or taxpayer identification number or decline to provide one, then the ssn field stores null.

None

Only one field is stored in database

Required user response IF <ssn_no> = “Yes, I have a Social Security number or Taxpayer Identification number”, else error message, “You must provide your social security number or taxpayer identification number, or select the option indicating you don’t have a social security number or taxpayer identification number, or you decline to provide one at this time.”

Two SSN/TIN entries must match; else error message, “Your social security number or taxpayer identification number entries do not match.  Please try again.”

SSN entries must meet validity check (see below); else error message, “The social security number or taxpayer identification number you entered is invalid. Please re-enter the correct number, or select the option indicating that you don’t have a social security number or taxpayer identification number, or you decline to provide one at this time.”

Please enter your 9-digit social security number or taxpayer identification number.

Confirm your social security number or taxpayer identification number.

“Why am I being asked for my social security number?”

A Social Security Number (SSN) or Taxpayer Identification Number (TIN/iTIN) is needed to allow California Community Colleges to report tax-related information to the Internal Revenue Service (IRS).

However, this reporting is not required with respect to non-U.S. resident students (whether documented or undocumented), students taking non-credit courses, students whose qualified tuition and related expenses are waived or paid with scholarships or paid by an institutional third party including an employer or government agency. (26 C.F.R. § 1.6050S-1.) A SSN or TIN/iTIN is not required when IRS reporting is not required.

SSN is never displayed to the applicant and cannot be viewed by anyone properly or improperly using the applicant’s account.

Populated from legacy OpenCCC Account if available from previously submitted application at time of submission.

See Social Security Number: None for further Help text.

2025: SSN question and data fields were moved back into the OpenCCC Account system and unencrypted data will continue to be delivered to existing downstream applications and services (v.6.21.0).

2021: SSN question and data fields were moved from OpenCCC Account to CCCApply Standard application (v.6.9)

ssn_type

ssnType

Indicates the type of identification number being provided: social security number or taxpayer identification number.

character/numeric, 1

0 = SSN

1 = TIN

Null = no response

Yes

No error checking. Value is calculated automatically based on the number combination that is entered in the <ssn> input fields.

All validity checks will apply to the <ssn> field, but not the <ssn_type>.

If available, populated from legacy OpenCCC Account at time of submission.

No longer collected via UI form field. Auto filled based on SSN or TIN number provided.

December 2021 (v.6.9)

ssn_no

ssnNo

Applicant has no social security number or taxpayer identification number or declines to provide it at this time.

boolean, 1 (character, numeric)

1 = Yes (checked)  

0 = No (not checked)

Yes

Stored in database for use in auto population.

The “No” radio button must be selected if there is no entry for Social Security Number or Taxpayer Identification Number; else error message, “You must provide your social security number or taxpayer identification number, or select the option indicating you don't have a social security number or taxpayer identification number, or you decline to provide one at this time.”

If the radio button for “No, I do not have a social security number or taxpayer identification number, or I decline to provide one at this time.” is selected:

Conditionally hide the SSN fields

Conditionally display an informational message (see Additional Text, below)

Conditionally display the check box for noncredit, undocumented or international student, or nonresident alien (see Additional Text, below and the ssn_exception field details)

“Do you have a social security number or taxpayer identification number?”

[ ]  Yes, I have a social security number or taxpayer identification number.

[ ]  No, I do not have a social security number or taxpayer identification number, or I decline to provide one at this time.

Under the “Social Security Number” header:

The Social Security Number (SSN) or Taxpayer Identification Number (TIN/iTIN) is used by the college as a means of matching student records, facilitating federal financial aid, and reporting tax-related information to the Internal Revenue System (IRS). However, it is not required for admission.

The Why am I being asked for my social security number? Link displays this text in the Help window:

A Social Security Number (SSN) or Taxpayer Identification Number (TIN/iTIN) is needed to allow California Community Colleges to report tax-related information to the Internal Revenue Service (IRS).

However, this reporting is not required with respect to non-U.S. resident students (whether documented or undocumented), students taking non-credit courses, students whose qualified tuition and related expenses are waived or paid with scholarships or paid by an institutional third party including an employer or government agency. (26 C.F.R. § 1.6050S-1.) An SSN or TIN/iTIN is not required when IRS reporting is not required.

Informational Text (displays when you select the “No” radio button):

Just Remember...

Providing a social security number or taxpayer identification number is not required with respect to non-U.S. resident students (whether documented or undocumented), students taking noncredit courses, students whose qualified tuition and related expenses are waived or paid with scholarships or paid by an institutional third party including an employer or government agency. (26 C.F.R. § 1.6050S-1.) An SSN or TIN/iTIN is not required when IRS reporting is not required.

Check this box if you are a student enrolled exclusively in noncredit courses, an undocumented student, an international student, a nonresident alien, or another exception and do not have a social security number or taxpayer identification number.

AB46 and other legislation prohibit requirement of Social Security Number for admission or student record-keeping. While the colleges and many educational agencies remain reliant on SSN as the only reliable unique identifier of a student, the applicant must have the option not to provide it.

Moved from OpenCCC Account to Standard Apply in December 2021 (v.6.9)

ssn_exception

ssnException

Applicant is a student enrolled exclusively in noncredit courses, an international student, an undocumented student, a person who is not a citizen or national of the United States, or another exception and has no social security number or taxpayer identification number.

boolean

Default value: false

1 = Yes (checked) 

 0 = No (not checked)

Yes

Stored in database for use in auto population.

None; optional field.

[Checkbox]

Check this box if you are a student enrolled exclusively in noncredit courses, an international student, an undocumented student, a person who is not a citizen or national of the United States, or another exception and do not have a social security number or taxpayer identification number.

This check box only appears if an applicant selects the check box for "Check this box if you do not have a Social Security Number or Taxpayer Identification Number, or decline to provide one at this time." This check box allows international students to further indicate that they do not have an SSN or TIN.

AB46 and other legislation prohibit requirement of Social Security Number for admission or student record-keeping. While the colleges and many educational agencies remain reliant on SSN as the only reliable unique identifier of a student, the applicant must have the option not to provide it.

Due to recent IRS penalties levied against California community colleges for failing to provide, or providing invalid, social security or taxpayer identification numbers, CCCCO Legal advises compliance with IRS Requirements for Collecting SSN/ TINs (IRS p. 1758) – which includes displaying specific regulations/restrictions “to every student in attendance”- including those not required to provide a SSN/TIN or are not eligible to obtain one (see Exceptions).  Statement to students includes what is being collected and provided to the IRS and why, and the admonishments/ penalties for not providing one/valid number.  SSN Encouragement language contains reiteration of “statement” with additional confirmation checkbox or “click here to confirm acknowledgement of receipt of information.”

2025: SSN question and data fields were moved back into the OpenCCC Account system and unencrypted data will continue to be delivered to existing downstream applications and services (v.6.21.0).

2024: Minor text change made to the exception checkbox language replacing “nonresident alien” with “a person who is not a citizen or national of the United States” per changes recommended by the State to the Title V AB540 language.

2021: SSN question and data fields were moved from OpenCCC Account to CCCApply Standard application (v.6.9)

verification_confirmation_timestamp

verificationConfirmationTimestamp

Indicates the date and time of the student’s successful identity verification by the source vendor (as indicated in the ID Verification Source field).

Date, UTC - 24 max length

Timestamp set following successful ID verification by the source vendor.

Stored with the student’s Account data and passed to the college with submitted application.

For accounts created by the OpenCCC Account Creation tool only: date/timestamp is set at the time the account is created.

Yes

A null value should be acceptable and representative of a user who has never verified their identity.

System-generated. Does not display to applicants.

Implemented as part of the DMV ID Verification integration with OpenCCC.

October 2025

verification_optin_timestamp

verificationOptinTimestamp

Indicates the date and time that the student opts in to verify their identity through the source vendor.

Date, UTC - 24 max length

Two possible values:

timestamp value = student has been presented with the ID Verification page as part of the account workflows and chooses to proceed with identity verification. A timestamp is then recorded.

blank/null = the student has made no selection (since not all students will be presented with this page, it cannot/should not be a required piece of information for each account)

Date/timestamp is stored with Account data and passed to college with submitted application.

Value is not visible to the student on the Edit Profile page.

For accounts created by the OpenCCC Account Creation tool only: date/timestamp is set at the time the account is created.

Yes

If student opts-in to verify their identity, then the date/timestamp is set and the student is redirected to the source vendor for identity verification; otherwise, no value is set and student continues without verification.

If student chooses to "Verify Later" (link), then no value is set, the Decline Verification modal is displayed, and the student is NOT redirected to the source vendor for verification.

If student chooses NOT to verify their identity during the account creation process, they can verify later by clicking the link in their Account Profile (bottom of the page).

TBD: Value will be overwritten if the student returns and makes a different decision. (Currently testing with students.)

Implemented as part of the DMV ID Verification integration with OpenCCC.

October 2025

verification_workflow_status

verificationWorkflowStatus

Indicates the student’s current identity verification status.

Varchar, varying 50

blank/null = student has Never Verified.

verified = student’s ID verification was successful and is current.

staff_verified = student’s identity was verified by a college staff at the time the account was created; (but student has not self-verified with source vendor yet).

unverified = student’s identity was previously verified with source vendor but has since changed some OpenCCC account profile information.

expired = student’s identity was previously verified with source vendor,  but is currently expired.

Passes to college with application data and stored with student's OpenCCC Account data.

Blank (no value) is stored if the applicant is age 17 years or younger (minor).

Yes. 

Null = Blank = Never Verified = No value.

Blank (no value) is stored if the applicant is age 17 years or younger (minor).

No value / blank

Always displays to applicants 18 years or older; else does NOT display.

Does NOT display if <verification_workflow_status> = “verified” or “staff_verified” or if the applicant is under age 18.

New Account:  ID verification interstitial screen displays following OpenCCC account creation IF user is 18 years old or older (not a minor).

Existing Account: ID verification interstitial screen displays upon OpenCCC sign in if the user opted out of verification (<verification_workflow_status> = blank/no value OR if the current <verification_workflow_status> value = “unverified” or = “expired”.

Staff Verified Account: ID verification screen does not display upon OpenCCC sign in if user’s <verification_workflow_status> = “staff_verified”.

Verification Status Change: The Verify Your Identity screen will display at OpenCCC sign in if the user edits or changes specific Account Profile information.

IF applicant is age 17 years old or younger at Application create time, then set <verification_workflow_status> to “blank” (null/no value)

IF applicant edits their First name, Last name, SSN or Date of Birth information in their OpenCCC account profile, then display the ID verification screens and require a response (opt in or decline) upon save and/or upon user’s next Sign In.

IF applicant declines to complete verification process (opts out), then set <verification_workflow_status> to “blank” (null/no value) and display the Decline Verification modal.

IF student account is created by a college staff using the OpenCCC Account Creation tool only:
then set the <verification_workflow_status> to "staff_verified".

IF < verification_workflow_status> = "verified" OR "staff_verified" AND one year (365 full days) has lapsed since the current < verification_workflow_status> value was set, then change < verification_workflow_status> to "expired".

IF < verification_workflow_status> = “verified” OR “staff_verified”, then set the CCCApply fraud status value <fraud_status> to = 7 = “IDENTITY_VERIFIED”

EN: Verify Your Identity

ES: Verifica tu identidad

A <staff_verified> value is stored when an authorized college staff creates an OpenCCC account on behalf of a student (OpenCCC Administrator tool)

Implemented as part of the CA DMV ID Verification integration with OpenCCC.

October 2025

verification_source_identity

verificationConfirmationTimestamp

Indicates the third-party vendor used by the student for identity verification.

20 max length

·       idme

·       dmv

Value set upon successful verification.

Passed to the college with application data and stored with the student's Account data.

For accounts created by the OpenCCC Account Creation tool only: date/timestamp is set at the time the account is created.

Yes

A null value should be acceptable and representative of a user who has not verified their identity with the source vendor.

System-generated. Does not display to applicants.

Implemented as part of the ID Verification (DMV) integration with OpenCCC.

October 2025

idme_confirmation_timestamp Deprecated August 2026

idmeConfirmationTimestamp

Indicates the date and time when the student’s identity has been successfully verified by the http://ID.me vendor.

Date, UTC - 24 max length

Timestamp set and provided by the http://ID.me vendor’s API upon successful verification of a student’s identity.

Passed to the college with application data and stored with the student's Account data.

For accounts created by the OpenCCC Account Creation tool only: date/timestamp is set at the time the account is created.

Yes

A null value should be acceptable and representative of a user who has not verified their identity with the IDme vendor.

System-generated. Does not display to applicants.

Implemented as part of the IDme student ID verification integration with OpenCCC.

Production release: Feb 2, 2024
Pilot release: December 2023

Deprecated August 2026

idme_optin_timestamp Deprecated August 2026

idmeOptinTimestamp

Indicates the date and time when the student opts in to the ID.me verification process.

Date, UTC - 24 max length

Two possible values:

timestamp value = student has been presented with the ID Verification page in the OpenCCC interface and chooses to proceed with ID.me identity verification. A timestamp is then recorded.

blank/null = the student has made no selection (since not all students will be presented with this page, it cannot/should not be a required piece of information for each account).

Date/timestamp value is passed to college with application data and stored with student's account data.

Value is not visible to the student on the Edit Profile page.

For accounts created by the OpenCCC Account Creation tool only: date/timestamp is set at the time the account is created.

Yes

If student chooses NOT to verify their identity during the account creation process, they can verify later by clicking the link in their Account Profile (bottom of the page).

TBD: Value will be overwritten if the student returns and makes a different decision (currently testing with students.)

Implemented as part of the ID.me Student ID Verification integration with OpenCCC.

Production release: Feb 2, 2024
Pilot release: December 2023

Deprecated August 2026

idme_workflow_status Deprecated August 2026

idmeWorkflowStatus

Indicates the current status of the student's identity verification through the IDme process.

Varchar, varying 50

blank/null = student has never verified
expired = student’s identity was previously verified with IDme but is currently expired.
verified = student’s ID verification was successful and is current.
staff_verified = student’s identity was verified by a college staff at the time the account was created; (but student has not self-verified with ID.me yet).
unverified = student’s identity was previously verified with IDme but has since changed some OpenCCC account profile information.

Passed to college with application data and stored with student's OpenCCC Account data.

Yes

Null = Blank = Never Verified = No value.

Blank (no value) is stored if the applicant is age 17 years or younger (minor).

New Account: Displays to user following initial creation of their OpenCCC account IF the user is NOT a minor.

Existing Account: Displays to user following a sign in to OpenCCC, as well as at the bottom of the user's Edit Profile page (Account) IF the user is NOT a minor.

EN: Verify Your Identity
ES: Verifica tu identidad

02/07/24: “unverified” value added

A "staff_verified" value is stored when an authorized college staff creates an OpenCCC account on behalf of a student (OpenCCC Administrator tool)

Implemented as part of the http://ID.me student ID verification integration with OpenCCC.

Production release: Feb 2, 2024
Pilot release: December 2023

Deprecated: August 2026

idme_account_id Deprecated: August 2026

idmeAccountId

Internal field only, used to identify accounts that have encountered the IDme process.

Varchar, varying 256

Restricted use. Internal use only. Value is not deliverable.

Yes

Restricted use. Implemented as part of IDme student ID verification integration with OpenCCC.

December 2023

Deprecated: August 2026

firstname

User’s first name used on legal documents.

VarChar, 50

(extended character set, allowing hyphens, letters with diacritical marks or accents, etc.)

Text, string case; may be null.

Yes

None

Stored for use in auto-population.

Optional response.

May not be changed at same time as birthdate (i.e., during the same ‘Save’); else error message, “Do not update your name (first, middle or last) and birth date at the same time.”
(ES: No actualice su Nombre (primer, segundo o apellido) y fecha de naciemiento a la mismo tiempo.)

Legal First Name [textbox]

ES: Nombre legal [textbox]

CO MIS field SB31.

lastname

User’s last name used on legal documents.

VarChar 50

(extended character set, allowing hyphens, letters with diacritical marks or accents, etc.)

Text string; may be null

No

None

Stored in database for use in auto-population.

Required response; else error message, “Legal last name required.”
(ES: “Se requiere el apellido legal.”)

May not be changed at same time as birthdate (i.e., during the same ‘Save’); else error message, “Do not update your name (first, middle or last) and birth date at the same time.”
(ES: No actualice su Nombre (primer, segundo o apellido) y fecha de naciemiento a la mismo tiempo.)

Legal Last Name [textbox]

ES: Apellido legal [textbox]

CO MIS DED SB32

middlename

User’s middle name used on legal documents.

VarChar, 50

(extended character set, allowing hyphens, letters with diacritical marks or accents, etc.)

Text string; may be null

Yes

None

Stored for use in auto-population.

Optional response.

May not be changed at same time as birthdate (i.e., during the same ‘Save’); else error message, “Do not update your name (first, middle or last) and birth date at the same time.”
(ES: No actualice su Nombre (primer, segundo o apellido) y fecha de naciemiento a la mismo tiempo.)

Legal Middle Name [textbox]

ES: Segundo nombre legal [textbox]

CO MIS field SB31.

no_perm_address_homeless

noPermAddressHomeless

User indicates whether or not they have no permanent address because they are currently homeless.

Boolean

True/False

Always displays.

No

No

Stored for use in auto-population.

Required user response, else error message: “Are you currently homeless?” is required.
ES: “Está actualmente sin vivienda es requerido.”

If Yes, then do not display permanent address fields on screen and disable address validations.

If No, display “Country” field and require a response. If displayed, “United States” will appear as the default response option.

If Yes, then display optional checkbox question, "I have no current mailing address because I am currently homeless" in the Current Mailing section (Profile page) in CCCApply applications; else do NOT display checkbox question.

If Yes, then set default value to “Yes” in “Homeless Youth” question on Residency page in CCCApply Standard application (Note: <homeless_youth> doesn’t appear in the Noncredit workflow).

IF No, then clear values in <homeless_youth> question in Standard app (no default value is set).

Yes [radio button] No [radio button] “Are you currently homeless?”

ES: Si [radio button] No [radio button] “¿Está sin hogar actualmente?”

perm_country
perm_addr_country (International application)
country (CC Promise Grant applications)

permCountry

Country portion of the user’s permanent address.

Char, 2

US or other two-character ISO country code. See: https://www.iso.org/obp/ui/ #search.

Does not display if “Are you currently homeless?” = Yes.

No

No

Stored in database for use in auto-population.

Required response when “Are you currently homeless?” = No; else error message, “Country is required.”

Country [menu]

The Country field value is used in determining the U.S or non-U.S. residency for the applicant.

perm_streetaddress1
perm_streetaddress2

permStreetaddress1
permStreetaddress2

Street portions of user’s permanent address.

Varchar, 50

Two text strings; second may be null

No, if displayed (streetaddress1)
Yes, always (streetaddress2)

No

Stored in database for use in auto-population.

Does not display if “Are you currently homeless?” = Yes.

Response required for Street Address 1; else error message, “You must provide your street address.”

System will attempt to validate the street address using USPS Address Validation. If the address provided is not recognized, the address validation override message is displayed.

Street Address [text fields]

Street Address 2 [text fields]

perm_city

permCity

City portion of the user’s permanent address.

VarChar, 50

Text string

No

No

Stored in database for use in auto-population.

Does not display if “Are you currently homeless” = Yes.

Required user response; else error message, “City is required.”

City [textbox]

perm_state

State/province portion of user’s permanent address.

Char, 2

blank/null or 2-character USPS state code

Yes

No

Stored in database for use in auto-population.

Does not display if “Are you currently homeless” = Yes.

Required only if Country = United States (US); else error message, “State is required.”

State [textbox] (If Country = United States (US)

State/Province [textbox] (If Country is NOT United States)

perm_nonusaprovince

permNonusaprovince

State/province portion of the user’s non-U.S. permanent address.

Character varying (30)

Text string

Yes

No

Stored in database for use in auto-population.

Does not display if “Are you currently homeless” = Yes.

Required response if Country DOES NOT = United States (US); else error message, “Province is required.” 

State/Province [text box]

perm_postalcode

permPostalcode

Zip code (for U.S.) or Postal Code (if non-U.S.) portion of the user’s permanent address.

Character varying, 20

(extended character set, allowing hyphens, symbols, letters with diacritical marks or accents, etc.)

No

No

One field is stored.

Stored in database for use in auto-population. Included in Account Profile.

When “Are you currently homeless?” is Yes, THEN:

Zip Code field does not display.

Postal Code field does not display.

Required response.

Zip Code must not be empty if Country = United States (US); then error message, “Zip code is required.”

Postal Code must not be empty if Country is NOT the United States (US); else error message, “Postal code is required.”

Zip Code [textbox] (displays if Country = United States (US)

Postal Code [textbox] (displays if Country does NOT = United States (US)

perm_zip4

permZip4

System configured. The last four digits of the user’s permanent Zip code (for U.S.) or Postal Code (if non-U.S.).

Char 4

No

No

Stored in database for use in auto-population.

mainphone

User’s primary phone number.

Character varying, 19

Null or Text string

Yes

None

Used in account creation as a method to verify identity. Can be set as the user’s preferred method of contact by the California Community Colleges or an authorized partner.

Stored for auto-population in Edit Account Profile.

Both International and Domestic phone numbers are supported.

Always

International phone numbers must include a “+” in front of the country code.

Create Account: Optional response.

Must be properly formatted and meet validation check for domestic and international phone numbers; else error message, “Please enter a valid phone number”
(ES: “Por favor ingrese un número de teléfono válido.”)

Must be a valid mobile phone number if used for account creation; else error message, “Preferred phone must be mobile.”
(ES: “El teléfono preferido debe ser móvil.”)

Sign In: Must meet mobile number validation checks; else error message, “Please enter a valid phone number.” (ES: “Por favor ingrese un número de teléfono válido.”)

Edit Account: Must meet mobile number validation checks, else error message, “Please enter a valid phone number or remove phone type.”
ES: “Ingrese un número de teléfono válido o elimine el tipo de teléfono.”

Phone

[textbox]
“For international numbers insert + before country code”

(ES: “Teléfono”)
(ES: “Para números internacionales ingrese + antes del código de país”)

Create Account (Contact Information):
Primary Phone Number

[textbox]
“For international numbers insert + before country code”

(ES: “Para números internacionales ingrese + antes del código de país”)

Sign In Page: Email or mobile phone* [textbox]
(ES: Correo electrónico o teléfono móvil*)

Edit Account: Phone [textbox]

Create Account:
“Enter your mobile phone number to begin creating your California Community Colleges student account. You will receive a code via text message to verify your identity and keep your account secure.”

(ES: “Entra tu dirección de número de teléfono móvil para comenzar a crear su CCC cuenta. Recibirás un código a través de correo electrónico para verificar su identidad y mantener su cuenta segura.”)

Phone field (“mainphone” in CCCApply) now supports both domestic and international phone numbers.

If a mobile phone is Verified during account creation, the system will pre-populate the Phone and Phone Type fields so they don't have to enter them again during the remainder (Step 2) of the account creation process. Both fields will be disabled to prevent edits until the account creation process is complete.

Compliance with the Amazon SMS Regulations

To comply with the Amazon Text regulations for sending and receiving a SMS text message and/or security-related codes via text message, the following disclaimer appears under the Primary Phone Number field. (See “Additional Onscreen Text” above.)

“By providing your cell phone number, you consent to receiving periodic messages. Message frequency may vary. Message and data rates may apply. Text "HELP" for help. Text "STOP" to cancel.”

(ES: “Al proporcionar su número de teléfono celular, acepta recibir mensajes periódicos. La frecuencia de los mensajes puede variar. Se pueden aplicar tarifas por mensajes y datos. Envía "HELP" para obtener ayuda. Envía "STOP" para cancelar.”

mainphone_ext

mainphoneExt

NO LONGER IN USE
Previously identified an extension for applicant’s main telephone number.

char, 4

Null or numeric string; integer up to 9999

Yes

Stored in database.

DEPRECATED. Removed from OpenCCC Account beginning Jan 2022.

mainphone_auth_txt

mainphoneAuthText

NO LONGER IN USE
Previously identified the user’s permission to send text messages to the main telephone number.

boolean, 1

1 = Yes (checked)

0 = No (not checked)

Yes

Stored in database for reporting.

DEPRECATED. Removed from OpenCCC Account beginning Jan 2022.

mainphoneintl

mainphoneintl

NO LONGER IN USE
User’s international main telephone number.

Character varying, 25

Stored in database for reporting.

DEPRECATED. See “Phone Number” for collecting international numbers.

secondphone

second_phone_number (CCCApply International application)

secondphone

NO LONGER IN USE.
Previously identified the applicant’s optional second telephone number.

10 to 14 characters, numeric plus: (nnn) nnn-nnnn

Null or text string

Stored in database for use in reporting.

DEPRECATED. Removed from OpenCCC Account beginning Jan 2022.

secondphone_ext

secondphoneExt

NO LONGER IN USE.
Previously identified the user’s second telephone extension.

VarChar, 4

Integer up to 9999

Stored in database for use in reporting.

DEPRECATED. Removed from OpenCCC Account beginning Jan 2022.

secondphone_auth_txt

secondphoneAuthText

NO LONGER IN USE
Previously identified the user’s permission to send text messages to their second telephone number.

boolean, 1

1 = Yes (checked)

0 = No (not checked)

Yes

Stored in database for reporting.

[Checkbox] I authorize text messages to my second telephone number and accept responsibility for any charges that result.

DEPRECATED. See “Phone Number” for collecting international numbers.

secondphoneintl

secondphoneintl

NO LONGER IN USE
Previously identified the user’s international second telephone number.

Character varying, 25

Stored in database for reporting.

DEPRECATED. Removed from OpenCCC Account beginning Jan 2022.

phone_type

Type of phone number provided by the user.

Character varying. 10

= Mobile

= Landline

Yes

Default value = Mobile If mobile phone number is used for identity verification during account creation; else no default.

Stored in Account.

Must not be empty if phone number value exists; else error message, “Phone type required.”
ES: “Tipo de teléfono requerido.”

Phone Type [menu]
ES: Tipo de teléfono [menu]

See “Phone Number” field for related onscreen language.

“Landline” phone type cannot be used for account verification. DELIVERED via SuperGlue for Apply.

phone_verified

mainphoneVerified

Indicates that the user’s valid mobile phone number has been verified with a security code.

Boolean

True / False

Value stored in Account database with timestamp.

If mobile phone number is verified, an asterisk is displayed on the Mobile Phone label in the user’s Account Profile.

At least one method of contact must be verified.

DELIVERED via SuperGlue for Apply.

phone_verified_timestamp

mainphoneVerifiedTiimestamp

Date and time of the verification of user’s mobile phone number.

date timestamp with time zone

Stored with <phone_verified> at time of account creation.

DELIVERED via SuperGlue for Apply.

preferred_contact_method

preferredMethodOfContact

The user’s preferred method for receiving messages (calls, text messages, and/or email messages) from entities associated with the user’s application process, including but not limited to designated schools and programs.

Character varying 10

= email

= phone

No

Defaults to method used during account creation to verify user’s identity (Email or Phone).

Only one value is stored at a time but both methods can be verified.

User must have at least one verified method of contact. Can be updated.

User selects method during account creation to verify user identity (with security code for two-factor authentication). Preferred method of contact must be verified.

Preferred method can be updated after initial account creation.

User is Required to designate a preferred method of contact.

Create Account / Edit Account:
Preferred method selected must be verified using a valid security code; else error message, “Please select email or phone as your preferred contact method”
ES: “Seleccione correo electrónico o teléfono como su método de contacto preferido.”

If preferred method selected is not “email”, then <mainphone> must be a valid mobile phone; else error message: “Preferred phone must be mobile.”
(ES: “El teléfono preferido debe ser móvil.”)

Preferred Method of Contact*

ES: Método de contacto preferido*

Account Profile:

[Button] Preferred Method of Contact (ES: Método de contacto preferido)

[Button] Make preferred (ES: Hacer preferido)

User must have at least one verified method of contact. Can be updated.

Only one value is stored at a time, but both methods can be verified.

User selects method during account creation to verify user identity (with security code for two-factor authentication). Preferred method of contact must be verified.

Preferred method can be updated after initial account creation.

DELIVERED via SuperGlue for Apply.

9/20/2023:  Corrected data field value from = mobile to = phone.

preferred_name

New OpenCCC 2.0 field “Preferred Name” maps to the legacy field: <preferred_firstname>.

preferredName

User’s full preferred name.

Boolean

True/False

Yes

Values entered in Preferred Name field are stored in the <preferred_firstname> field in database.

Optional response.

Must not include a combination of first + middle + last + suffix; else error message, “Preferred name cannot equal first + middle + last + suffix.”
(ES: “El nombre preferido no puede ser igual al primer + segundo + apellido + sufijo.”)

Preferred Name [textbox]

ES: Nombre Preferido [textbox]

New format implemented with OpenCCC 2.0 (Jan 2022): One, optional text field called “Preferred Name”.

If user enters a preferred name, the values will populate the <preferred_firstname> (preferredFirstname) field in the downloads and/or SuperGlue for Apply. 

preferred_firstname

New OpenCCC 2.0 field “Preferred Name” maps to this field: <preferred_firstname>.

preferredFirstname

User’s full preferred name.

VarChar, 50

(extended character set, allowing hyphens, letters with diacritical marks or accents, etc.)

Text string

Yes

No

New OpenCCC Account field “Preferred Name” maps to the legacy <preferred_firstname> field.

Optional response.

Must not include a combination of first + middle + last + suffix; else error message, “Preferred name cannot equal first + middle + last + suffix.”
(ES: “El nombre preferido no puede ser igual al primer + segundo + apellido + sufijo.”)

Preferred Name [textbox]

ES: Nombre Preferido [textbox]

New format implemented with OpenCCC 2.0 (Jan 2022): one, optional text field called “Preferred Name”.

preferred_middlename

preferredMiddlename

NO LONGER IN USE.

Previously identified the applicant’s preferred middle name.

Character varying, 50

(Extended character set, allowing hyphens, letters with diacritical marks or accents, etc.)

Text string

Yes

Stored in database.

NO LONGER IN USE.

preferred_lastname

preferredLastname

NO LONGER IN USE.

Previously identified the applicant’s preferred last name.

char, 50

(Extended character set, allowing hyphens, letters with diacritical marks or accents, etc.)

Text string

Yes

Stored in database for reporting.

NO LONGER IN USE. Removed from OpenCCC Account beginning Jan 2022.

Password

N/A

RESTRICTED FIELD.
User’s secure password credential used for Account sign-in and recovery.

VarChar, 25

Two input fields: must match and must be at least 8 characters, alphanumeric.

text string

No

RESTRICTED. NOT AVAILABLE FOR DELIVERY OR REPORTING.

Stored using reversible encryption scheme. Used for comparison purposes but never transmitted.

Always masked on screen, including when typed.

Normalized for storage and comparison so that Password is case-insensitive.

Required response; else error message, “Password required.” (ES: “Se requiere contraseña.”)

Confirm Password is a required response; else error message, “Confirm Password required.” (ES: “Confirme la contraseña requerida.”)

Two entries must match and must be at least 8 characters, alphanumeric; else error message, “Passwords do not match.” (ES: Las contraseñas no coinciden.)

Must meet length and format requirements; else error message, ”

Must meet all input validity checks; else error message, “Invalid password. Please follow the format in the description.”

Cannot include the <username> (legacy user) in the Password; else error message, “For security reasons, your Password cannot contain your Username. Please choose another Password.”

Format requirements must meet the following specifications:

At least 8 characters.

At least one uppercase letter.

At least one lower case letter.

At least one number.

At least one of these special characters (!,@,#,$,%,^,&,*).

Cannot contain any part of your name

Must be a unique password each time a user resets it. Password cannot be one you have already used

Your Password must be at least 8 characters in length, must contain upper and lowercase letters, and must have at least one number and one special character (!,@,#,$,%,^,&,*). It cannot contain any part of your name.

Restricted field.  Not available for delivery or reporting.

The password is set/saved in the database when the system creates the user/CCCID.

The password can't contain any of the whole names in the password otherwise it would lead to too much complexity.

suffiX

suffix

Suffix to user’s legal name.

VarChar, 3

alphanumeric

JR

SR

II

III

IV

Yes

None

Optional user response

Suffix [menu] : (Jr. Sr., I, I, III, IV)

username

N/A

RESTRICTED
Legacy Username credential used for account recovery.

VarChar, 128

6 to 128 keyboard characters (ASCII 33-126: alphanumeric plus punctuation, no spaces).

Valid alphanumeric string

RESTRICTED. NOT AVAILABLE FOR DELIVERY OR REPORTING.

Used for legacy account recovery only.

Must be unique (i.e., not already in use for another account); else error message: “Invalid username”.

Must not be blank, fewer than six characters, include spaces, or characters other than numbers, letters, or the following special characters: !#%&()*+,-./:; =? @[]^_`{} ~. else error message, “Invalid username.”

Username [textbox] (ES: Nombre de Usuario)

RESTRICTED.  Used for legacy account recovery only. Not available for delivery or reporting

The $, |, <, and > characters are not allowed in either the user name or password.