The ideal first step is to create appropriate roles for your organization. With custom roles, admins can create the ideal level of permissions based on the user’s needs. The Primary Admin Role is immutable and cannot be changed, and is the highest level of permission on an account. From there, we can set up roles for regional managers, pilots, and even stream-only access. Each account starts out with a template that offers the Admin role along with a default pilot role. The Default Pilot Role is initially set up to limit pilot visibility on the account to only their own data and logs.
Changing a User's Role:
Admins, or those with permission, can change someone's role by going into the Manage > Roles & Permissions page, selecting the desired role, and searching for the user via the side panel:
Adding Additional Roles:
If your pilots are more autonomous and doing their own planning, filing authorizations, and essential "self-approving", limiting their view to only their own activity may make sense. This also keeps the pilot's interface clean and organized.
If you run larger operations with multiple pilots, increasing the visibility may be needed. Pilots would then be able to contribute to and log information on the same missions. They would also be able to see the logs from other pilots.
Increasing visibility can also lead to increased awareness. If you have a new pilot that can only see their flights, they might realize they left off an important piece of information or step of the process if they're able to see logs from the more experienced operators.
Accounts can have as many roles as needed, although the "keep it simple" approach is encouraged. Think about how you structure your pilots currently, and create roles to match your organization. For instance, roles can be tailored based on:
Type of Operation or Use-case: Inspection team, survey team, maintenance, etc.
Aircraft complexity or type: 4-Prop Multirotor, Caged, Fixed-Wing. This can also be broken down by Tier, for instance, Tier 1 for small-frame drones, Tier 2 for intermediate or special sensors, and Tier 3 for larger-frame aircraft and sensor operations.
Pilot experience: New pilots may have additional steps that are required before and during each operation. Chief Pilots may have more flexibility in their workflows, or elevated permission to assist with the approval process of other pilot missions.
Team or Department: The marketing department will fly very differently from a security or emergency response team.
Here's an example of what that could look like:
This can vary greatly, so if you're unsure of how you want to structure the account, you can get started with the initial template as these can always be updated. Reach out to Support@Aloft.ai with any questions!
Next, you can customize the workflow for each role as needed.
Ready to start adding users?