A scheduled task runs without you, so nobody is there to press a button when it wants to use one of your connectors. Before a task is scheduled, saved or resumed, and whenever its instructions change, Bluedeer checks which of its actions would normally ask you first. If there are any, it shows a card called This task needs permission. The phone shows the same card.
What the card lists
The card lists only the actions the task cannot yet do on its own. Each row has the action's name and one sentence that says why it is listed.
A connector tool is listed when its rule is Ask first. Tools that only read information start at Don't ask, so the card leaves them out unless you changed their rule. To see the tools of a connector and their rules, open Settings → AI & Chat → Connector permissions. It shows the connectors of the workspace you have selected.
Allow the actions
- Allow all sets every action the card can allow to Don't ask. This applies to this task only. When the task runs, it can use those actions without stopping.
- Also don't ask in chats is a switch. It appears when at least one action can be allowed. Turn it on before you press Allow all, and the same actions are set to Don't ask in your chats too. If you leave it off, Bluedeer still asks you in chats.
- Cancel changes nothing. The task is not scheduled, saved or resumed.
If the task also sends its results to teammates, the card asks you to agree to that as well. It says which teammates will get access to the task and the artifacts its runs make. You agree once, and later runs send results to them without asking again. The button then reads Allow all and share, and one press allows the actions and agrees to the sharing. See How do I run, pause, edit or cancel a task?
When none of the listed actions can be allowed, the button reads Schedule anyway, Save anyway or Resume anyway instead. If the only thing left to agree to is the sharing, it reads Share and schedule, Share and save or Share and resume. The steps that cannot be allowed are then skipped.
When a task's instructions change
What you allowed a task to do on its own was allowed for what the task did then. When its instructions change, those permissions are put on hold until you allow them again. This holds however the instructions change, including when the assistant changes them in a chat. It protects you from text planted somewhere the assistant reads, for example in an email or a web page, that tries to rewrite a task so it acts without asking you.
- When you change the instructions, yourself or by asking the assistant, the same This task needs permission card appears. It lists every action the task was allowed to do on its own. Allow all saves the new instructions and allows the actions again. Cancel changes nothing: the task keeps its old instructions and its permissions.
- When someone else changes the instructions of a shared task, its permissions are removed. The task then skips those steps and asks you in your inbox, as described below, until you allow them again.
Renaming a task or changing only its schedule doesn't touch its permissions.
Steps that cannot be allowed
The card lists these under These steps will be skipped and reported, with the reason. A step stays skipped when:
- The connector tool is turned off, or its connector is not allowed in the workspace. The card says "this connector tool is not available."
- The workspace does not allow it. For example, only the owner and admins can notify everyone, notices to everyone may be turned off, or assistants may not notify teammates. A task can still send you a notice. In a personal workspace, notifying everyone and sharing with a teammate are not allowed, because there are no teammates.
- Only the task's owner can allow it. If someone else is looking at the task, they see the step but cannot allow it.
- Scheduled tasks cannot do it on their own. Some actions are never run without you, whatever your rules say.
A task also never sends an email that is already sitting in your mailbox as a draft. You may have written that draft yourself, and Bluedeer has not shown it to you, so in a chat it always appears on a card for you to review first, whatever your rule for sending email says. A task's run has nobody to review it, so the draft is not sent. The run says: "A draft in the mailbox is sent only after the person has seen it, and nobody is here to review it, so it wasn't sent. They can ask for it in a chat and send it from the card."
Steps that reach people outside the organization
In a shared workspace, some steps cannot wait for a card that nobody is there to answer, yet must not run unseen: sending a file to someone outside the organization, or any message, invitation or share to someone outside when the workspace owner or an admin turned on Always ask before anything goes to people outside the organization. Outside means anyone who is not a member of the workspace and not on one of its verified domains. These steps ignore Don't ask, including the permissions you gave the task. See What are action confirmations and approval cards?.
Instead of skipping the step, the run waits for you, the task's owner:
- The run's status is Waiting for approval, and its history reads, for example, "Waiting for you: Send email" with the reason.
- You get a Needs your attention item in your Inbox, a notification and an email. Open it on the web or the phone and select Approve or Refuse. Only you can answer it; nobody else in the workspace sees it.
- If you approve, Bluedeer checks the workspace's rules again, then carries out the step with your account. If a rule now refuses it or sends it to an approver, nothing is sent.
- If you refuse, or nobody answers within 24 hours, nothing is sent and the run's history says so.
- While one step waits, later runs of the same task do not ask again for the same action. Their history says that an earlier approval is still pending.
When a connector is off or disconnected
- A built-in service that you disconnect stops working for your chats and tasks until you connect it again. The disconnect dialog warns you about this. See How do I disconnect a service?
- A custom connector that you remove takes its tools with it. A task that used them skips those steps. See Manage a custom connector's tools
- A service or connector that is not allowed in a shared workspace. An owner or admin does this in the workspace's Connectors tab. Whatever kind of connector it is, everyone is signed out of it, its tools stop straight away, and tasks skip those steps. Allowing it again doesn't sign anyone back in: each person connects it again. See Choose which connectors a workspace allows
A task never waits for a connector to become available again. It skips the step, and its results say what was skipped.
When a task skips a step
When a run reaches a step it is not allowed to do, it skips that step. The run's result lists the skipped step and says that it needs your permission to run in this task.
Bluedeer also adds an item to your inbox under Needs your attention. It is labeled Needs review and titled with the task's name and the action, such as "Weekly report needs permission for Send email". There is one open item per task and action, so a task that runs every hour does not fill your inbox with duplicates. The item stays until you allow the action.
To fix it, open the item and press Allow for this task. Then press Run again to run the task. For what the inbox shows, see Where do task results and notices appear?
Where these rules are kept
The rules that a task has are listed in Settings → AI & Chat → Action confirmations, under Chats, pages and tasks with their own rules. Select Remove to take a rule back. The task then asks again the next time it needs the action.
For the full picture of approval cards and rules, read What are action confirmations and approval cards?