# Engineering (/docs/roles/engineering)

Default demo person: Daniel Tan, Process engineer. This page describes the default access of the **Engineering** role. The Org admin can change it under **Settings > Roles & permissions**; see [Roles at a glance](/docs/roles).

## What you do [#what]

You take a new product from development item to released method, keep products, bills of materials and work instructions current, and propose engineering changes.

## Where you start [#start]

Sign in, choose your workspace, and the apps launcher opens. It shows one tile for each module your role can open. **My work** carries a number when records are waiting for you.

<GuideStep
  title="Your apps launcher"
  description="The apps launcher with the tiles this role can open."
  src="/guide/roles-engineering/1.png"
  alt="Apps launcher on desktop showing the modules available to Engineering"
  width={1440}
  height={1000}
  callouts={[
    { x: 18, y: 24, caption: "My work: the number of records waiting on you." },
    { x: 50, y: 24, caption: "Module tiles. Only the modules your role can open appear." },
    { x: 82, y: 24, caption: "Settings, if your role has it." },
  ]}
/>

Your queue on **Home > Queue** (My work): Production methods in **Draft**, and products.

<GuideStep
  title="Your work queue on a phone"
  description="My work on a phone, the records waiting for this role."
  src="/guide/roles-engineering/2.png"
  alt="My work queue on mobile for Engineering"
  width={375}
  height={812}
  callouts={[
    { x: 50, y: 6, caption: "Page title and your role." },
    { x: 50, y: 30, caption: "One card per record waiting. Live-order records come first." },
    { x: 50, y: 94, caption: "Bottom tabs to move between modules." },
  ]}
/>

## Your daily screens [#screens]

| Screen | Where | What you do there |
|---|---|---|
| **Products** | `/engineering/engineering` | Products, revisions and bills of materials. |
| **Work instructions** | `/engineering/steps` | Step-by-step instructions for the floor. |
| **Development items** | `/engineering/devit` | Track a new product through feasibility to qualified. |
| **Device files** | `/engineering/mdf` | Device master files. |
| **Engineering change notes** | `/engineering/chg` | Propose and follow changes. |
| **Process FMEA** | `/engineering/fmea` | Score and reduce process risk. |
| **Process validation** | `/engineering/pval` | Protocols and reports. |

<GuideStep
  title="The products list"
  description="Engineering products list."
  src="/guide/roles-engineering/3.png"
  alt="Products with revision and status"
  width={1440}
  height={1000}
  callouts={[
    { x: 30, y: 22, caption: "Filter or search products." },
    { x: 55, y: 40, caption: "Revision and status of each product." },
    { x: 70, y: 40, caption: "Open a product to see its bill of materials and method." },
  ]}
/>

## What you can do [#can]

You have full access to: Engineering. You can create, edit and take steps there.

Steps you sign, with the button names on screen:

| Record | Steps |
|---|---|
| Products, work instructions and production methods | **Submit for review**, **Approve**, **New revision** |
| Process FMEA | **Start action**, **Re-score · close**, **Reopen (change / new data)** |
| Development items | **Move to DFM review**, **Move to Trial**, **Move to First article** (the QA manager signs **Approve · qualified**) |

A signed step needs your [e-signature specimen](/docs/get-started/signatures-and-refusals#specimen) and, where a requirement is set, current training.

## What you can see but not change [#view]

View access: Sales, Purchasing, Inventory, Production, Quality, Maintenance, EHS. You can open and read these. Their action buttons are disabled with `Your role can view this but not change it.`

## What you cannot do and who does it [#cannot]

| You cannot | Who does it | What you see |
|---|---|---|
| Approve a validation protocol or report | QA engineer or QA manager | `This step needs a QA engineer signature. You are signed in as Daniel Tan (Process engineer).` |
| Send a change to the change board | QA manager | `This step needs a QA manager signature. You are signed in as Daniel Tan (Process engineer).` |
| Open Inventory | Org admin can change access | `Your role has no access to Inventory.` |

Hidden for your role: Settings. They do not appear on the launcher. If you open one by address you see **You do not have access to this page** and **Back to apps**.

## A typical day [#day]

<Steps>
<Step>

Open **My work**. Read the methods in draft. Details: [Find your way around](/docs/get-started/find-your-way-around).

</Step>
<Step>

Move the development item through its stages. Details: [Development items](/docs/product-development/development-items).

</Step>
<Step>

Write the bill of materials and the method. Details: [Bill of materials](/docs/product-development/bill-of-materials).

</Step>
<Step>

Write the work instructions. Details: [Work instructions](/docs/product-development/work-instructions).

</Step>
<Step>

Submit each document for review and approve it. Details: [Document release](/docs/product-development/document-release).

</Step>
<Step>

Propose a change to a released document. Details: [Engineering changes](/docs/product-development/engineering-changes).

</Step>
</Steps>

<NextSteps>

<NextStep href="/docs/product-development/development-items" title="Development items" description="Start a new product." />

<NextStep href="/docs/get-started/signatures-and-refusals" title="Signatures, reasons and common refusals" description="Why a button is disabled and what to do." />

<NextStep href="/docs/roles" title="Roles at a glance" description="Compare your role with the others." />

</NextSteps>