Roles and permissions
Roles determine which protected areas and actions an account can access. The application checks the role before granting access.
Who can see what? What content does the assistant use? Here are the features that help answer those questions.
Roles determine which protected areas and actions an account can access. The application checks the role before granting access.
You can set up an authenticator app for an account. With two-factor sign-in enabled, signing in requires a one-time code in addition to the password.
Signed-in users can export the data stored for their own account as JSON.
Write to us to ask about deleting specific data. Include only the information we need to identify the records involved.
Your team maintains the entries and documents used to find answers.
For requests classified as sensitive and subject to EU routing, the AI router checks the provider and destination. If it can’t use an eligible provider, it stops the request.
Start with your team’s responsibilities. Who handles incoming requests, who only sees details needed for appointments, and who can change settings? Walk through those cases together. A role should let people do their work and reflect their responsibilities. Give each person their own account for handoffs so their sign-in stays tied to their role.
You can set up an authenticator app for sign-in. Plan for what happens when someone changes devices. When handling data access questions, distinguish the user’s own account from other records held by the business. The JSON export applies to the signed-in account. For questions about other data, describe the relevant process or account briefly.
Start by putting in content your team wants to use for answers. Opening hours, general services, and straightforward instructions for inquiries are good starting points. Decide who maintains the information and which versions apply. Ask about one of those topics and check whether the answer matches your source.
AI routing depends on how the request is classified and the policy selected. For sensitive requests subject to EU routing, the router checks the provider and destination before making the call. If no eligible connection is available, the request ends with an error. In a conversation, we can look at a specific workflow and discuss which data your team actually needs to handle.
You can set it up per account. Decide which responsibilities in your business call for the additional one-time code and how to handle device changes.
The authenticated data access export provides data about your own account as a JSON file. For a question about another record, use the contact address and describe the relevant matter.
Write to the contact address on this page and tell us what the request is about. Wait until we ask for any additional documents needed to identify the records.
Your team adds entries and documents to the knowledge base. Assign someone to maintain it and check important answers against an example you choose.
For a sensitive request classified under that policy, the router stops the process. The check applies to that particular AI call. Choose a specific workflow for the demo so we can discuss it together.