Single Sign-On for Booking Ninjas on Salesforce
Use the single sign-on and identity architecture configured for your Salesforce environment to simplify access to Booking Ninjas without creating a separate authentication system.
Booking Ninjas can work behind your Salesforce single sign-on setup.
Booking Ninjas is Salesforce-native, so users can access the application through the authentication architecture configured for the Salesforce environment, including a connected identity provider where required.
The exact SSO method, MFA requirements, session policies, external-user access, and identity-provider configuration depend on your Salesforce licensing, security architecture, and implementation.
Simplify Access Without Creating Another Login System
Use the identity architecture your organization already relies on, then connect authenticated users to Booking Ninjas.
Single Sign-On
Use a configured Salesforce or connected identity-provider sign-in process for Booking Ninjas access.
Fewer Separate Logins
Reduce the need for another standalone Booking Ninjas credential where your SSO architecture supports it.
Identity Provider
Keep identity verification with the Salesforce or specialist identity service responsible for authentication.
Operational Access
Once authenticated, users can access the Booking Ninjas records and functions their permissions allow.
Separate Authentication From Authorization
SSO confirms how a user signs in. Salesforce permissions determine what that user can see and do afterward.
Authenticate
The user signs in through the Salesforce or connected identity-provider process configured by your organization.
Apply MFA Where Required
Use the multi-factor authentication controls supported by the Salesforce and identity architecture in use.
Authorize
Roles, permission sets, sharing rules, and related Salesforce controls determine relevant application access.
Use Booking Ninjas
Authenticated users work with the booking and operational records permitted by the configured access model.
Use SSO With the Security Controls Your Organization Requires
SSO can be one part of a broader identity and access architecture.
MFA
Use supported multi-factor authentication through the configured Salesforce or identity-provider security model.
Session Controls
Apply relevant session and sign-in policies through the security systems responsible for authentication.
Role-Based Access
Use Salesforce permissions to control access after the user has successfully authenticated.
Login Oversight
Use the authentication and login information provided by the configured Salesforce and identity services.
Connect User Access to Your Existing Administration Process
User provisioning, access changes, and offboarding depend on the Salesforce and identity-management process your organization uses.
- Create the appropriate Salesforce or external-user account where required.
- Assign the relevant roles, permission sets, and record access.
- Use the configured SSO and identity-provider architecture for authentication.
- Update access when a user's responsibilities change.
- Remove or restrict access through the appropriate administrative process when a user leaves.
- Keep specialist identity-governance tools in place where cross-system lifecycle automation is required.
Use One Identity Architecture Across Multiple Booking Ninjas Workflows
Where your Salesforce security model supports it, the same authentication architecture can serve users working across different properties, teams, or operational areas.
Property Teams
Use authentication with configured property-level record access where appropriate.
Central Teams
Provide broader access to authorized users where the Salesforce security model requires it.
External Users
Use the appropriate external-user and portal authentication architecture where a Portal is configured.
Administrators
Apply the stronger authentication and access policies your organization defines for administrative users.
AI Does Not Replace Single Sign-On or Identity Controls
Authentication decisions should remain with the Salesforce and identity systems responsible for controlling access.
Administrative Summaries
AI can summarize suitable access or administrative information when separately scoped.
Historical Review
AI can assist human review of suitable historical records where the use case supports it.
No Autonomous Access
AI should not independently grant, revoke, or approve sensitive access.
Human Oversight
Identity policy, authentication configuration, and access decisions remain with authorized administrators.
Connect SSO to Your Booking Ninjas Environment
Authentication is one layer. Booking Ninjas remains focused on the booking and operational workflows users access after sign-in.
Where Salesforce-Connected SSO Can Fit
Useful where staff or external users need controlled access to Booking Ninjas across different operating environments.
Booking Ninjas Uses Your Identity Architecture — It Is Not a Standalone SSO Provider
Booking Ninjas can operate behind the Salesforce single sign-on, MFA, session, permission, and identity-provider controls configured for your organization. It does not independently provide a universal enterprise identity platform, guarantee account security, automatically detect every suspicious login, or replace specialist identity governance, privileged-access, threat-detection, or workforce identity products. Those systems can remain in place and may be integrated where required.
Available on Salesforce AppExchange
Booking Ninjas is available on Salesforce AppExchange.
Single Sign-On Setup Pricing
SSO configuration depends on your Salesforce environment, identity provider, user types, authentication model, and implementation scope.
Configured for Your Environment
Implementation-basedThere is no separate fixed public Booking Ninjas SSO add-on price.
- User and access-model review
- Salesforce authentication configuration where required
- Identity-provider integration where required
- MFA and session-policy alignment
- Portal or external-user access where applicable
- Testing and rollout
Booking Ninjas Core
for 1–50 Active Bookable Units
- Booking Engine and Reservation System
- Availability Management and Rate Controller
- Billing and Invoicing
- Request and Contact Management
- Property Management and Front Desk
- Standard reports and dashboards
Separate Logins vs a Connected Single Sign-On Setup
Compare different ways of authenticating users before they reach Booking Ninjas.
| Capability | Separate Tool / Manual Process | Connected Operational Setup |
|---|---|---|
| Authentication | Users may maintain separate credentials for different applications | Booking Ninjas can use the Salesforce authentication path configured for the user |
| Identity provider | Each application may have its own authentication setup | Salesforce or a connected identity provider can serve as the authentication layer |
| MFA | MFA may be configured separately for each application | Supported MFA can follow the configured Salesforce and identity architecture |
| Authorization | Application permissions are administered separately | Relevant Booking Ninjas access can use Salesforce permissions and sharing |
| User lifecycle | Provisioning and offboarding may require multiple separate updates | Access can follow the Salesforce and identity administration process configured by the organization |
| Specialist identity depth | Dedicated identity platforms may provide broader cross-system governance and threat tooling | Booking Ninjas remains focused on Salesforce-native operational access |
Frequently Asked Questions
Connect Booking Ninjas to Your Existing Sign-In Architecture
Show us how users authenticate today, which identity provider you use, and which Booking Ninjas workflows each user group needs.