Account access
Use individual accounts, protect sign-in credentials, and remove access when a teammate no longer needs the workspace.
Security and responsible operations
Security depends on the product, your account configuration, the people with access, and every system connected to the workflow.
Share your security or procurement questions with our team. We will respond with information applicable to your planned setup and the current product.
Operational controls
Use individual accounts, protect sign-in credentials, and remove access when a teammate no longer needs the workspace.
Give teammates the access required for their work and review powerful administrative permissions carefully.
Treat WhatsApp, API, webhook, and third-party integration credentials as sensitive operational access.
Review which customer events leave the platform, where they are sent, and who operates the receiving system.
Shared responsibility
Product: Automate Chats provides account and team-management capabilities available in the product.
Your organization: Your organization decides who is invited, which access they receive, and when access is removed.
Product: The platform processes the content and configuration required to operate the workflows you enable.
Your organization: Your organization is responsible for lawful collection, messaging, retention choices, and appropriate customer content.
Product: The platform provides supported connection points such as integrations, APIs, and webhooks.
Your organization: Your organization chooses endpoints, protects credentials, and reviews the security of connected systems.
Procurement checklist
Security answers can change with the capabilities, integrations, and operating choices your organization enables.
We can review how your team plans to use Automate Chats and address questions relevant to that setup.