Overview

NextCrew allows administrators to set permissions based on office location. This ensures that each user (crew members, clients, or staffing managers) only has access to what is relevant to their associated office. The most common way to configure this is by assigning permissions through roles. Each user profile in NextCrew is linked to a single office location, and permissions are granted or restricted accordingly.

Navigation

  1. Go to Settings in the NextCrew Menu.

  2. Click on Permissions.

  3. Select the Role tab.

Key Features

  • Assign permissions by Role and Office Location, Groups

  • Restrict or allow access to records based on location-specific rules.

  • Apply permissions consistently across crew members, clients, and staffing managers.

  • Maintain control by first denying permissions globally, then selectively granting them.

Use Case: Setting Permissions for Crew Members

Steps:

  1. Navigate to Settings → Permissions.

  2. Select the Role tab.

  3. Choose the Crew Member role.

  4. Under Record Type, select Office Location.

  5. Choose Office Location: All and set the permission Level: Deny.

    • This removes all access permissions across different offices.

  6. Next, select the Crew Member role again.

  7. Under Record Type, select Location.

  8. Choose the Crew Member’s assigned office location and set the permission Level: Write.


Reasoning: Permissions are first denied for all locations to prevent unintended access. Specific permissions are then granted for the crew member’s associated office location.

FAQ

Q: Can a crew member be linked to multiple office locations?
A: No. Each crew member profile is associated with only one office location.

Q: Will this process affect clients or staffing managers?
A: Yes. The same role-based setup applies to all user types in NextCrew.

Q: What happens if I forget to grant permissions after setting deny for all locations?
A: Crew members will not be able to access any location-specific records until permissions are selectively granted.

Pro-Tip

Always start with deny-all permissions before assigning specific grants. This ensures stricter data security and avoids unintentional permission sharing across offices.

See Also

Legacy Compatibility

  • Works with legacy user profiles as permissions are tied to office IDs, not system versions.

  • Old role definitions may need adjustments when migrating office structures.