Wallfacer

See what ran, what changed, and who decided.

Choose the access an employee gets and the decisions your team keeps. Wallfacer records the steps, attempts, and decisions in configured work, so you can follow the result back to the work behind it.

Explore the controls

Keep your team’s decisions in the process.

Choose what the employee can access, which reviews the work needs, and where a person decides. Build those boundaries into the way the job runs.

  1. Assigned work
    Agent checks and review

    The configured checks and review happen before the handoff.

  2. Human decision

    Approve, request changes, or stop.

  3. Your existing release process

    Continue through your team’s merge and release requirements.

One example of a configured engineering workflow. Your playbook determines the steps, reviewers, decision points, and paths for corrections.

GitHub branch protections and required checks remain controls you configure in your repository. Set employee permissions and playbook reviews to work with those requirements.

How the handbook works

Follow the work, including the corrections.

A requested change is part of the story. The task record connects recorded attempts and decisions so you can follow how the work moved forward.

An example task record

Illustrative sequence for a configured process.

  1. Implementation assigned

    Engineering employee · attempt 1

    The employee prepares a change and requests review.

  2. Review requests changes

    Reviewing employee

    The review records findings and returns the work for correction.

  3. A corrected attempt

    Engineering employee · attempt 2

    The employee addresses the findings and brings the updated work back for review.

  4. A person approves

    Human reviewer

    The work reaches the configured human decision.

The process used for the job

For a playbook run, the task retains the published process version it followed. Linked handbook pages have their own revision history.

People, employees, and attempts

Step records identify the performer, attempt, and recorded outcome. You can see where review sent work back and who made a decision.

A record you can inspect and export

Export the task record and compare it with pull requests, checks, and change history in your connected systems. Session links lead to the related conversation.

Give access for the job.

Choose the accounts and systems the employee needs. Credentials are used when preparing and running its environment; controls on storage and snapshots help manage that access.

Read about security

  • Encrypted values. Separate keys.

    Stored secret values are encrypted. The keys used to unlock them are held in a separate key service.

  • The API keeps secret values write-only.

    The customer API returns information about a stored secret, rather than returning its value.

  • Clean credentials out before saving.

    The snapshot process removes per-identity credentials before saving the setup. If that cleanup fails, capture stops.

Bring your security team into the setup.

Review how the employee will work before connecting it to your systems. We can work through security questionnaires and the evidence your team needs to assess the setup.

Start with the questions that matter.

  • Which systems can this employee access?
  • Which actions need a person’s decision?
  • What records will your team review and retain?
  • Where will the code and credentials be used?

Work records are one part of an assessment. Your team evaluates them alongside your policies, connected systems, and applicable audit requirements.

Security details

Let’s work through your requirements.

Bring the job, the systems it touches, and the decisions your team needs to keep. We’ll discuss access, review, and the records you need.

Talk about your controls