Creating or Updating a Role: Permissions

Creating or Updating a Role: Permissions

Purpose Statement

The Permissions tab in First Due provides administrators with comprehensive control over user access rights, allowing them to grant or restrict specific capabilities within the platform. This feature ensures proper security protocols while enabling users to perform their designated roles effectively within the emergency services organization.


Background Information

User permission management is critical for maintaining system security and operational efficiency in emergency services environments. The permissions system in First Due operates on a modular basis, organizing access rights by functional areas such as incident management, personnel records, scheduling, and reporting. This granular approach allows administrators to create customized access profiles that align with organizational hierarchy, job responsibilities, and compliance requirements. Proper permission management ensures that sensitive data remains secure while providing users with the tools they need to perform their duties effectively.


Required Permissions

To manage user permissions in First Due, you must have:

  • Roles 

Video




Step-by-Step Guide



1. Navigate to the Permissions Tab

Access the user's profile and locate the Permissions tab to begin configuring access rights.

2. Search or Filter Permissions

On the Permissions tab, you can search for a particular permission using the search function, or click the Module that the permission would affect to filter permissions by functional area.




3. Utilize Bulk Actions

You have the ability to use Bulk Actions, which provide efficient permission management options:

  • Select All Permissions: Grants all available permissions within the selected scope
  • Unselect All Permissions: Removes all permissions within the selected scope



4. Apply Permission Groups

Select a Group to quickly assign predefined permission sets. Groups are configured by Product Managers and provide a streamlined way to award standardized permission collections based on common role requirements.




5. Configure Individual Permissions

The permissions are listed with granular control options. Depending on the specific permission, you will have access to the following permission levels:

  • Allow: Grants the user the ability to perform that specific permission or access that feature
  • Read: User can view the lists or items generally associated with that permission
  • Update: User can modify the lists or items generally associated with that permission
  • Create: User can create new lists or items generally associated with that permission
  • Delete: User can remove the lists or items generally associated with that permission



6. Review Permission Details

By hovering over the Info Icon next to each permission, you can view the detailed description of what that permission controls and its functional scope.




7. Save Configuration

When you have finished setting permissions according to the user's role and responsibilities, click the Save button to apply the changes.





Best Practices

Permission Assignment Strategy:

  • Start with the minimum required permissions and add additional access as needed
  • Use permission groups as a foundation, then customize individual permissions for specific roles
  • Regularly audit user permissions to ensure they align with current job responsibilities
  • Document permission rationale for compliance and troubleshooting purposes

Security Considerations:

  • Avoid granting blanket administrative permissions unless absolutely necessary
  • Implement the principle of least privilege - users should only have access to what they need for their role
  • Review and update permissions when users change roles or departments
  • Monitor permission usage to identify potential security risks or unnecessary access

Organizational Efficiency:

  • Create standardized permission groups for common roles (Captain, Lieutenant, Firefighter, etc.)
  • Coordinate with department leadership to ensure permissions align with operational needs
  • Train supervisors on permission implications to support proper access management
  • Establish clear approval processes for permission changes

Troubleshooting & FAQs

Q: Why can't I see certain permissions in the list? A: Permission visibility may be restricted based on your own access level. Contact your system administrator if you need access to additional permission categories.

Q: What happens if I accidentally remove all permissions from a user? A: The user will lose access to all First Due functionality. Use the permission groups or bulk actions to quickly restore appropriate access levels.

Q: How do I know which permissions a user needs for their role? A: Reference the permission group descriptions and hover over individual permission info icons for detailed explanations. Consult with department leadership to understand role requirements.

Q: Can I copy permissions from one user to another? A: While direct copying isn't available through this interface, you can use permission groups to standardize access across similar roles, then make individual adjustments as needed.

Q: Why are some permission options grayed out? A: Grayed out permissions may be restricted by your organization's configuration or your own permission level. Contact your system administrator for clarification.


    • Related Articles

    • Creating or Updating a Role: Users

      Purpose Statement The Role Management feature allows administrators to assign and modify user roles within the First Due system, ensuring appropriate access levels and permissions for different personnel. This functionality is essential for ...
    • Creating or Updating a Role: Configuration

      Purpose Statement Roles and Permissions allow administrators to create and manage custom user roles within First Due. This feature enables departments to define specific access levels, security requirements, and operational permissions tailored to ...
    • API User Setup

      Purpose Statement This article explains how to generate and manage API tokens within First Due, which are essential for establishing secure connections between First Due and external systems. API tokens enable automated data exchange, third-party ...
    • Admin > Field Management

      Purpose Statement Field Management enables administrators to configure and customize form fields across the First Due platform. This feature allows agencies to tailor data collection fields, set user permissions, and manage dropdown lists to meet ...
    • Restrict Inspection Types based on Permissions by Level

      Purpose Statement This feature allows administrators to control which personnel can start and complete specific inspection types by assigning permission levels. The system separates Company Level Inspections from Fire Prevention Inspections, ensuring ...