Identity & Access

Multi-Factor Authentication on Salesforce

Booking Ninjas runs in Salesforce, so user authentication and MFA can follow the Salesforce and identity-provider controls configured for your environment.

MFA protects access to Booking Ninjas through the Salesforce security environment.

Booking Ninjas does not need to become a separate authentication system. Internal and external access can use the Salesforce authentication architecture and connected identity providers configured for your organization.

The exact MFA methods, authentication policies, session controls, device rules, login restrictions, and identity services depend on your Salesforce edition, licensing, identity architecture, and implementation.

Require More Than a Password

Use the authentication controls configured for your Salesforce environment before users reach Booking Ninjas.

Multi-Factor Authentication

Require supported additional verification through the authentication architecture configured for the user.

User Access

Apply the relevant Salesforce access model after authentication succeeds.

Identity Providers

Use connected identity providers when your organization requires SSO, federation, or specialist authentication.

Authentication History

Use authentication and login information available from the configured Salesforce security environment.

Connect Authentication to Access Control

Authentication confirms access to the environment; permissions determine what each user can do afterward.

Authenticate

The user signs in through the configured Salesforce or connected identity-provider process.

Verify

MFA or other supported authentication controls are applied according to the security configuration.

Authorize

Salesforce roles, permission sets, sharing rules, and other configured controls determine relevant application access.

Use Booking Ninjas

Authenticated users can work with the Booking Ninjas capabilities and records their configured access permits.

Use Conditional Security Controls Where Supported

More advanced authentication rules depend on the Salesforce and identity services in your security architecture.

  • Apply supported sign-in and session policies to relevant users.
  • Use configured authentication requirements for privileged or sensitive access.
  • Use identity-provider or Salesforce controls for device, network, or location-related policies where supported.
  • Use configured restrictions when a login does not meet your organization's access requirements.
  • Review available login and authentication information through the relevant security administration tools.
  • Scope advanced identity and authentication services separately where required.

Protect Sensitive Operational Access

Use authentication and Salesforce permissions together when Booking Ninjas users have different levels of responsibility.

Administrators

Apply the authentication and permission requirements your organization defines for administrative access.

Operational Users

Give staff access only to the records and functions required for their configured role.

External Users

Use the appropriate external-user and portal authentication model where a Booking Ninjas portal is configured.

Access Review

Review relevant user access and permission assignments according to your internal security process.

Keep Authentication Oversight With the Security Layer

Login monitoring and authentication controls should remain with Salesforce and the identity services responsible for access.

Login Activity

Review authentication information made available by the configured Salesforce environment.

Security Policies

Apply supported authentication and access policies through the appropriate security administration layer.

Identity Integration

Use specialist identity or authentication providers where your architecture requires them.

Operational Access

Keep Booking Ninjas focused on the operational records and workflows users are authorized to access.

AI Does Not Replace Authentication Controls

Identity assurance, MFA, authentication decisions, and security enforcement should remain with the systems designed to control access.

Activity Summaries

AI can summarize suitable administrative security information when separately configured.

Pattern Review

AI can assist human review of suitable historical information where the data and use case support it.

Administrative Support

AI can help organize information without becoming the authentication or access-control authority.

Human Oversight

Security policy and access decisions remain controlled by your organization and its configured security systems.

Connect Authentication to the Rest of Your Salesforce Environment

Identity services can remain separate while Booking Ninjas uses the authenticated Salesforce environment for operations.

Booking Ninjas Uses the Salesforce Security Environment — It Is Not a Standalone MFA Provider

Booking Ninjas can operate behind the authentication, MFA, permissions, and identity-provider controls configured for your Salesforce environment. It does not independently guarantee identity, prevent account compromise, detect every suspicious login, or replace specialist identity, fraud, security-monitoring, or privileged-access products. Authentication capabilities and licensing depend on the Salesforce and identity services you use.

Available on Salesforce AppExchange

Booking Ninjas is available on Salesforce AppExchange.

MFA and Authentication Setup Pricing

Authentication costs depend on the Salesforce security architecture, user types, identity providers, and implementation required.

When Core is required

Booking Ninjas Core

Starts from $400/month

for 1–50 Active Bookable Units when authenticated users are accessing Booking Ninjas Core workflows

  • Booking Engine and Reservation System
  • Availability Management and Rate Controller
  • Billing and Invoicing
  • Request and Contact Management
  • Standard reports and dashboards
  • Basic transactional communication
Security services can be separate. Salesforce user or external-user licensing, identity-provider services, authentication products, SSO infrastructure, specialist security tools, and custom integrations can create additional costs. Implementation is quoted after the user, access, and identity architecture is reviewed.

Password-Only Access vs MFA-Protected Access

These approaches differ in how users prove their identity before reaching the application.

Capability Password-Only Access MFA-Protected Salesforce Access
Authentication Relies on the primary sign-in credential Uses an additional supported verification step
Booking Ninjas access Depends on the authentication configuration in use Users authenticate before reaching permitted Booking Ninjas workflows
Permissions Still require separate application authorization Salesforce permissions continue to govern what authenticated users can access
Identity provider May use the native sign-in environment Can use Salesforce or a connected identity provider where configured
Security administration Managed through the relevant authentication platform MFA and authentication remain governed by the Salesforce security architecture
Operational system Authentication and operations remain separate responsibilities Booking Ninjas remains focused on authorized operational workflows

Frequently Asked Questions

What is multi-factor authentication?

Multi-factor authentication requires a user to complete an additional verification step beyond the primary sign-in credential before access is granted.

Does Booking Ninjas have its own MFA system?

Booking Ninjas is Salesforce-native and can use the authentication environment configured for Salesforce users. It is not positioned here as a separate standalone MFA provider.

Can Booking Ninjas work with single sign-on?

SSO can be used where the Salesforce environment and connected identity architecture are configured to support it.

Can external portal users use MFA?

External-user authentication depends on the portal, Salesforce licensing, identity architecture, and security configuration used for that implementation.

Can access differ by user role?

Yes. Authentication establishes the user session, while configured Salesforce roles, permission sets, sharing rules, and other controls determine what relevant Booking Ninjas data and functions a user can access.

Can device or location rules be used?

Device, network, location, session, or contextual security rules depend on the Salesforce and identity services configured for your environment.

Does Booking Ninjas detect suspicious logins?

Booking Ninjas is not positioned as a standalone login-threat detection system. Login monitoring, authentication risk, and related security controls should remain with Salesforce or the specialist identity and security services responsible for access.

Does MFA guarantee that an account cannot be compromised?

No. MFA adds another authentication control, but account security still depends on the authentication methods, identity provider, user behavior, security configuration, session controls, and wider security practices.

Does Booking Ninjas use AI for authentication decisions?

Booking Ninjas does not position AI as the authentication authority. AI-assisted administrative summaries or analysis can be separately scoped, while authentication and access enforcement remain with the configured security systems.

How much does MFA setup cost?

There is no separate fixed public Booking Ninjas MFA price. Cost depends on Salesforce licensing, user types, identity-provider services, SSO or authentication requirements, and implementation. If Booking Ninjas Core is required, Core starts from $400/month for 1–50 Active Bookable Units.

Connect Booking Ninjas to Your Existing Access Model

Show us who needs access, how users authenticate today, and which Booking Ninjas workflows each user type should reach.

WhatsApp Us

WhatsApp Us