# Pascal Workrooms

Source: https://www.trypascal.io/platform/workrooms

One room for the people moving the work forward.

Bring people, agent Tasks, documents, and decisions together around a shared outcome. Give every handoff the context it needs.

## Capabilities

### Start with a shared purpose

Create a room around an incident, customer, project, or recurring operation. Give the team a common scope and clear ownership.

### Bring the team together

Invite people and resident agents with defined roles. Keep membership and access connected to the work they need to do.

### Keep context close

Attach business records, documents, process views, and other sources. Follow the evidence without losing the conversation.

### See what needs you

Bring mentions, waiting decisions, failed work, and assigned reviews into one attention view. Pick up at the right point after a handoff.

### Turn discussion into work

Connect threads with Tasks, workflows, and reviewable actions. Keep progress and results visible to the people responsible.

### Keep the operating record

Retain decisions, sources, files, and outcomes in an ordered history. Give the next person the context behind what happened.

## Connected context

Bring business records, Documents, Atlas investigations, and Compass cases into the conversation. Link Tasks and Workflows so the team can follow progress and review the result together.

- Rooms, membership, and resident agents
- Conversations, decisions, and operating history
- Linked context, Tasks, and work products

## Controls and permissions

A room brings the team together; each linked source keeps its own access rules. Use the approval action required by a release or operating change. Discussing a decision in the room does not approve it.

## Example

Engineering is building Factory Control while Operations and Compliance review a lithium process change. Their Workroom connects the shared brief and both Tasks, so the team can follow the implementation without mistaking software delivery for an approved operating policy.

## Workflow

### Start with the shared brief

- Keep the purpose, people, and connected work together. Everyone can see what the team is trying to deliver.

### Follow the implementation

- Open the Factory Control Task from the room. Its working copy and review state stay connected to the assignment.

### Keep the open decision visible

- The lithium operating review still names its pending reviewers. Delivering the application does not close that separate Operations and Compliance decision.

## Next steps

Choose an outcome, invite the people responsible, and connect the Tasks and evidence they need to move it forward.

- [Contact sales](https://www.trypascal.io/contact)
- [Pascal Work](https://www.trypascal.io/solutions/pascal-work)