Creating an Outbound VPN access to a company - is this correct?

[ojosaghae]

Hi everyone. Trust y'all are doing fine.
I have a working pfSense router with OpenVPN set up in the office such that I can connect remotely to the office LAN and check on the infrastructure.

However, we have a partner company that requires us to provide Public IPs for them to whitelist before we can connect to their infrastructure. The way we're going about it is giving them our pfSense's public IP, then configure our users (predominantly remote) to connect to the company via our pfSense's OpenVPN set up.

What I've done: I've created user credentials for our users, used the OpenVPN wizard to set up remote access for them, and downloaded their client .ovpn profiles.

My ask: is that all I need to do; like, if I share the .ovpn profiles (along with their pfSense credentials), is that enough for them to use for the case above? or am I missing something else?
I'm asking because I saw a sequence of steps to create an outbound VPN that requires me creating clients by going to VPN >> OpenVPN >> Clients and setting up the clients that way.
I already have a working remote access VPN configuration and I don't want to break anything. Is this necessary?

Thank you.

[The Party of Hell No]

@ojosaghae
Clients in VPN - OpenVPN - Clients - are for VPN services like SurfShark, NordVPN. ExpressVPN.. where the connections you create to these services would show as clients. I think you are running your own OpenVPN server for "Road Warrior" access. So no, if I am correct in my perspective.

However if you want to assign a specific IP to each "Road Warrior" device you can us the "Client Specific Overrides" - VPN - OpenVPN - Client Specific Overrides.