Integration · Current RMS

Current RMS

TAO connects to Current RMS so equipment rental and event-production teams can pull inventory, opportunities, and bookings into TAO's job and quoting flow. Current RMS supports OAuth 2.0 for end-user-installed apps and subdomain-scoped API keys for back-office automations — TAO uses OAuth where it's available and falls back to API keys only when a customer explicitly provisions one, with clear warnings about the broader access an API key grants.

Apply for Beta All data & permissions

How the connection works

Two paths. Preferred: OAuth 2.0 against the customer's Current RMS subdomain, with the customer granting TAO access to a specific account. Fallback: a subdomain-scoped API access token generated by the customer in System Setup → API Access. API keys carry the full permissions of the user who created them, so TAO requires the customer to provision a dedicated integration user with the narrowest role that still covers the connected features.

Scopes TAO requests

We request only the scopes the connected features actually use. Each scope, why we ask for it, and which tier it sits in for Current RMS:

ScopeTierWhat it's for

inventory.readreadRead product, asset, and stock-level data to drive TAO availability checks

opportunities.readreadRead opportunities and quotes so TAO can mirror the rental pipeline

opportunities.writewriteCreate and update opportunities raised from TAO jobs (optional, off by default)

contacts.readreadRead organisations and contacts to keep TAO's contact graph aligned

bookings.readreadRead confirmed bookings, check-outs, and check-ins for the TAO calendar

documents.readreadRead quote and invoice documents to attach to TAO records

What TAO accesses

The connected features read specific Current RMS data — and only what's needed for the operational record visible inside TAO.

Inventory, assets, and stock levels for availability and quoting inside TAO
Opportunities, quotes, and bookings linked to active TAO jobs
Organisations and contacts so TAO's contact graph stays in sync with Current RMS
Quote and invoice documents linked from TAO records

What TAO never does with this data

Some commitments are easier to read as a list.

We do not train models on your inventory, customer, or financial data
We do not sell, rent, or transfer your data to third parties or data brokers
We do not modify system settings, user roles, or billing inside Current RMS
We do not retain a full inventory copy — only the records linked to active TAO jobs
When connected via API key, TAO refuses calls that fall outside the documented scopes above even if the key technically permits them

Use of data — disclosure

TAO uses Current RMS data only to deliver the rental and event-production workflows visible inside TAO. API keys in Current RMS inherit the permissions of the user who created them; where a customer connects via API key rather than OAuth, TAO clearly flags this broader access in the connection screen and recommends provisioning a dedicated integration user with the narrowest role that still covers the features in use. We don't sell your data, we don't train models on it, and we don't transfer it outside TAO except where you initiate the transfer or law requires it.

OAuth consent screen + listing

The exact configuration TAO submits to Current RMS for every customer connection — keep this aligned with the public site for reviewers and consent dialogs.

Subdomain = the customer's Current RMS subdomain, captured during connect
Connection name = TAO Integration, visible inside Current RMS System Setup → API Access
Privacy policy URL = https://theartificialorganisation.com/privacy presented in TAO's connect dialog
When using OAuth, scope list is shown in plain language at consent time
When using an API key, TAO warns about the broader access and recommends a dedicated integration user

Verification + review path

Current RMS does not operate a formal app marketplace verification programme on the scale of Google or Microsoft. TAO aligns with Current RMS's published partnership and Open API documentation, runs against a sandbox account before production, and reviews each customer connection for least-privilege role assignment. We re-check our integration against Current RMS's API changelog quarterly so breaking changes don't surprise customers.

How to disconnect

Inside Current RMS, go to System Setup → API Access, find the TAO token, and click Revoke (or delete the dedicated integration user). Inside TAO, go to Settings → Integrations → Current RMS → Disconnect; TAO stops calling the API immediately and permanently deletes cached Current RMS data within 24 hours.

Reference: Current RMS developer documentation

Canonical Current RMS reference: https://www.current-rms.com/latest-features/current-rms-open-api

See also the full Data & Permissions page for the side-by-side comparison across all providers TAO connects to, and the Privacy Policy for retention, deletion, and your rights.

Want to see this running on the apps you already use? Apply for the beta, or tell us what your team is trying to run from one place.