Vendors Custom Role and Permissions
Overview
Available on Ramp Plus. See Ramp Plus overview for plan details.
Custom Roles allow admins to customize the specific permissions of each role across the different product areas on the platform.
The Vendors permission group lets admins give users targeted access to vendor management in Ramp without giving them full Admin access. You can use these permissions on a customizable built-in role or add them to a Custom Role when someone needs to view vendors, manage vendor records, or work with vendor contracts.
To get started:
- Go to Company > Settings > Roles & permissions to edit role permissions.
- You can apply these permissions to a customizable built-in role, or to a Custom Role if only a subset of users needs vendor access.
- For users without Admin access, account-wide vendor permissions can still be limited by additional access restrictions. Permissions scoped to owned vendors can also include vendors owned by the user's reports and vendors the user has been granted edit access to.
- For a complete breakdown of permissions across all product areas, see Customizing Roles and Permissions.
How to configure vendors permissions
- Go to Company > Settings > Roles & permissions.
- Select the role you want to update, or create a Custom Role.
- Scroll to the Vendors permission group.
- Turn the relevant permissions on or off. If a permission includes a scope dropdown, choose the scope you want to apply.
- Click Save changes.
Vendors permissions
- View all vendors: allows users to open the Vendors page and view vendor profiles across your account. For users without Admin access, profiles with additional access restrictions are excluded unless the user has been granted access.
- Edit details on vendors they own: allows users to update vendors they own, vendors owned by their reports, and vendors they have been granted edit access to.
- Create and delete any vendor: allows users to create vendor records and delete vendors.
- Delete vendors they own: allows users to delete vendors they own, vendors owned by their reports, and vendors they have been granted edit access to.
- Edit details on all vendors: allows users to update vendor records across the company. For users without Admin access, vendors with additional access restrictions are excluded unless the user has been granted edit access.
- Edit vendor payment & tax details: allows users to update vendor payment details and tax details.
- If you want users to see this information without editing it, use View vendor payment & tax details.
- View vendor documents: allows users to open non-tax documents stored on vendor profiles, such as contracts. Viewing tax forms also requires View vendor payment & tax details.
- Request payment details and onboarding forms from vendors: allows users to send vendors requests for payment details and onboarding forms from Ramp.
- Merge vendor contracts: does not separately control contract merging. Contract merging uses Modify vendor contracts and renewal information.
- Modify vendor contracts and renewal information: allows users to update contract details and renewal information.
- View vendor contracts and renewal information: allows users to view contract details and renewal information.
- Price Intelligence: Allows users to access Ramp’s Price Intelligence for supported vendors.
- Seat Intelligence: allows users with an active License Intelligence integration to access license usage data in the vendor experience.
Frequently asked questions
Can I let someone create vendors without also letting them delete vendors?
No. The Create and delete any vendor permission is bundled, so it is not possible to grant vendor creation without also granting vendor deletion.
What’s the difference between owned-vendor permissions and all-vendor permissions?
Owned-vendor permissions can include vendors the user owns, vendors owned by their reports, and vendors they have been granted edit access to. All-vendor permissions apply across your account. For users without Admin access, additional access restrictions can still limit access.
When should I use a Custom Role instead of editing a built-in role?
Use a Custom Role when only certain users need this vendor access. If every user with a built-in role should get the same Vendors permissions, you can update that built-in role instead.