Notifications, errors and audit
Notifications
The bell in the console lists what needs attention: new AWS referrals, SLA reminders, deals that need information, AWS decisions and failed syncs. The same notice goes out at most once a day, so a problem that keeps recurring does not flood anyone. Two more places can receive them, both under Settings → Notifications.
Going to what a notice is about
Click a notice's title to open what it is about. Opening it also marks it as read.
| Notice | Opens |
|---|---|
| A deal needs information, failed to sync, or has AWS's review outcome | The deal |
| An AWS referral, a reminder about it, or a failed acceptance | That invitation |
| The daily Pipeline health digest | Pipeline health |
| A finished bulk job | Bulk jobs |
| A data export, or a workspace deletion | Settings → Data & privacy |
Open in Partner Central and Open in AWS Marketplace go to the record on the AWS side.
Emails and Slack messages link to the same page. For AWS review outcomes they link to Partner Central, as before.
Clearing notices
- Mark all as read marks every unread notice, not only the ones on screen.
- Clear all deletes every notice in the workspace, for everyone. Admins see it, and it asks for confirmation first. The deals, invitations and errors the notices were about are not changed, and the clearing is recorded in the audit log.
Settings → Notifications opens with where notices go: in the console (always), by email and to Slack, each with where it stands. Workspace admins set up email and Slack there; everyone else sees the overview.
Type an address under Add email recipients and choose Add (or press Enter); paste several at once, separated by
commas. Anything that is not an address stays in the box to be put right. The list holds up to 20 addresses; each row
has a button to remove it, and Save recipients keeps the changes (Discard changes drops them). Mail comes from no-reply@habilelabs.io, under the name CoSell.
CoSell installed in your own AWS account sends from the address given as SenderEmail when it was installed;
without one, notices go to Slack only.
Members of the workspace get notices straight away. Anyone else first gets an email asking them to confirm, and CoSell sends them nothing more until they press Send me these notices on the page it links to. The link works for 7 days. Each address on the list shows as Member, Confirmed or Waiting for confirmation (with when they were asked), or not saved yet until you save. If someone's link expired, save the list again the next day to send them a new one.
Slack
- In Slack, add an incoming webhook for the channel the team watches.
- In CoSell, paste the webhook URL (it starts with
https://hooks.slack.com/services/) and choose Connect Slack. CoSell posts a test message first and saves the webhook only when Slack accepts it. - From then on each notice appears in the channel with a button that opens the page it is about in CoSell, or the opportunity in Partner Central for AWS review outcomes.
The webhook URL is stored encrypted and never shown again. Send test message posts to the channel; Post to another channel takes a new webhook in place of the old one; Disconnect asks first, then forgets the webhook. If a message cannot be delivered, Settings shows why and CoSell tries again with the next notice. If Slack reports that the webhook was removed or the channel archived, CoSell stops posting and asks for a new webhook. Accepting or rejecting a referral from Slack itself is planned for a later release.
Sync errors
Sync errors lists syncs that could not finish, with the category (validation, permission, throttling, conflict…), the message from Zoho or AWS, and the field it concerns.
- Retry runs the sync again, once you have fixed the cause.
- Resolve closes an error that needs nothing more.
CoSell retries temporary problems itself (throttling, timeouts) before it records an error.
The list keeps itself current, so what you see is what still needs someone:
- One row per deal. A deal's newest problem replaces the rows about what it ran into before. You are told about a problem once, not each time CoSell finds it unchanged.
- Setting a deal aside closes its errors. Marking a deal Not for AWS in the review queue closes them at once.
- A daily re-check. Once a day CoSell closes the rows of deals it no longer follows and syncs every deal that is still failing, up to 25 a day. A problem fixed since, in your CRM or in AWS, closes its own row.
- Fields AWS has locked are left out. After launch, and in some review states, AWS refuses changes to certain fields. CoSell sends the rest of your changes and stops offering the locked field until the opportunity moves on, instead of failing the whole update.
Audit log
Every change made in the console and every call CoSell makes on your behalf is recorded, with who, when and what. That covers mapping versions, settings, submissions, invitation decisions, imports and assistant questions. Opportunity data is recorded as field names, not full copies.