Configure Piece identity

How Lead360 helps

Piece Identity establishes what the Piece is for before tools or memory are attached. A precise role helps administrators choose least-privilege capabilities, reviewers build realistic Arena scenarios, and downstream consumers understand whether the Piece fits their workflow.

When to use this workflow

Use Identity at the start of a Piece and whenever the role, audience, owner, or intended business outcome changes materially.

Before you begin

Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.

• Write the role in plain business language.
• Identify internal or external audience and the exact sub-account.
• Choose an accountable owner and review cycle.

Complete the workflow

Follow the steps in order and stop when a required resource, permission, review, or approval is missing.

1. Open the Piece draft and select Identity.
2. Enter a clear name that distinguishes the role from channels and bots.
3. Describe the purpose, audience, supported outcomes, and owner.
4. State important exclusions and escalation expectations.
5. Save a new draft revision and review how the identity affects later setup steps.

Understand the key controls

Name is not authorization

A role name can explain intent but does not grant tools, memory, channels, or permissions.

Audience matters

Internal staff assistance and customer-facing use require different disclosure, privacy, testing, and escalation controls.

Material changes

Changing the role can invalidate existing capability, memory, safety, and Arena evidence and should trigger re-review.

Confirm the result

Do not rely on a success message alone. Confirm the saved state and any live effect in the product area that owns the final record.

• Ask a reviewer to explain the Piece purpose from Identity alone.
• Check that the role maps to one coherent set of tasks.
• Confirm ownership and audience remain accurate in the saved draft.

Troubleshooting

The identity is too broad

Split unrelated jobs into separate Pieces with their own capabilities, memory, and tests.

The role changed after certification

Create a new revision and repeat validation and applicable Arena certification before publication.