Skip to main content
Sign in

Guest or Temporary Users

  • Updated
There may be occasions where pilots outside your organization need to be added to your organization for a mission or other event. You may also need to provide access to non-pilots for Operations Hub access.
 
The easiest approach to adding this kind of user is to create a generic temporary ID.
  1. Create generic temporary logins with your email domain, such as guestpilot1@cityFD.com.
  2. Invite and then provision each account with a password, PIN, and other items prior to the event.
  3. Provide the organization name and log in credentials to guests prior to or at the event.
  4. After event finishes, change each password to remove access.

Additionally, you can ask DroneSense Support to suspend the account and then reactivate before the next event. If you want each new guest pilot to start completely fresh, you can revoke the generic users after an event and create new accounts starting at the next number, such as guestpilot27@cityFD.com.

TIP: If your organization uses Google as its email provider, you can use the + modifier to create multiple email addresses for logins that all point to the same email address. For example, guestpilot+1@cityFD.com and guestpilot+5@cityFD.com would act as unique DroneSense users, but Google treats these both as guestpilot@cityFD.com, which makes it easier to manage from a single email account.

Restricting Guest Permissions

Guest or temporary users generally will not need access to most of the data management features of the DroneSense Web platform. To provide extra security around these parts of the DroneSense platform, you can create a role specifically for these guest users that has restricted access to unnecessary or sensitive features.

Related articles