User access in a Booking Ninjas Salesforce environment is controlled through user accounts, roles, permissions, and the records or actions each person is allowed to see or change.
The exact access model depends on job responsibilities, Salesforce licensing, security requirements, and implementation scope. Not every user should automatically receive the same level of access.
What Should Access Control?
- Which records a user can view.
- Which fields or actions a user can change.
- Which workflows or approvals they can perform.
- Which reports, dashboards, or administrative tools they can access.
Why Should Access Follow Job Responsibility?
Broad access creates security and data-quality risk. Role-based access makes it clearer who owns each action and reduces accidental changes.
How Are Staff and Portal Users Different?
Internal Salesforce users and external portal users can have different experiences and permission models. External users should only receive the access required for their self-service role.
What Should Be Reviewed Before Launch?
Test representative user roles against real workflows. Confirm that each role can complete required work but cannot access information or actions outside its responsibility.
What Should You Review Next?
Related reading: How Existing Salesforce Information Can Be Used · What Can You Explore in the Org? · Role-Based Access.
Sources and Further Reading
- Booking Ninjas: Role-Based Access — covers role-based permissions and controlled access to records and actions.
- Booking Ninjas: User Access Review — supports reviewing and governing user permissions over time.
- Salesforce Glossary: Organization (Org)
- Salesforce: Manage Users and Data Access
- Salesforce Integration Patterns
External references explain the underlying concepts; they do not imply Booking Ninjas requires or uses the referenced product.