SupportConfigure Piece capabilities
Select the exact Lead360 tools and supported operations an Ask360 Piece can propose or use for its approved role.
How this fits into Lead360Explore Ask360 Piece StudioUnderstand the commercial operating model behind versioned Ask360 roles.- 01
How Lead360 helps
- 02
Before you begin
- 03
Complete the workflow
- 04
Understand the key controls
How Lead360 helps
Piece Capabilities defines the operational surface available to a Piece. Keeping capabilities explicit lets administrators compare the intended role with actual read and write effects, remove unrelated access, and build Arena scenarios around consequential or disallowed operations.
When to use this workflow
Use Capabilities after Identity is clear and whenever the role needs a new supported Lead360 function.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- List required outcomes and classify each as read, draft, write, send, publish, financial, destructive, or privileged.
- Confirm the current sub-account supports the operation.
- Identify user permission and confirmation requirements.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Open the Piece draft and select Capabilities.
- Review current selections and remove anything outside the role.
- Add the minimum supported capabilities required for each approved outcome.
- Inspect related scopes, effects, and confirmation policies.
- Save the revision and create Arena scenarios for allowed and disallowed requests.
Understand the key controls
Capability versus authority
A Piece capability does not override user permissions, tenant boundaries, resource assignment, or operation availability.
Consequential effects
Customer writes, external sends, publication, financial operations, deletions, and privileged invocation deserve explicit scenarios and confirmation review.
Unavailable operations
Removed and Arena-only operations cannot become production capabilities through Piece configuration.
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.
- Trace every capability to a stated role outcome.
- Test each high-risk capability with realistic inputs.
- Confirm unrelated and cross-tenant requests are refused.
Troubleshooting
A capability is missing from selection
The underlying feature or operation may be unavailable, removed, restricted, or outside the current administrator authority.
The Piece can read but not write
Check operation scope, user authority, target resource, effect policy, confirmation, and required connector or plugin.
Frequently asked questions
Does adding a capability allow every user to run it?
No. Runtime use still depends on the signed-in user, tenant, target resource, effect policy, and operation requirements.
Should read and write capabilities be tested separately?
Yes. They have different data exposure, confirmation, recovery, and audit expectations.
Continue with Lead360
Use this workflow in Lead360
Put this guide into practice with a 14-day free trial of Lead360 Pro early access, or continue learning through the related collection.