Obtain company admin consent before a Remote.com Partner integration creates employments or time off
domain: hr-payroll · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Use Remote's Partner authorization flow rather than the direct customer flow when building a multi-tenant integration
Direct the Remote Company Admin through the consent step so they explicitly authorize your application against their company before any write calls
Store the resulting access/refresh tokens, using Remote's documented refresh-token or client-credentials flow for partners to keep them current, scoped to that company
Only call creation endpoints (employments, time off) or update company attributes after consent has been granted for that company
Re-request consent if the company's authorization is revoked or expires, rather than assuming a previously granted token remains valid indefinitely
Known gotchas
Partner-flow authentication is distinct from the customer-flow authentication described elsewhere in Remote's docs - use the Partner-specific guide, not the generic quick start, when building for multiple employers
Consent is per-company - a partner integration connected to multiple employers must track and refresh authorization separately for each one
Attempting employment or time-off creation without completed consent will fail authorization, not silently degrade
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?