Sharing authorities between organisations

Enterprise customers can share company authorities between multiple organisations (internal or external)

This article will cover the following:

• Authority Sharing

• Switching between organisations

• Creating a Mission Workflow using the shared authority 

• CRP approving missions

(back to top)

The ability to share authorities across 2 or more organisations can be useful in many ways. Some common examples include:

• For large organisations - the ability to manage your operator certificate and associated workflow centrally, while enforcing it's use across multiple sites.
• Providing oversight of missions conducted by the 'child' organisation (missions conducted under the parent's authority are visible in the parent organisation).

1. From the Organisation Admin panel, click on 'Shared Resources'
   
   
2. From the dropdown box, select the organisation you would like to share your authority with and click 'Add'. This org will be referred to as the 'child organisation'.
   
3. Under the 'Shared Authorities' dropdown box, select the relevant authority you want to share and click 'Share'. In this example, I have shared the ReOC authority.
   
   It should look something like this:
   
   
   You have now shared your authority with the child org. The next step is to create a mission workflow using this shared authority in the child org. 
   
   

Switching between organisations

(back to top)

Once you have established a parent-child relationship, the org admin user will be able to switch between orgs easily. 

On the left-hand panel, click on the dropdown box and select the organisation you would like to switch to:

Creating a Mission Workflow using the shared authority

(back to top)

1. From the child org, navigate to the 'Organisation Admin' panel
2. Click on 'Mission Configuration'
3. Click the 'plus' icon to create a new mission workflow
4. This window is where you will configure the mission workflow:
   1. Name: give this workflow a meaningful name so it is clear to the remote pilots which workflow they are selecting. 
   2. Primary Authority: Use the dropdown box to select the shared authority. This will inherit all forms configured in this authority's workflow.
   3. Click 'Save and Close'.
      
      
   
   You have now created a mission workflow in the child org using the shared authority.

CRP approving missions

(back to top)

Depending on the users notification preferences, (if switched on) the CRP will receive an email notifying a mission has been submitted for approval. The email will state which organisation the approval has come from. Please check this carefully.

1. Make sure you are in the correct organisation
2. See How to approve a mission (CRP/SRP) to perform the approval