Internal users and customer users
Updated
OnRamp has two kinds of users. Internal users are people in your OnRamp organization. Customer users are people at your customers' organizations who work in the customer portal.
When to use it
Read this when you're deciding who to add to OnRamp, or when you need to find someone and see what they're involved in.
How it works
The Users page
Go to Users to see everyone in your organization. A toggle at the top switches between Internal and Customer.
Each list has an Active and Inactive switch that shows how many users are in each. You can search, filter, save filters and choose columns, including user data fields.
Contributors can't open the Users page.
Internal users
Internal users are your team: CSMs, onboarding managers, RevOps and anyone else who works in OnRamp. Each internal user takes up a seat license, and your organization can only add as many as its contract allows.
What an internal user can do depends on their seat license: Super Admin, Creator, Contributor, Collaborator or Integrator. For example, a Creator builds playbooks, and a Contributor works on the projects and tasks they're given. For what each seat license allows, see Seat licenses and permissions.
Super Admins add internal users from Users > Internal by selecting Add Internal User. The form asks for First Name, Last Name, Email Address and a Seat License. Job Title is optional. When you select Save, OnRamp creates the user and sends them an invitation to join.
If your organization manages users outside OnRamp through single sign-on, the Internal list shows Sync Users in place of Add Internal User, and you can't add users in OnRamp. For how that's set up, see Set up Azure SSO. To add many users at once, see Import users in bulk into OnRamp.
Customer users
Customer users belong to an account. When you edit a customer user, Account is a required field, and you can create an account from that field.
Customer users are added in a few ways:
By a workflow. In a workflow's Project Customer Users card, map the CRM contact's email, first name and last name fields. When the workflow creates the project, OnRamp creates a customer user if the record has a valid email, a first name and a last name, and no customer user with that email exists yet. If one already exists, OnRamp uses that customer user.
By another customer user. In the customer portal, customer users can select Invite to add a colleague to the project. The button is turned off when your organization manages users outside OnRamp through single sign-on. In a team widget, it appears only when that widget allows invites.
By your team. See Add customer users to a project.
User profiles
Select a user to open their profile. Every profile has Projects, Tasks, Comments, Activity and Data Fields tabs. Projects and Tasks show only to people with permission to view customer users.
Internal user profiles also have To-dos and Notes, which need that same permission. They can also show:
Time, when time tracking is turned on and you have permission to view timesheets.
Access Control, for people with permission to view access-control role assignments.
Groups, when user groups are turned on for your organization and you have permission to view groups. Contributors don't see it.
If you have permission to view integration connections, the details card has a CRM records section listing the CRM records linked to the user. For a customer user, the details card also shows their account.
Limits
Whether an internal user can create projects or build playbooks depends on their seat license, not on being an internal user.
Only Super Admins can add internal users in OnRamp, and only when single sign-on doesn't manage your users.
To remove someone's access, deactivate them. For the steps when someone leaves your team, see Offboard an internal user in OnRamp.