**The key idea:** Using a comm unit to **look something up**, using Computers to **understand** a system, and **hacking** a secured system are different tasks.
## What are you trying to do?
| Task | Typical approach | Notes |
|---|---|---|
| **Look up public information** | **Access Infosphere** with a connected device | Usually **10 minutes** on a local infosphere; research similar to Recall Knowledge. |
| **Understand a program, digital hazard or machine** | **Recall Knowledge (Computers)** | General untrained use; GM decides DC and what information a result reveals. |
| **Get into a secured network** | **Hack (Computers)** | Exploration activity; requires **hacking toolkit**. Target may demand multiple successes. |
| **Disable a computerized mechanism** | **Disable a Device** with Computers | Requires trained proficiency in Computers for the relevant trained action. |
| **Fix a broken item** | **Repair (Crafting)** | Usually takes **10 minutes**, a repair toolkit and a stable work surface; do not confuse this with bypassing security. |
*Source: Player Core, pp. 190, 196–197, 209.*
## Hacking outcomes
| Computers check | General outcome |
|---|---|
| **Critical success** | Access the system or gain **two successes** towards a multi-success system, leaving no trace. |
| **Success** | Access it or gain **one success**. |
| **Failure** | Make no progress; some systems activate security measures. |
| **Critical failure** | Trigger ingrained security or become locked out for **1 hour**. |
A hack targets a local secured system accessed directly or using your toolkit. Its **exploration** trait matters: standard Hack is **not automatically a one-action encounter button**. Special encounter hacking sequences may use procedures introduced by a scenario or the GM. *(pp. 196, GM Core pp. 222–225.)*
## Comm units and field research
- Personal **comm units** support audio and text communications at planetary range, offer a flashlight, simple computing features and a browser for accessible **local infospheres**.
- An armour-integrated comm unit supports some hands-free spoken use; **typing, apps and browsing** still generally require at least one hand.
- Publicly available information is not the same as data inside a protected terminal. A generic network search does not grant security clearance.
- Save **where, when and from whom** a lead was obtained. Taking notes is good play, not an additional rules action.
*Source: pp. 238–240.*
## Miniature example (illustrative)
**Goal:** Find the manufacturer of a disabled maintenance droid. First try relevant **Computers Recall Knowledge** or **Access Infosphere**. If its locked service records hold essential data, the team might attempt **Hack** with a toolkit. If the droid itself is malfunctioning, **Crafting/Repair** may be the right approach instead.
**Official sources:** *Starfinder Player Core*, pp. 190, 196–197, 209, 238–240. GM handling of hacking scenes: *Starfinder GM Core*, pp. 222–225. **See also:** Sheets 04, 08 and 12. **Campaign note:** Any custom Comm-Unit interface, simulated security layers or house hacking rules are distinct from the printed Hack action.