RMS Cloud access guide

How to access your RMS Cloud account

This guide walks through, step by step, how to sign in to the RMS Cloud platform, retrieve your API credentials and restore access when you are locked out. Instructions cover both the connection from Cloudrms and the most common incidents property administrators run into.

Updated: June 2026 Reading time: 8 minutes Audience: RMS Cloud administrators

Note: Cloudrms is an independent third-party service and is not affiliated with RMS Cloud Pty Ltd This guide describes the general procedure based on publicly available information. Menu labels and the exact navigation path may differ depending on your RMS Cloud plan, the version installed and your property configuration. If in doubt, contact RMS Cloud support directly.

Signing in to your RMS Cloud account

Follow these six steps to open your RMS Cloud workspace, retrieve your API credentials and run a first synchronisation with your Cloudrms modules.

Step 1 — Open the RMS Cloud access URL

Go to the URL RMS Cloud provided when your property was onboarded. It usually takes the form https://[yourhotel].rmscloud.com or https://app.rmscloud.com/[yourhotel]. If you cannot find it, the onboarding email from RMS Cloud contains it as well. Open the page in a recent browser (an up-to-date Chrome, Firefox or Edge) to avoid any certificate-related blocks.

Step 2 — Enter your administrator credentials

Enter your RMS Cloud identifier (typically the business email address attached to the property) and the password set at account creation. If two-factor authentication is enabled on your account, keep your authenticator app or SMS code ready before you submit. Cloudrms has no access to your RMS Cloud password or your 2FA codes.

Step 3 — Open the Administration module

Once signed in, open the Administration or Settings menu depending on your version. Depending on the RMS Cloud release deployed on your account, the path may be: Administration → Integrations → API Access, Settings → External Integrations → Developer API, or Configuration → API → Generate Credentials. If no API entry is visible, your profile lacks the required rights — ask your property's main administrator to grant them.

Step 4 — Generate or retrieve your API key

In the API Access section, click "Generate a new key" or view the existing key. Copy the full key and the associated endpoint URL immediately: most RMS Cloud releases only reveal the key once. Store both values in an enterprise password manager, never in a shared text file.

Step 5 — Paste the credentials into Cloudrms

Open your Cloudrms Client Area, go to Settings → Connected RMS Cloud Account, and paste the API key and endpoint URL into the fields provided. Click "Test connection": Cloudrms calls the RMS Cloud API and displays your property name, room types and detected permissions. This step does not yet change any data in RMS Cloud.

Step 6 — Activate modules and monitor connectivity

Once the connection is validated, activate each of the modules you need (Booking Engine Multi-Language, Channel Manager Sync, Guest CRM, and so on) individually from the Cloudrms catalogue. The dashboard continuously shows the state of the RMS Cloud link and alerts you by email if synchronisation is interrupted. Review the permissions once a quarter to keep flows stable.

Common problems

The five incidents below account for the majority of the support requests received by Cloudrms. Check the matching remedy before opening a ticket.

Forgotten password

Use the "Forgot password" link on the RMS Cloud access page. A reset email is sent to the address linked to your administrator profile. If the email does not arrive within 15 minutes, check the spam folder and confirm with your IT team that no filter is blocking the RMS Cloud sender domain. Cloudrms cannot reset a RMS Cloud password on your behalf under any circumstances.

API key not visible

If the "API" entry does not appear in the Administration menu, your RMS Cloud plan probably does not include API access. Contact your RMS Cloud account manager to confirm eligibility. Another common cause: the key was generated by another administrator and never shared. Generate a new one and remove the old to preserve traceability.

Insufficient permissions

A "permission denied" error during the connection test means your key does not include all the required scopes. For most Cloudrms modules you need at minimum: Read reservations, Read rates, Write rates, Read guest profiles and Write guest profiles. The PDF Invoicing module additionally requires read access to night-audit data. Edit the key in RMS Cloud to add the missing scopes and re-run the test.

Expired session

RMS Cloud automatically logs out inactive sessions after 30 minutes. If you are redirected to the authentication screen mid-configuration, sign in again and pick up at step 3: unsaved changes will be lost. For long operations (room mapping, rate plan imports) prepare all your data ahead of time and save regularly to avoid data loss.

Broken 2FA

If you have changed phones or lost access to your authenticator app, RMS Cloud requires a manual reset through its own support desk. Prepare your RMS Cloud property identifier and ID for the person named on the administrator account. The reset typically takes 24 to 48 business hours — do not disable 2FA permanently, it remains the strongest protection against credential theft.

Need help with your RMS Cloud account?

Cloudrms supports users on the link between Cloudrms modules and RMS Cloud. For issues internal to the RMS Cloud platform itself — password reset, plan upgrade to enable API access, questions about the available functionality — contact the RMS Cloud support desk directly on the official RMS Cloud website.

Cloudrms support can be reached at support@cloudrms.org or by phone on +61 2 8756 3421. Our team is available Monday to Friday, 09:00–17:00 AEST, from our offices at 42 Pitt Street, Level 8, Sydney NSW 2000, Australia. When writing about a RMS Cloud API connection, please include the email on your Cloudrms account, the name of the affected module and the full error message shown in your dashboard.