SupportAssign Ask360 bot capabilities
Grant an Ask360 bot the smallest set of supported product capabilities required for its role.
How this fits into Lead360Explore Ask360See how Pieces, memory, channels, playbooks, learning, and kits work together.- 01
How Lead360 helps
- 02
Before you begin
- 03
Complete the workflow
- 04
Understand the key controls
How Lead360 helps
Capabilities define which Lead360 operations a bot can use. Keeping them separate from identity, memory, connectors, and channels makes access reviewable and lets administrators reduce a bot to the exact product functions needed for its approved job.
When to use this workflow
Use Bot Capabilities during initial bot setup, when adding a verified workflow, or when removing access that is no longer needed.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Write the required read and write outcomes.
- Identify the corresponding supported capabilities and effect risk.
- Confirm the administrator can grant access for this sub-account.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Open the intended bot profile.
- Review currently assigned capabilities and remove stale access.
- Add only the capabilities required by the approved workflow.
- Configure related effect policies and resource mappings.
- Test an allowed request and a disallowed request before enabling the bot.
Understand the key controls
Capability is not permission escalation
The bot, signed-in user, and tenant operation must all be authorized. A capability does not override user or sub-account boundaries.
Read and write effects
A capability name may cover operations with different confirmation requirements. Inspect the actual operation and effect policy.
Ongoing review
Capabilities should be revisited when the bot role, channel, owner, or connected resources change.
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.
- Review the final capability list against the role definition.
- Confirm disallowed operations remain unavailable.
- Inspect audit records for controlled test operations.
Troubleshooting
A capability is unavailable
Check feature availability, administrator authority, and whether the related operation is production-supported. Removed and Arena-only operations cannot be granted for live use.
An allowed capability still fails
Check the signed-in user, bot effect policy, connector or resource mapping, confirmation, and target record state.
Frequently asked questions
Does a bot capability override user permissions?
No. Live operations still require the relevant tenant, user, resource, and operation authority.
How often should capabilities be reviewed?
Review them after role, owner, channel, connector, plugin, or workflow changes and as part of a regular least-privilege access review.
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.