How to access your SabeeApp workspace.
A clear walkthrough of the SabeeApp sign-in flow, followed by the OAuth binding to your Sabeemod workspace. Should take under five minutes.
Part 1 — Sign in to SabeeApp
SabeeApp is signed into at the standard SabeeApp URL your property was given when the account was created. If you no longer have that URL, you can recover it in three ways: check the welcome email SabeeApp sent when your property was activated (subject typically "Welcome to SabeeApp"); ask your SabeeApp account manager; or contact SabeeApp support directly, who will identify your account from your property name and email you the exact URL.
Step 1 — Open the SabeeApp sign-in page
Type the SabeeApp URL for your property into the browser address bar. The URL is usually of the form yourproperty.sabeeapp.com or similar; do not add extra path segments. If you have bookmarked the workspace on a previous browser, use that bookmark to avoid typing errors.
Step 2 — Enter your email address
Use the business email address associated with your SabeeApp user. If two people share the same operational address, log in with your own personal user, not with a shared account. Sharing SabeeApp credentials breaches the SabeeApp Terms and prevents Sabeemod modules from attributing changes correctly.
Step 3 — Enter your password
Enter the password associated with your SabeeApp user. If you have forgotten it, use the "Forgot password" link on the SabeeApp sign-in page — SabeeApp will email you a reset link. If you have enrolled in SabeeApp two-factor authentication (recommended), enter the six-digit code from your authenticator app on the next screen.
Step 4 — Confirm you are on the right property
Once signed in, look at the top-right corner of SabeeApp: the property name displayed there is the SabeeApp account you are now signed into. If you manage several properties, use the property switcher to select the one you intend to work on today. This step matters because the OAuth binding in Part 2 attaches Sabeemod modules to the currently selected property.
Part 2 — Bind your Sabeemod workspace
Once you are signed in to SabeeApp, you can bind that SabeeApp account to your Sabeemod workspace so that Sabeemod modules read and write through the official SabeeApp API.
Step 5 — Open your Sabeemod workspace
Go to the Access your workspace page on sabeemod.org and enter the business email registered on your Sabeemod account. A secure sign-in link arrives within a few minutes — click it to open the workspace.
Step 6 — Start the OAuth flow
Inside the workspace, go to Settings → SabeeApp connection → Connect a new SabeeApp account. Click "Sign in with SabeeApp". You are redirected to the SabeeApp OAuth consent page.
Step 7 — Approve the requested scopes
SabeeApp shows a consent screen listing the exact scopes the module requests: reservations read, rate plans read, guest profiles read, folios read, and — depending on the module — reservations write and folios write. Review the list. If you are unsure why a scope is needed, cancel the flow and check the module documentation page; every scope is justified there in one plain sentence. Approve when comfortable.
Step 8 — Confirm the binding
SabeeApp redirects you back to your Sabeemod workspace. Confirm the connection is now labelled "Active" and lists the property name that matches the one displayed in your SabeeApp top-right corner. The first sync begins within a few seconds and completes for most properties within fifteen minutes.
Troubleshooting
The magic-link email did not arrive
Check the spam folder. If nothing arrives within ten minutes, add support@sabeemod.org to your safe senders list and request a new link. If the problem persists, your billing email may be misconfigured — write to support@sabeemod.org from any working address.
The OAuth flow returns "API access is not enabled"
Your SabeeApp plan does not include API access. Ask your SabeeApp account manager to enable it — there is no additional cost on the SabeeApp side for most plans. Once enabled, retry the OAuth flow.
The OAuth flow returns "insufficient permissions"
Your SabeeApp user has an operator role, not an administrator role. Ask a SabeeApp administrator at your property to complete the OAuth flow, or ask them to elevate your role. This is a one-off operation.
The first sync has been "running" for more than an hour
Large properties (200+ rooms) can take up to two hours for the initial sync because it walks the last 24 months of history. Check back periodically. If it is still running after four hours, open a support ticket.