NextGen FSM

Understanding Crew Shell User Permissions

Permissions in the NextGen FSM use a role-based access control system, which means they're assigned to the user group, or user type, rather than individual users. This ensures that users like planners, dispatchers, and administrators have the appropriate access for their specific job functions.

For the Crew Shell module, the two primary permissions that control a user's ability to interact with crew data are View Crew Shells and Edit Crew Shells.

Core Crew Shell Permissions

These permissions govern basic access and modification rights within the Crew Shell functionality.

Permission

Purpose

Capabilities

Impact without Permission

View Crew Shell

Grants users the ability to see all information related to Crew Shells

  • Access the Crew Shells menu item in the FSM interface.

  • View all properties of Crew Shells, including their departure and arrival addresses, associated skills, and listed members.

  • Retrieve Crew Shell information from external systems using relevant FSM REST APIs, such as GET requests for Crew Shell properties, addresses, skills, or members.

  • Crew Shells is turned off or not visible in the main menu

  • Crew Shells are unavailable or inactive for them in other parts of the system. This effectively prevents any interaction with Crew Shell data.

Edit Crew Shell

Grants users the ability to create and modify Crew Shells.

  • Create new Crew Shells within the system.

  • Insert or change values for all information related to Crew Shells, including properties, departure and arrival addresses, associated skills, and assigned members.

  • Required to recall PATCH (for modifying existing data) and POST (for creating new data) APIs on a Crew Shell via external integrations.

N/A

Permission Hierarchy and Dependencies

  • Hierarchy: The Edit Crew Shells permission implicitly includes the capabilities of View Crew Shells. You must be able to view data before you can change it.

  • Dependencies: Crew Shell permissions often rely on broader NextGen FSM permissions. For instance, to view or edit Crew Shells, a user must typically also possess the general Resource: View or Resource: Edit permissions, respectively. This ensures a consistent and secure access model across the platform.

Recap and Next Steps

Correct permission management is essential for administrators to maintain data integrity and operational security within NextGen FSM. To manage these permissions effectively: