In Bearish OS CRM, permissions and access control are critical for ensuring that sensitive customer and business data is securely managed while allowing the right people to access the information they need. The system is designed to provide granular control over who can view, edit, and manage data within the CRM.
Role-Based Access Control (RBAC)
Bearish OS CRM employs a Role-Based Access Control (RBAC) system that allows administrators to define user roles and assign specific permissions. Roles dictate what actions users can take within the CRM:
Admin: Full access to all CRM features and data. Admins can view, edit, delete, and manage contacts, companies, deals, and groups. They can also adjust user permissions for others.
Manager: Managers have broader visibility over their team's activities and can access CRM data for users they manage. They can create, edit, and assign contacts, companies, and deals to their team members.
User: Regular users can access contacts, companies, and deals they are assigned to. They may also have permission to view or collaborate on shared data, depending on their role in the project or team.
Restricted User: Users with restricted access can only view basic details of contacts or companies they are directly involved with (e.g., First Name, Last Name, Email). They cannot edit, delete, or access any additional sensitive information.
Field-Level Permissions
Bearish OS CRM supports field-level permissions, allowing specific data fields to be restricted based on the user’s role:
View-Only Fields: Certain fields, such as sensitive financial data or personal contact details, can be marked as view-only for lower-level users.
Editable Fields: Admins and users with appropriate permissions can edit core fields such as job titles, contact information, or deal details. Users with lower permissions may be restricted from making changes.
Access to Sensitive Data
Sensitive data, such as personal contact information, financial details, and deal valuations, can be restricted to specific roles or teams. This ensures that only authorized personnel have access to confidential information.
Full Access: Users with full access can view and edit all fields and activities related to a contact, company, or deal.
Limited Access: Users with limited access may only view selected fields, such as basic contact information and activity logs, and may have the ability to add notes or comments without altering core data.
Custom Permission Groups
Admins can create custom permission groups tailored to specific business needs. This feature allows companies to define unique access levels for departments or teams (e.g., Sales, HR, Legal) based on their responsibilities and the type of data they interact with.
Sharing and Collaboration Permissions
Bearish OS CRM includes options for sharing contacts, companies, and deals with other users or teams:
Direct Sharing: Users can directly share a contact, company, or deal with colleagues, granting view or edit access. Permissions can be customized for each shared entity.
Collaboration Settings: Teams working on the same deals or projects can collaborate within the CRM, with permissions set to define who can edit, view, or comment on specific items.
Audit Logs and Activity Tracking
Every action taken within the CRM is logged, allowing admins to review who accessed or modified a contact, company, or deal. Audit logs track:
- Who viewed or edited specific data.
- When changes were made and by whom.
- What changes were implemented (e.g., field updates, deletions).
- This feature ensures transparency and accountability within the CRM.
Integration with External Systems
Bearish OS CRM permissions extend to integrations with external systems (e.g., Slack, Outlook, Teams). When syncing data between Bearish OS and external CRMs or communication tools, access control remains intact, ensuring only authorized Bearish OS users can interact with synced data.
The combination of role-based access, field-level permissions, and activity tracking in Bearish OS CRM ensures that sensitive data is properly managed, while still allowing for collaboration and efficient data management.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article