> ## Documentation Index > Fetch the complete documentation index at: https://help.neurapulse.com/llms.txt > Use this file to discover all available pages before exploring further. # Platform Science > Drivers take Neurapulse assessments from their Platform Science tablet, with results in your Neurapulse projects. With the Platform Science integration, drivers take Neurapulse assessments on the Platform Science tablet in their cab. Platform Science signs them in, so they never need a Neurapulse login, and their results land in your Neurapulse projects. > [!NOTE] > > Integrations are in **Preview**. ## At a Glance | | | | - | - | | **Available on** | Essentials and higher plans | | **Set up by** | Your Impirica account manager | | **Drivers use** | The Neurapulse app on their Platform Science tablet | | **Drivers are grouped by** | Terminal | | **Driver list refreshed** | Daily | | **Scheduled tests** | Not sent by Neurapulse | ## Getting Connected Impirica connects your Platform Science account for you. There is no connect button in the portal, and you never enter credentials yourself. **1. Contact your Impirica account manager** Tell them you use Platform Science and which Neurapulse workspace your drivers should join. **2. Impirica connects the account** Your account manager links your Platform Science account to the workspace. They can see your terminals and how many active drivers each one has. **3. Impirica sets up your projects** Together you agree on a default project for your drivers, and whether any terminals should go to a project of their own. Impirica can create new projects for you during setup. **4. Make the app available on your tablets** Your fleet's Platform Science administrator makes the Neurapulse app available on your tablets. To check the connection, go to **Settings**, find the **Integrations** card, and click **Manage Integrations**. For your Platform Science account you will see: * **Connected by Impirica on** the date the connection was made. * **Last test taker sign-in**, the most recent time a driver opened Neurapulse from their tablet and Platform Science signed them in. It counts every launch that reached Neurapulse, including launches where the driver could not start an assessment, for example because their terminal is not enrolled. * **Default project**, where drivers go unless their terminal has its own project. * **Terminals**, for example "4 terminals · 2 use the default · 1 own project · 1 not enrolled". * **Projects**, the projects receiving drivers. Neurapulse reads your terminals and drivers from Platform Science when the account is connected, then refreshes them every day. New terminals appear automatically and follow the default project. ## What Drivers See **1. Open Neurapulse on the tablet** The driver opens the Neurapulse app from their Platform Science tablet. **2. Signed in automatically** Neurapulse recognizes the driver through Platform Science. The first time, it adds them as a test taker in the project for their terminal. **3. Take the assessment** The assessment runs in the app. If it needs the camera, the app asks only at that step. Most fleet tablets already allow it, so drivers usually see no prompt. The result shows in the project like any other test taker's, and follows that project's settings. Some drivers cannot start an assessment: | Driver | What the app shows | | - | - | | Terminal set to **Not enrolled** | *You're not enrolled in an assessment yet. Contact your fleet administrator.* | | Removed from the project in Neurapulse | *You're not enrolled in an assessment yet. Contact your fleet administrator.* | | Not found in Platform Science for your account | *You're not enrolled in an assessment yet. Contact your fleet administrator.* | | Inactive or terminated in Platform Science | *Your driver account isn't active. Contact your fleet administrator.* | | Shares their driver ID with another active driver in Platform Science | *More than one driver in your fleet has your driver ID. Contact your fleet administrator.* | ## Driver Details When a driver starts their first assessment, Neurapulse fills in their first name, last name, phone number and email from the Platform Science app on their tablet. Values Neurapulse can't use are left blank, for example a phone number it can't convert to international format. You can edit the details in Neurapulse at any time. Later assessments fill in only details that are blank, so a value you change is kept, but a field you clear is filled in again at the driver's next assessment. If Platform Science has no email for a driver, or the email already belongs to another test taker in the project, Neurapulse gives the driver a placeholder address ending in `@platformscience.invalid`. When a later assessment brings an email Neurapulse can use, it replaces the placeholder. ## Removing a Driver Deleting a Platform Science test taker from a project stops them starting assessments. Their next launch on the tablet shows *You're not enrolled in an assessment yet* and does not add them again. Workspace owners and admins can re-enrol them: **1. Open Removed test takers** Go to **Settings**, click **Manage Integrations**, and open **Removed test takers** under your Platform Science account. **2. Re-enrol the driver** Click **Re-enrol** next to the driver. They can start assessments again from their tablet, and their earlier results are kept. A test taker whose data was erased can't be re-enrolled. ## Choosing Which Project Drivers Join Workspace owners and admins choose which project each terminal's drivers join. Go to **Settings**, click **Manage Integrations**, and click **Edit mapping** on your Platform Science account. Each terminal is set to one of three choices: | Choice | What happens | | - | - | | **Default project** | Drivers join the default project. If you change the default, these terminals follow it. New terminals start here. | | **A specific project** | Drivers join the project you pick, whatever the default is. | | **Not enrolled** | Drivers at this terminal cannot start assessments. | The **Default project** setting at the top applies to every terminal that follows the default, including terminals added later. You can set the default itself to **Not enrolled** so that only terminals with their own project can take assessments. Drivers without a terminal join the default project. When you have many terminals, the editor adds a search box (by terminal name or ID) and filters for All, Default, Own project, Not enrolled, and Changed. A terminal you change stays in view until you change the filter or search. Terminals marked **Not in the latest sync** no longer appear in Platform Science; their setting is kept in case they come back. ### When You Change the Mapping The editor warns you before you save a change that affects drivers. * **Moving a terminal to another project.** Drivers keep their earlier results in the old project. Their next assessment starts a new record in the new project. * **Changing the default project.** Every terminal that follows the default moves with it, including terminals added later. * **Setting a terminal to Not enrolled.** Its drivers can no longer start assessments. Their past results stay where they are. The same applies when a driver moves to another terminal in Platform Science: their next assessment goes to that terminal's project, and earlier results stay where they were. ## Scheduled Tests and Send Test Neurapulse does not send scheduled tests to Platform Science drivers. A project that receives Platform Science drivers, as the default or as a terminal's own project: * Has **Test Frequency** locked in project settings, with a note and a **Manage integration** link. * Shows **Managed by Platform Science** in the project list's **Schedule** column. * Sends no Neurapulse scheduled tests to anyone in it, including people you added by hand. > [!WARNING] > > When a project starts receiving Platform Science drivers, its scheduled tests stop for everyone in it. The mapping editor tells you before you save. If a project stops receiving drivers, its scheduled tests stay off. Turn them back on in the project's settings when you are ready, so drivers who only use their tablet are not suddenly emailed. Neurapulse does not send links to Platform Science drivers: * **Send Test** to one of them is refused with "This test taker starts assessments from a connected platform, so Neurapulse doesn't send them links." * **Bulk sends** skip them and send to everyone else selected. Other test takers in the same project, such as people you added by hand, can still be sent links. ## Disconnecting To stop using Platform Science, contact your Impirica account manager. Once disconnected, drivers can no longer start assessments from their tablets. Their past results stay in your projects, and scheduled tests stay off until you turn them back on in each project's settings. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.