- Create generic email addresses with your email domain, such as guestpilot1@cityFD.com.
- Invite and then provision each email account with a password, PIN, and other items prior to the event.
- Provide the organization ID, username and password to the guest users prior to or at the event.
- After event finishes, deactivate the user or change the generic user's password to remove access.
If you want each new guest user 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. This can be especially useful if you have temporary pilots flying with your organization for an event, as it will keep all pilot, flight, and hardware information associated with that guest user beyond their participation.
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 DroneSense, and pilots will likely not need Ops Hub access. To provide extra security around these parts of the DroneSense platform, you can configure the user to only have the Ops Viewer role, or you can choose more granular permissions by creating a role with specific permissions to these features for these users from the Admin section.