Agileday is used for staffing, CVs and project tracking in consultancies. With the Agileday connector the AI agent can find the right people and projects while you write bids, instead of you having to dig them out yourself.
The connector is available on paid plans. You connect with your own Agileday account, and the agent only gets access to what you can already see and do. You use the connector through the agent, so you need the administrator, member or a custom role. Contributors don't have access to the agent. Read more about roles and permissions.
What the agent can do
Look up consultants, skills and CVs you have access to.
Find projects and staffing.
Pull that information into your bid work.
Agileday decides which tools are available, and your own permissions decide what the agent gets to see. You can see the list on the integration card once you have connected.
First: an administrator sets up Agileday
An administrator sets up the connector once for the workspace. Each customer has their own Agileday address. Client ID Metadata Documents (CIMD) let Cobrief identify itself automatically, so you do not need to create your own OAuth client.
Enable access in Agileday
An Agileday administrator needs to complete these steps before users can connect:
Make sure MCP is enabled for your organization.
Go to "Settings" → "Integrations" → "OAuth Clients" and turn on "Enable OAuth".
Under "Limits for self-registering clients", choose the "Maximum role" and "Allowed tools". Select the role and tools Cobrief may use, then click "Save".
Turn on "Client ID Metadata Documents".
Choose who may approve a new client under "Who can approve a new client".
Add
app.cobrief.comunder "Allowed hosts" and click "Save". Enter only the hostname, withouthttps://or a path.
Agileday only allows the exact hostnames listed under "Allowed hosts". cobrief.com does not cover app.cobrief.com. The first user who connects must have the role required to approve a new client.
Enter the tenant in Cobrief
Go to "Settings" → "Integrations", find Agileday and click "Configure".
Fill in "Agileday tenant". This is the part before
.agileday.ioin your sign-in address. You can also paste the full Agileday address or MCP URL. Cobrief extracts the tenant automatically and shows the server URL.Click "Save setup".
You do not need a client ID or client secret with this setup. Each user then connects with their own Agileday account.
Advanced: use your own OAuth client
You can still use a manually registered client:
Open "Configure" on the Agileday card and turn on "Use your own OAuth client (advanced)".
Copy the "Redirect URI" from Cobrief.
Click "Create the OAuth client in Agileday" in Cobrief. In Agileday, open "Settings" → "Integrations" → "OAuth Clients" and click "Add OAuth client". Register the redirect URI exactly as shown in Cobrief.
Paste the client ID back into Cobrief.
Choose "Client authentication". If the client has no secret, choose "Public (PKCE only)". If it has one, choose "Client secret" and paste it in. Under "How the client sends the client secret", select the same method used by the client in Agileday.
Click "Save setup".
If an administrator changes the tenant or switches between automatic setup and a custom OAuth client, everyone in the workspace needs to reconnect. Changes to the client details also require reconnection.
How to connect
Go to "Settings" → "Integrations".
Find Agileday under "Personal" and click "Connect".
Sign in to Agileday and approve access.
When you return to Cobrief, you can see which account is connected.
Connecting from the settings turns the connector on for new conversations. Conversations you have already started keep their current setting. You can also connect from the "Connectors" menu inside a conversation. That turns the connector on for that conversation.
Use Agileday in a conversation
Open the "Connectors" menu in the agent and turn Agileday on for the conversation. For example, you can ask the agent to:
"Find consultants with experience from cloud services in the public sector."
"Who is available from March?"
"Fetch this consultant's CV and adapt it to the requirements in the tender."
Choose what the agent may do
The tools from Agileday fall into two groups: those that only read, and those that can change or delete something. By default the agent may read freely, while anything that changes something needs your approval in the conversation. The agent shows you what it wants to do, and you choose "Approve" or "Reject".
Administrators can change this for the whole workspace under "Settings" → "Integrations" → Agileday. Each group and each individual tool can be set to "Always allow", "Needs approval" or "Blocked". Other users can see the settings but cannot change them.
Disconnect or reconnect
Go to "Settings" → "Integrations", find Agileday and click "Disconnect". The agent then loses access to your Agileday account. You can connect again whenever you like.
If access expires or is revoked, Cobrief shows "Requires new sign-in". Click "Reconnect" to continue.
Administrators can also click "Remove setup" on the Agileday card. Everyone in the workspace then loses their connection, and the connector disappears until the setup is added again.
Security
The agent uses your own sign-in with Agileday and never reaches further than you do yourself. Content is fetched while the agent works, and we don't keep a copy of your Agileday data. Answers and documents the agent produces are stored in Cobrief as usual.
Read more about how we work with security and privacy in our Trust Center.
Can't connect?
If you don't see Agileday under "Integrations", the setup hasn't been done yet. Ask an administrator to configure it.
If you see "This client is not permitted for this tenant", ask an administrator to check that CIMD is enabled and
app.cobrief.comis listed under "Allowed hosts" in Agileday. Also check who may approve a new client.If you use your own OAuth client, check that the redirect URI is registered exactly as shown in Cobrief. "Client authentication" must also match the Agileday configuration.
If the setup was changed recently, you need to connect again.