# Set up Barua

Use this guide for a new integration. Barua access is gated; an admitted owner must grant access before an agent can configure a workspace.

## Install the skill

Run this in the product repository with Node 18.17 or newer:

```sh
npx skills add getbarua/skills --skill barua-setup
```

Set `BARUA_SKILL` to the installed skill directory. For a Codex project install:

```sh
export BARUA_SKILL="$PWD/.agents/skills/barua-setup"
```

Other agents may use a different install directory. Read the installed `SKILL.md` completely. It selects the required branch references; these short guides help you find them.

## Choose access

With a scoped `BARUA_MANAGEMENT_KEY` supplied through your private environment, check what the connection can do:

```sh
node "$BARUA_SKILL/scripts/manage.mjs" capabilities
node "$BARUA_SKILL/scripts/manage.mjs" setup
```

Success is a capabilities response and the current setup state. Read `allowed` and `terms_current`; a valid key alone does not mean the requested action is permitted.

With only an event key, follow [the event-only setup path](/setup.md). A test key validates event shape but creates no people and sends no email. See [keys and permissions](/docs/guides/authentication.md) for the distinction.

## Complete setup

Follow [the management setup procedure](/skills/barua-setup/references/management.md#complete-setup-and-later-changes). Complete the [journey review](/skills/barua-setup/references/journey-review.md) before proposing or approving the onboarding plan or submitting brand settings. Preserve the owner's review choices.

Install the server event emitter and verify the sender. Finish the required approvals. The [installation reference](/docs/install.md) covers the pixel and server events. Enabled pixel observations can trigger marketing Plays for identified people under the existing marketing basis. Server events remain authoritative for consent and transactional email.

## Verify the result

Follow the skill's fresh-event proof and review-package procedure. A configured workspace is not proof of a delivered email. Report the observed delivery state, the remaining owner decisions, and the review package. Historical or duplicate events cannot satisfy launch proof.

If setup stops, use [Recover a blocked task](/docs/guides/troubleshooting.md). Owner reviews can be completed through [the owner helper](/docs/guides/owner-access.md).