Accounts in OnRamp
Last updated: February 18, 2026
Accounts are the foundation of your customer records in OnRamp.
They group together:
Projects
Users
Notes
Data fields
CRM connections
Branding elements (like logos)
Think of an Account as the container for everything related to a single customer.
What Is an Account?
An Account represents a customer company in OnRamp.
Every project must belong to an Account.
Every customer user belongs to an Account.
This keeps reporting, visibility, and CRM syncing aligned.
How Accounts Are Created
There are three primary ways Accounts get created.
1⃣ Manually Create an Account
You can create an Account directly inside OnRamp.
To create one manually:
Navigate to Accounts in the left-hand menu
Click + Create
Enter the account name and details
Save
You can later link this Account to a CRM record through your integration.
Best for:
Internal-only projects
One-off onboarding
Pre-CRM setup
2⃣ Automatically via Workflow (CRM-Driven)
If you're using Workflows for project automation:
When your CRM trigger runs and creates a project:
OnRamp will automatically associate it with an existing Account
Or create a new Account if one doesn’t exist
This keeps CRM and OnRamp aligned without manual effort.
Best for:
Scaled onboarding
Closed-won automation
Standardized implementation processes
3⃣ On the Fly During Project Creation
When manually creating a project, you can create an Account in the same step.
In the Account field:
Start typing the company name
If it doesn’t exist, select Create Customer
OnRamp instantly creates the Account and assigns the project to it.
Best for:
Quick starts
One-off projects
Early-stage customer setup
What Lives Inside an Account
Accounts are more than just a name.
📁 Projects
The Projects tab shows:
Active projects
Completed projects
Archived projects
This gives you a full lifecycle view of the customer relationship.
👥 Users
The Users tab shows:
All internal users associated with the account
All customer users invited to projects
This makes it easy to see:
Who has access
Who’s participating
Who may need to be added or removed
📝 Notes
Use account-level Notes to:
Capture strategic context
Log relationship updates
Record high-level discussions
These sit above any one project.
🗂 Data Fields
Accounts can store custom data fields such as:
Industry
Segment
Contract Type
Customer Tier
These can be used for reporting.
🖼 Account Logo
You can upload a logo to an Account.
That logo:
Appears in the customer portal
Improves branding
Creates a more polished experience
It’s a small touch that makes onboarding feel more intentional.
🔗 External Object Link (CRM)
If connected to Salesforce or HubSpot:
The Account can display its linked CRM record.
This allows:
Workflow alignment
Clean data reporting
Why Accounts Matter
Strong Account structure enables:
Clean CRM integration
Accurate reporting
Better portal branding
Clear user grouping
Organized project history
Without Accounts, everything becomes fragmented.
With them, everything stays aligned.
Best Practices
✔ Always confirm Account mapping in Workflows
✔ Upload logos for customer-facing polish
✔ Use Account data fields for segmentation
✔ Avoid duplicate Accounts (especially when using automation)
✔ Link to CRM early for clean syncing
Accounts are simple — but they’re structural.
Get them right, and everything else in OnRamp runs smoother.