# Pascal Governance

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

Clear permissions. Accountable action.

Set who can access data, propose a change, and approve it. Keep the permission, decision, and confirmed result with the work.

## Capabilities

### Scope what each person can access

Manage membership, teams, roles, and grants. Apply the relevant workspace, record, and field restrictions to the data people and agents use.

### Check authority at the moment of action

Evaluate the current policy when a tool or operation is invoked. Keep a research task distinct from permission to change an external system.

### Bring the right person into the decision

Route consequential changes with the proposal and its evidence. Preserve the reviewer’s decision with the action it authorizes.

### Bound delegated work

Define which tools, data, resources, and effects an agent may use. Keep the scope of a task and the limits of its authority explicit.

### Trace the action through its outcome

Connect the request, policy decision, approval, and activity record. Inspect the result returned by the system responsible for the change.

### Review and maintain access over time

Inspect grants and policy decisions, review who still needs access, and handle revocation and retention through their managed workflows.

## Connected context

Apply identity, access rules, and reviews across Pascal. Keep the proposal, approval, and result connected as work passes between people, agents, and external systems.

- People, teams, roles, and access grants
- Policies, reviews, and approval decisions
- Audit history, action receipts, and retention

## Controls and permissions

Approval permits an action; the responsible system confirms its result. If the outcome is unknown, check what happened before retrying. Revoking access prevents new effects while preserving the record of work already performed.

## Example

An operator approves 14 eligible reroutes after reviewing the proposal. The Task retains the confirmed result and follow-up work. Three lithium shipments remain held, and a proposed process change still awaits Operations and Compliance. Each decision covers the work it actually authorizes.

## Workflow

### Review the proposed action

- The Task requests approval for the eligible reroutes. The proposal states its scope and retains the three hazardous-load holds.

### Inspect the confirmed result

- The recorded action returns confirmation. The team can distinguish the decision to allow the action from the result of carrying it out.

### Keep unresolved work visible

- Confirmation covers the approved reroutes. The remaining lithium loads still require their own Compliance decision before they can move.

## Next steps

Choose an action that matters. Identify who can request it, who must approve it, and which system will confirm the result.

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