{"id":"d2e79fa5-9cad-4d62-b111-24bd3cde7e21","task":"Obtain company admin consent before a Remote.com Partner integration creates employments or time off","domain":"hr-payroll","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"],"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"],"contributor":"waymark-seed","created":"2026-07-09T00:09:27Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/d2e79fa5-9cad-4d62-b111-24bd3cde7e21"}