User Tools
software:launchpad:managing-users
Differences
This shows you the differences between two versions of the page.
|
software:launchpad:managing-users [2019/10/08 08:37] jarrod |
software:launchpad:managing-users [2019/12/13 00:20] (current) jarrod |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| If automatic allocation is turned on, then any user with the valid token and PIN information can launch the project.\\ | If automatic allocation is turned on, then any user with the valid token and PIN information can launch the project.\\ | ||
| This will automatically deduct a credit from your LaunchPad account. If you do not have any credits remaining in your account then the automatic allocation will fail, falling back to manual allocation. | This will automatically deduct a credit from your LaunchPad account. If you do not have any credits remaining in your account then the automatic allocation will fail, falling back to manual allocation. | ||
| + | |||
| + | {{ :software:launchpad:autoallocatemaxcredits.mp4 }} | ||
| ===== Manual Allocation ===== | ===== Manual Allocation ===== | ||
| Line 18: | Line 20: | ||
| When automatic allocation is disabled, any user who attempts to launch the project will be logged and await your manual approval via the LaunchPad website. | When automatic allocation is disabled, any user who attempts to launch the project will be logged and await your manual approval via the LaunchPad website. | ||
| - | Once the user is approved, it is allocated and the project can be launched again by that user by entering the project token and PIN again. | + | When a user attempts to launch a project via a valid token and PIN code, the device details will be added to the project as 'awaiting allocation'. An email will also be sent to the project owner to notify them of the new device allocation request. |
| + | |||
| + | The project owner can then either allocate or delete the allocation request. | ||
| + | |||
| + | Once the user is approved, it is allocated and the project can be launched again by that user by entering the project token and PIN again on their mobile device. | ||
| ===== Deallocation ===== | ===== Deallocation ===== | ||
| Line 37: | Line 43: | ||
| Importantly, the device must have internet access to first load the project and must still have internet access after 'allow offline use' was enabled (if it was not enabled before first load) until it has communicated with LaunchPad server to receive the 'allow offline use' state. This will generally only take 1 minute at most. | Importantly, the device must have internet access to first load the project and must still have internet access after 'allow offline use' was enabled (if it was not enabled before first load) until it has communicated with LaunchPad server to receive the 'allow offline use' state. This will generally only take 1 minute at most. | ||
| - | After disabling 'allow offline use', the device must first connect to the internet and check in with the LaunchPad server to receive the state change before it can be deallocated from the project. | + | After disabling 'allow offline use', the device must first connect to the internet and check in with the LaunchPad server to receive the state change before it can be deallocated or removed from the project. |
| ===== Delete User ===== | ===== Delete User ===== | ||
software/launchpad/managing-users.1570523874.txt.gz · Last modified: 2019/10/08 08:37 by jarrod
