Create and Use Data Fields in OnRamp
Updated
Data Fields let you store custom, structured information across OnRamp β at the account, project, playbook, task, or user level. They power automations, CRM sync, reporting, and personalization for details unique to your business process, like region, renewal date, or implementation manager.
Accessing Data Field Settings
To create and manage data fields, go to Settings > Data Fields. This page shows all fields currently configured in your workspace. From here you can search for existing fields, filter by location or type, toggle between active and archived fields, and create, edit, or archive fields.
Understanding the Data Fields List
Each row in the list describes how a field is configured:
Name β the label used throughout OnRamp
Location β the object the field is attached to (Project, Account, Task, etc.)
Type β the field format (Dropdown, Date, Text, etc.)
Add on Creation β whether the field is automatically added when a new object of that type is created
Required β whether the field must be filled in before saving
Edit Rights β which user roles can update the field
Use Count β how many objects currently have this field, useful for gauging impact before editing or archiving
You can filter the list by Location (Internal User, Customer User, Account, Playbook, Project, Module, Task) or by Field Type, and toggle between Active and Archived fields at the top of the page.
Creating a Data Field
Who can do this: Super Admins, Creators and Integrators
Go to Settings > Data fields.
Select New data field in the upper right corner.
Fill out the form:
Name β a clear label (for example, "Internal Onboarding Status")
Description β context so teammates know how to use it
Object type β where the field belongs: Account, Internal user, Customer user, Playbook, Project, Module, or Task
Field type β see field type reference below
Name, Object type and Field type are required. You can't change Object type or Field type after the field is created.
4. Configure additional options:
Default value β pre-populates the field until changed. It's offered for every field type except Dropdown, Multi-Select and User. Link fields have Default link instead.
Required value β toggle on to mark the field as required
Add on creation β toggle on to auto-include this field whenever a new record of that type is created
User edit rights β select the seat licenses that can edit this field: All seat licenses (the default), None (locked), or specific seat licenses. This applies only to manual editing in the app. API and integration access isn't affected.
Select Save field.
Create a formula field
This feature is available when it's turned on for your organization. If you don't see it, contact your OnRamp team.
A formula field holds a calculated value. OnRamp calculates the value and the field is read-only.
Go to Settings > Data fields.
Select New formula field.
Enter a Field name and Description (optional).
Under Applies to, choose Projects or Accounts.
Under Function, choose Days between two dates or Math on numbers, then set its inputs.
Select Create field.
For what each function takes as inputs, when values update, and tips, see Formula Fields: Let OnRamp Calculate a Value for You.
Field Types
Choose the type that matches how the data will be used:
Dropdown β single selection from a predefined list; best for consistent values used in reporting and automation. Needs at least two options, and you can give each option a color.
Multi-Select β select multiple values from a list. Needs at least two options, and you can give each option a color. Use this instead of multiple boolean fields when tracking several values at once (for example, product lines, regions).
Text β free-form text input
User β links to an OnRamp user; useful for tracking ownership
Date β date picker
Number β numeric value
Currency β monetary value. You must choose a Currency, which defaults to USD.
Color β color selection
Link β a clickable URL
Using Data Fields on Objects
Open a Project, Playbook, or Task and go to the Data Fields tab.
Select a field value to edit it β changes save automatically.
To add a field that wasn't included by default, select + Add Optional Data Field.
You can also edit project data fields directly from the project list view without opening individual projects β select the pencil icon on any row to edit a single field, or select multiple projects to bulk-edit fields at once.
Field Visibility in the Project List
Each field on the Data Fields tab has a visibility toggle that controls whether it appears in the header of the List tab inside that project:
Green eye β field appears above the task list for quick reference while working in the project
Red eye with line β field is hidden from the list header but still exists in the Data Fields tab and continues to power automations and reporting
Use visible fields for information your team references frequently (for example, Go-Live Goal Date, Customer Segment). Hide fields used only for automation or reporting.
Editing and Archiving Fields
From a field's row menu in the Data fields list, select Edit field or Archive field. For an archived field, select Unarchive field. Fields managed by Journeys have no row menu.
Formula fields open the formula dialog when you edit them. Their Edit field option is unavailable when formula fields are turned off for your organization or the field is archived.
Archiving keeps existing values and stops the field from being added to new objects. It also removes the field from views, and unarchiving adds it back. Before archiving, check the field's Use count. Select the count to see the objects that use the field.
Tips
Not sure which Object type to use? Use Account if you want the field tied to the customer across multiple projects.
Want consistency? Enable Add on Creation at the Playbook level so fields are included every time you launch a new project.
CRM sync: Align Data Fields with Salesforce or HubSpot fields to keep systems in sync automatically.
Restricting edits? Use Edit Permissions to limit sensitive fields (like contract value or renewal date) to specific roles.
Create fields only when they serve a clear purpose and use consistent naming conventions β well-structured fields make reporting and automation far easier to maintain.