CS Gold: Door Access
Last updated: October 5, 2026
Housing.Cloud is capable of generating a Door Access CSV file with the intent of being consumed by CS Gold. The CSV transmission process will follow Housing.Cloud's standard SFTP process.
Configuration
- Institution will provide their CS Gold Site ID
- Institution will specify the transfer cadence of the file (e.g. every 30 minutes)
- The cadence can be any value supported by a Cron string, but it must be equal to or greater than every 10 minutes
File Format
| Column Header | Data Type | Description |
| PRIMARYKEYVALUE | string | A Resident's sisId in Housing.Cloud |
| OCCUPANCY_START | date string | The date in which a Resident checked in |
| OCCUPANCY_END | date string | The date of the Occupancy end, or the date when a Resident checked out * |
| SITE_ID | string | Pass through value provided by Institution |
| BUILDING_ID | string | Building id in Housing.Cloud |
| FLOOR_ID | string | Floor name in Housing.Cloud |
| SUITE_ID | string | Suite name in Housing.Cloud |
| ROOM_ID | string | Room name in Housing.Cloud |
Data Type Clarifications:
- Date String will be an ISO date string using the format:
yyyy-mm-ddTHH:MM:SS.MSZ - It is possible that
FLOOR_IDandSUITE_IDare empty strings as those Inventory Levels are not required in Housing.Cloud. If those levels exist in Housing.Cloud, those fields will be populated in the file
Notes:
- By default, an Occupancy will appear in the file as soon as the Resident is checked in
- A configuration such that an Occupancy will appear in the file as soon as the Occupancy is created in Housing.Cloud
- By default
OCCUPANCY_ENDwill be set to the Occupancy end date, until the Resident is checked out. As soon as the Resident is checked out, theOCCUPANCY_ENDdate will be the check out date * - If your institution utilizes Ethos to connect Housing.Cloud to your SIS, the inventory naming pattern in CS Gold's Access Map must match the inventory naming pattern in your SIS. This is not an issue if your institution utilizes SFTP.