The Organization page is used to configure settings that apply across the entire OWL environment. These settings establish the organization's identity, available modules, default access configuration, and global policies that affect all users. Organization-level settings should be configured during the initial deployment and updated whenever organizational requirements change.
The Organization page contains three tabs:
- Info – View and manage organization details and primary contact information.
- Role Settings – Configure default module access, security, notifications, collaboration, and compliance settings for roles and license types.
- Organization Module Catalogue – View the modules and features available to the organization based on the licensed OWL edition.
Info Tab
The Info tab displays the organization's general information and administrative contact details.
Organization Information
This section identifies the organization within OWL
- Organization Name
- Account ID
- Time Zone
- Default Language
These settings affect the organization as a whole and should be configured during initial deployment.
Organization Address
This section stores the organization’s administrative address details.
- Billing Address
- Shipping Address
- City
- State
- ZIP/Postal Code
- Country
These details are primarily used for administrative and licensing purposes.
Primary Contact
This section identifies the organization’s primary administrator or business contact.
- Name
- Username
- Email Address
- Phone Number
- Mobile Number
The primary contact is typically the person responsible for coordinating with organization administrators or OWL support.
Role Settings Tab
The Role Settings tab allows administrators to configure the default capabilities available to users based on their assigned Role and License Type.
First, select:
- Role
- License Type
Then configure the available settings through the applicable configuration tabs.
Module Access
Module Access controls the OWL modules and features available to the selected role and license type.
Examples include:
- Query Data
- Case Management
- Collaboration
- Monitoring
- OWLdocs
- Analytics
- Tasks & Calendar
Individual features within each module can also be enabled or disabled, depending on the selected license.
Configure here when:
- A role should have access to specific OWL modules.
- Different roles require different functional capabilities.
Security Policies
Security Policies define the security requirements available to the selected role and license type.
Examples may include:
- Authentication requirements
- Password policies
- Multi-factor authentication requirements
- Session restrictions
- Login security
Configure here when:
- Different user groups require different security controls.
Notifications
Notifications determine the notification types and delivery methods available to users in the selected role.
Available methods may include:
- SMS/Text Message
- Web UI Notifications
Organizations can control which system events generate notifications for each role.
Configure here when:
- Different user groups require different notification preferences.
Collaboration
Collaboration defines the collaboration capabilities available to the selected role.
Examples may include:
- External Collaboration
- Cross Department Collaboration
- Information Sharing
- Sharing records
- Collaboration approvals
Configure here when:
- Certain roles should be allowed to collaborate internally or cross department.
When both User Collaboration settings and Role settings are configured and cover the same user, the user-level collaboration settings take precedence.
Deconfliction
Deconfliction controls access to the features used to identify potential overlap or operational conflicts between investigations.
Depending on permissions, users may be able to:
- Submit investigations for deconfliction
- Search existing deconfliction records
- View potential conflicts
- Manage deconfliction requests
Configure here when:
- Roles participate in investigative coordination across departments or organizations.
Organization Module Catalogue Tab
The Organization Module Catalogue provides a read-only overview of the modules and features available to the organization based on the purchased OWL Software Edition.
The page displays:
- Purchased OWL Software Edition (Standard, Enterprise, Smart City, etc.)
- Active Modules - The number of modules included in your current edition. These are the ones you can actually grant to roles and users.
- Locked Modules - Locked Modules are modules that exist in OWL but are not included in your organization's licensed edition.
- Total Features - The total count of individual features across all modules in the catalogue. Every module contains some number of granular features/capabilities, and this stat sums them up. So it counts features, not modules.
- Module Categories - The number of distinct groupings the modules fall under (Query Data, Case Management, Collaboration, etc.)
Modules are grouped by category, such as:
- Query Data
- Case Management
- Collaboration
- Monitoring
- OWLdocs
- Analytics
- Notifications
Each module displays:
- Module Name
- Status (Active or Locked)
- Number of available features
This tab helps administrators understand which modules are available under the organization's current license before assigning permissions through Role Settings.
Best Practices for Organization Settings
- Use Role Settings to manage permissions for groups of users rather than configuring individual users.
- Assign users to the appropriate Department/Team for operational organization and supervisor oversight.
- Use individual user-level access changes only for approved exceptions, and review those exceptions regularly.
- Follow the principle of least privilege: give users access only to the modules and features required for their work.
- Review role access, security controls, collaboration permissions, and notification settings periodically.
- Review the Organization Module Catalogue before requesting or assigning access to a module.