Workspace and project scope
Groups and project permissions govern access to resources. Customer-facing actions also carry customer identity and group permissions.
Security
Controls around access, identity and action.
This overview describes implemented product controls. For security requirements or documentation requests, contact our team.
Product access controls
Tool authority
Tools are filtered by the agent’s capabilities and the invoker’s permissions. Execution checks the applicable scope and requirements; sensitive operations can require confirmation.
Customer-data endpoints
Configured endpoints bind customer identity, declare input parameters and return selected response fields. Credentials are stored separately from model input and are not returned by settings reads.
MCP installation approval
Configured MCP servers require installation approval before discovery or execution. Agent links and allowed or denied tool rules narrow access.
Review and follow-up
Operational records
Conversation history, ticket activity, workflow runs and approval decisions help teams inspect what happened in supported workflows.
Discuss your requirements
Ask our team about your security and data-handling requirements. Current sign-in supports email/password, Google and GitHub; enterprise SSO and provisioning are planned on the roadmap.
Learn more →Compare current capabilities with your requirements. Planned channels and integrations are listed separately on the roadmap.