Connect Ramp so Coworker can reason about company spend. Ramp is admin-connected once with OAuth client credentials — there is no per-employee connection, because a Ramp credential always sees the whole business's spend.
What Coworker can do with Ramp
Index card transactions, accounts-payable bills, employee reimbursements, spend limits (budgets), spend programs, cards, statements, suppliers, departments, locations and the people in your Ramp account
Produce one company-wide spend digest per period: what settled versus what is still pending, which people and categories drove it, declined charges worth a second look, bills moving through approval and payment, and the budgets closest to their ceiling. A quiet period produces nothing.
Answer spend questions on demand — how much was spent on a category last month, how much budget is left, why a card was declined, or what is owed to a specific supplier
Ramp is read-only in Coworker. There are no tools to move money, issue a card, change a budget or approve a bill.
Before you start
You must be a Coworker Network Admin
A Ramp finance admin needs to create a Ramp application and issue a client ID and client secret with the required read scopes
Ramp sandbox and production use different API hosts and credentials — know which one you are connecting
Connect as an admin
Open Data Sources from the admin settings in Coworker and select Ramp.
Enter the client ID and client secret from your Ramp application.
Enter the API base URL for the environment you are connecting (production or sandbox).
Save. Coworker exchanges the pair for short-lived machine tokens on every call.
Grant Ramp access to the specific people who should see spend data — the policy starts with no members.
Connect as a member
Ramp has no per-user connect flow. Members get access to Ramp data only when an admin explicitly grants it.
Good to know
Every amount, balance, budget and supplier-owner record sits behind a single private Ramp access policy that starts empty, so spend data is visible to nobody until an admin grants access. A "you do not have access to Ramp data" answer is a real permission result, not an error.
The deliberate exception is names. People in Ramp become the same Person entities the rest of Coworker knows, and true accounts-payable suppliers become Customer entities whose names are organization-visible — while everything financial about them is not.
Ramp's manager field draws reporting lines between people, making it a useful second opinion on your org chart.
Card merchants are not suppliers. Ramp auto-creates a vendor record for every merchant a card touches, so only true accounts-payable vendors become entities — roughly 5% of the raw vendor list.
Transactions, bills, reimbursements, cards, statements and spend limits stay in the raw store rather than the graph. A card swipe is an event, not a permanent node.
A successful token exchange does not guarantee every endpoint is authorized. Missing scopes show up as endpoint-specific permission errors, which are fixed in the Ramp application.