Some actions change things outside Bluedeer or cannot be undone, such as sending an email, deleting a file, sharing with a teammate or running a tool of one of your connectors. Before these run, Bluedeer can pause and show an approval card in the chat. Access checks and the other service's permissions always apply.
One rule for each action
Every action that can ask for approval follows one rule, with two options:
- Ask first: Bluedeer shows an approval card and waits for you.
- Don't ask: Bluedeer runs it without a card.
The same rules apply to built-in actions, to sharing with teammates, and to the tools of your own connectors. Every action of a connector that changes something asks first until you choose otherwise: every built-in app (Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets, Slack, including sending a Slack message) and every custom connector, such as Notion, Atlassian or GitHub. Reading never asks. You see and change all of them in Settings → AI & Chat: Bluedeer's own actions under Action confirmations, and your apps' and connectors' actions under Connector permissions.
Approval cards
The buttons on the card depend on the action:
- For an email, the card lists each attachment with its name and size. Send email, Save draft or Schedule email approves it, and Cancel email stops it. Don't ask again asks you to press it a second time, because later emails will then send without review.
- For a notice, or a file or chat shared with a teammate, the approve button says what it does, such as Send notice, Send to everyone, Share file or Share chat. These cards also offer Don't ask again, which sets that action's rule to Don't ask. Sharing a file or a chat follows one rule, Share with a teammate.
- A notice that points a teammate at something they can't open yet would also give them Can view access to it, so it follows the Share with a teammate rule too: while that rule is Ask first, it asks with its own card, Share and send or Don't send. Its Don't ask again switch sets Share with a teammate to Don't ask.
- For other actions, such as creating a calendar event or moving a Drive file to the trash, the card says what will change, Confirm & Execute allows it, and Cancel stops it. Don't ask again approves it and sets that action's rule to Don't ask.
- For a tool from one of your connectors, Don't ask again runs this tool now and sets its rule to Don't ask. Don't ask before changes for followed by the connector's name, for example Don't ask before changes for Notion, turns on that connector's switch of the same name, so all its tools run without asking, including tools it adds later; a tool you set to Ask first still asks. Either choice also approves the other requests for the same tool (or the same connector) already waiting in this chat and in your other chats in this workspace, as if you had approved each one.
Choosing Don't ask again also approves the action now.
If you leave the same card unanswered several times, the assistant stops showing it again on its own and tells you once what it can't do without it. Ask for it (for example "show me the connect button") and it appears again. The same goes for cards to connect an app or to enter a secret.
When Don't ask doesn't apply: people outside the organization
In a shared workspace, an action that sends or shares a file with someone outside the organization always shows its approval card, even if you chose Don't ask for it before. Its Don't ask again is grayed out; hover over it, or move to it with the keyboard, and it says why. Outside means anyone who isn't a member of the workspace and isn't on one of its verified domains. Members count by the address they sign in with, exactly as written: a teammate's other address, or the same address with a +tag, counts as outside. Someone who was invited but hasn't joined yet, or who was removed, counts as outside; a member without a seat counts as inside, and so does your own sign-in address. A group or mailing list address counts as outside unless it's on a verified domain. The exception is a file going only to people on the workspace's allowed outside addresses: then your usual rule applies.
The workspace owner or an admin can go further with Always ask before anything goes to people outside the organization. When it's on, every email, invitation, share or message that would reach someone outside asks first in the same way, with or without a file. See Workspace rules.
A scheduled task (on a schedule or started by an event) and your own live page can't show a card while they run. When one of their steps would send something outside like this, the step waits for you instead: you get a Needs your attention item in your Inbox, a notification and an email, and you approve or refuse it there, on the web or the phone. Only you, the owner of the task or page, can answer it; nobody else in the workspace sees it. If nobody answers within 24 hours, it expires and nothing is sent, and the task's run says so. While one waits, later runs of the same task don't ask again for the same action: their run says one is already waiting. When you approve it, Bluedeer checks the workspace's rules again first; if a rule now refuses the action or sends it to an approver, nothing is sent. Someone else using your live page can't send such a step at all: it stops and nothing is sent.
This doesn't change anything in a personal workspace. A Slack channel, and a connector tool whose recipient Bluedeer can't identify, follow your usual rules.
Once you decide, the card shows your choice, for example Action Confirmed or Action Canceled, or for an email Email sent or Email canceled. If you do not answer in time, the approval expires and the card says so. The card keeps your choice if you open the chat again later.
The badge follows what happened after you approved, not only your choice. The web and the phone use the same words:
- Action Confirmed appears only for an action that was carried out.
- Not done appears when you approved the action but it was not carried out, because the app refused it or because something it depends on changed after the card was shown. The card says why in a sentence, for example that Google Calendar did not accept the request as it was written. It shows the same sentence when you open the chat again later.
- Outcome needs review appears when Bluedeer could not confirm whether the action happened. Check the other service before you ask again.
- Action in progress appears while an approved action is still running.
After a card ends as Not done or Outcome needs review, the assistant's reply carries on, so it can tell you what to do next.
The step for the action in the reply's thinking section follows the card too. While the card waits, it reads, for example, Asked to send a Slack message, waiting for your approval (or waiting for an approver when a workspace rule sent it to someone else). Once the approval is decided, the same step says what happened: Sent your Slack message, Didn't send a Slack message: you declined, Didn't send a Slack message: the approval expired, or that it didn't finish. This works the same for every app and connector, on the web and the phone, and when you open the chat again later, also after you decided on another device.
Email draft cards
When Bluedeer writes a new email for you, it shows it as an email draft card with To, Cc, Subject and the email itself. Nothing is sent until you choose.
- You can change any part of the card. Your changes are saved a moment after you stop typing, so the card reads the same after a reload and on your other devices.
- Send, Save as draft (a Gmail draft) or Schedule (pick when it goes out; on the phone, choose In an hour, Tomorrow at 9:00 or Monday at 9:00) sends it straight from the card. Pressing one of them is your approval: there is no second question. Bluedeer then tells you in the chat what happened. If the card is inside a thread, the reply continues in that thread.
- Your email signature shows under the email. Select it to change it. The eye beside the pen leaves it out of this one email only, and shows it again; your saved signature stays. See Your email signature.
- A card cannot be sent while a reply is still being written in its chat. Wait for the reply to finish, then send.
- If you change the card and then write to Bluedeer instead of sending, your message tells Bluedeer how the card reads now.
- When you ask for changes, Bluedeer shows a new card. An older card says Newer draft below, and you can still send it.
- A card that was sent keeps that state: it says Email sent (or Saved to Gmail drafts, or Scheduled for a time) and its buttons are disabled; hovering over a button shows that it was approved earlier and sent. If an email didn't go out, the card says why and offers Send again.
- In a shared workspace, a workspace rule can send the email to an approver first. The card then says Waiting for that person, and later whether it was approved and sent, rejected, or ran out of time. See Workspace rules.
- In a shared chat, only the person the email was written for can change or send it, because it goes from their Gmail. Everyone else sees the card as written, read-only: they cannot edit it, add files to it or send it, and approval cards they open in someone else's chat have their buttons turned off. A member without a seat, and a support session, can read a card but not change or send it.
Choose when Bluedeer asks
Open Settings and choose AI & Chat (on the phone, the AI & Chat tab). There are two sections, and the most specific rule wins.
Action confirmations
Never ask before changes is at the top. It is the switch for trusting Bluedeer fully: when it is on, Bluedeer never shows an approval or permission card of any kind. Connector changes, sharing files and chats with teammates, notices, a scheduled task's permissions and sharing your approximate location all go ahead without asking. Live pages are the exception: a live page is written by someone else, so it still needs its own Allow (or Don't ask on this page) from you, even while Never ask before changes is on. Emails, events, files and messages are then created, changed, sent or deleted straight away, so turn it on only if you are sure. Sending a draft that is already in your mailbox is the exception: Bluedeer always shows it on a card first, because Bluedeer may not have seen it. Turn it off to be asked again. An action you set to Ask first still asks. Switches that workspace owners and admins set for everyone still apply.
Below it are Bluedeer's own actions, each with Use default, Ask first or Don't ask: under Teammates and sharing, Notify a teammate starts at Don't ask, and Notify everyone in the workspace and Share with a teammate start at Ask first. Other actions lists any other action you chose a rule for, for example with Don't ask again on its card.
Connector permissions
Every app and connector you connected is listed here, so you can allow any of its actions before Bluedeer ever asks. On the web, this section has two columns:
- On the left is a list of your apps and connectors, each with its logo. Type in Search connectors to find one by name or kind, such as "calendar". A small teal dot marks an app or connector where you chose a rule of your own. With the keyboard, the arrow keys, Home and End move through the list, and typing the first letters of a name jumps to it.
- On the right is the one you chose: its name, its kind and a short summary such as Asks before all 4 actions or Doesn't ask: Send email, then its switch and each of its actions.
Each built-in app (Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets, Slack) lists each of its actions that change something, and these start at Ask first. The email and calendar actions are the exception: they are listed once each, under Email and Calendar, with one choice for each action, whichever mailbox or calendar it uses. Email and Calendar have no switch of their own; an action there that you haven't set yourself follows your apps' own switches when they all say the same. Each of your own connectors in the selected workspace lists its tools that are on: a tool that says it only reads starts at Don't ask, and every other tool starts at Ask first. If nothing is connected yet, the section says so and links to Customization → Connectors.
The first switch is Ask before changes in followed by the name, for example Ask before changes in Google Calendar. It is on by default. Turn it off, and every action of that app or connector that changes something runs without an approval card, including actions it adds later. This is the same rule as the Don't ask before changes for button on an approval card. Turn it back on to be asked again.
Below it, each action has an Ask first switch. On means Bluedeer asks before it, off means it runs without asking. The switch always shows what happens now. When you flip it, that becomes the action's own rule: the row shows a Your rule tag, and the rule stays even if you later change the app's switch or Never ask before changes. To make the action follow those again, select Use default under its name; the text in brackets shows the default, for example Use default (Don't ask). Use defaults at the top undoes every rule you chose for that app or connector at once. Don't ask again on a card changes the same rule.
A switch that cannot be changed right now is grayed out. Hover over it, or move to it with the keyboard, and it says why.
The order of precedence is: a chat's, page's or task's own rules, then an action's own rule, then its app's or connector's switch, then Never ask before changes, then the starting choice. A few cards are themselves a request for permission (a scheduled task's permissions, sharing your approximate location, a notice that would give a teammate access); they always ask, unless Never ask before changes is on. A live page never follows Never ask before changes: only its own rules let it act.
Rules for one chat, page or task
A chat, a live page or a scheduled task can have rules of its own, which win there:
- A chat: on an approval card, select Rules to choose this action's rule across your account or In this chat only.
- A live page: Don't ask on this page lets that page use what it lists without asking (your apps, AI, saving your changes into the files it shows), for you, on that page only.
- A scheduled task: its permissions card sets the actions it lists to Don't ask for that task only.
They are listed under Chats, pages and tasks with their own rules in Action confirmations, on the web and the phone. Select Remove to make one follow your other rules again; a live page then asks again before it uses your apps.
Workspace owners and admins can still turn some things off for everyone, such as notices from assistants. Your rules never override that. On Enterprise, a workspace rule can also refuse an action, or send it to someone else to approve: the card then says Waiting for the approver, and you can cancel it but not approve it yourself.
Scheduled tasks
Nobody can approve an action while a scheduled task runs, so a task does not run an action set to Ask first on its own. A task, like a live page, never sends a draft that is already in your mailbox, because nobody is there to look at it first. Ask for it in a chat and send it from the card. When you schedule, edit or resume a task that needs one, Bluedeer shows a card called This task needs permission. Allow the actions there for that task only. Changing a task's instructions asks you again for every action it was allowed to do on its own. See Let a scheduled task use your connectors