Notifications
ITS tells your administration when something concerns it: a declaration touching your territory, an office code your register does not carry, a problem with your integration, a rule the Secretariat has changed. The bell in the header shows the latest; the notification centre keeps everything.
Who receives what
A notice is addressed to an organisation, not to a person. Everybody in your organisation whose account may see it gets it, including a colleague who joins next month, who sees the history too. Whether you have read a notice is recorded for you alone: marking it read does not mark it read for your colleagues.
| You are | You are told about |
|---|---|
| The Secretariat | Declarations and adoption across the continent, notices addressed to the Secretariat itself, and the rule and limit changes it has made. When a problem with another organisation's system is urgent, the Secretariat also gets its own copy of that notice, naming the organisation. Other notices addressed to another organisation, such as its less urgent refused requests or its own onboarding steps, go to that organisation only; the Secretariat reads those in Failed transmissions and Reports › Integration |
| A State Party or a REC | Declarations touching your territory, register corrections you can make, problems with your own integration, and changes to the rules and limits that apply to every organisation |
Some notices also depend on your role. Expect it at your frontier, which tells a country a consignment is heading its way, goes only to accounts that stamp at that frontier (customs officers), not to administrators or the Secretariat. Changes to rules and limits go to each organisation's administrators.
The bell
Select the bell in the header to see the six latest notices. Its number is labelled Needing attention: it counts the notices that need something done, not every unread one, so it can differ from the unread count in the centre. The number turns red while any unread notice is urgent. Routine notices of a category you have turned off are left out of the bell; see Choose what reaches you. See also Find your way around.
Open the notification centre
- Select the bell, then View all notifications.
- Or open All areas and select Notifications under Operations.

The page describes itself as Everything ITS has told your administration: declarations touching your territory, register corrections you can make, and problems with your integration.
Each notice
| Part | What it shows |
|---|---|
| The tint and the dot | An unread notice has a tinted background and a dot before its title: red for an urgent notice, amber for one needing attention, grey for information. Both go when the notice is read |
| The title | What happened, for example KEMBATD2609281 was stamped by Uganda |
| The sentence under it | More detail, for example Uganda recorded a customs act against transit declaration KEMBATD2609281. |
| When | How long ago, such as 4 hours ago or yesterday |
| The severity | For information or Needs attention. The most serious notices show a red Urgent tag instead |
| The category | One of the six categories below |
| Mark as read | On unread notices only. See Mark notices read |
Urgent notices
An urgent notice is about something that can hold up cargo or stop your integration: for example, requests from your system that ITS is refusing, or announcements ITS cannot deliver. It has a red edge and a red Urgent tag, and it keeps both after you have read it, because reading it does not fix what it is about.
The Severity filter and the notice's own page call the same severity Failing.
The categories
| Category | What it is about |
|---|---|
| Declarations | A declaration touching your territory was lodged, stamped, sent on to you, corrected or closed |
| Register | A declaration names one of your offices that your customs office register does not carry. See Customs offices |
| Onboarding | An organisation's progress towards connecting its system |
| Integration | Your system's calls are being refused, or ITS cannot deliver announcements to it |
| Adoption | Which countries on a corridor are, or are not, connected to ITS |
| Rules and limits | The Secretariat has changed a rule or a limit that applies to every State Party and REC. See Rule and limit changes |
Filter the list
| Filter | Options |
|---|---|
| Status | All or Unread |
| Category | Any category, or one of the six categories |
| Severity | Any severity, For information, Needs attention or Failing. Failing finds the notices the list tags Urgent |

The list shows ten notices per page, newest first. Items per page under the list changes that.
Under the list, the count reads like 1–10 of 2,337 notifications. On a very long feed ITS stops counting at ten thousand, and the count reads 1–10 of 10,000+ notifications: the page numbers then stop at the last one counted, and Next keeps working until the last page.
Open one notice
-
Select the notice, in the centre or in the bell.
Its own page opens, with When, Severity, Category, About and, for an integration problem, the Correlation id to look up in Failed transmissions. Opening a notice marks it read.
-
Select Open to go to what the notice is about, such as the declaration.
A notice with nothing to act on has no Open button. It says This one is for information. There is nothing to do about it here.
-
Select Back to notifications to return to the list.
A notice about refused requests has no page of its own: selecting it opens Failed transmissions directly.
Mark notices read
Reading is recorded for you alone. None of these changes anything for your colleagues, and none can be undone.
- One notice. Select Mark as read at the right of an unread notice, in the centre or in the bell. Use it when you have already dealt with what the notice is about and do not need to open it.
- Every notice. Select Mark all read, at the top right of the centre and of the bell's panel.
- The notices about refused requests. Select Mark as read on the strip at the top of Failed transmissions.
The tint, the dot and the Mark as read link disappear from a notice that has been read.
Choose what reaches you
You can turn off the routine notices of a category, in the app, by e-mail or both. The choice is yours alone: it changes nothing for your colleagues.
-
In the notification centre, select Notification settings, at the top right beside Mark all read.
The Notification settings window opens: Choose what reaches you in the app and by e-mail. Anything that needs your action always arrives. It has one row per category, each with a sentence saying what the category is about, and two switches, In-app and E-mail.

-
Turn off the switches of what you do not want to receive.
-
Select Save. The portal says Notification settings saved.
To leave without saving, select Cancel. If you have changed a switch, the portal asks Discard your changes?: select Discard changes to leave, or Keep editing to go back.
| Switch | Turned off |
|---|---|
| In-app | The category's notices For information no longer appear in the bell, are no longer counted as unread and are left out when you filter on Unread. They are still in the notification centre under All, and still open. A notice that Needs attention or is Failing always arrives, whatever you choose |
| The category's routine e-mails stop. Only Onboarding has one you can stop today: the e-mail about your organisation's progress in the Sandbox. Every other row shows its E-mail switch on and locked: Locked e-mails always arrive and can't be turned off. |
The e-mails that ask an administrator to act, and those about admission, certification, production access or a one-time sign-in code, always arrive.
If your e-mail choices cannot be read at that moment, the window says Your e-mail choices could not be loaded just now, so the e-mail switches are hidden. Your in-app choices can still be saved.
| Row | What its sentence says it covers |
|---|---|
| Declarations | Routine movement of the transit declarations on your corridors: lodged, amended, stamped |
| Register | Customs offices named on declarations that are not in your register |
| Onboarding | Progress of your organisation's onboarding and sandbox testing |
| Integration | How your systems' exchanges with ITS are going |
| Adoption | Countries on a corridor that are not yet connected to ITS |
| Rules and limits | Rules and limits the AfCFTA Secretariat sets for every organisation |
When the list is empty
| What you see | What it means |
|---|---|
| Nothing yet | Nothing has been addressed to your organisation yet |
| Nothing matches those filters / Widen the filters to see the rest of the record. | The filters hide everything. Set them back to All, Any category and Any severity |
Refused requests
When ITS refuses requests from your organisation's connected system, it tells you once per problem, not once per request. One problem is the same request, refused with the same error code, on the same UTC day.
The notice is headed like 12 requests from your system to PUT /api/v1/etd/{serial_no}/endorsements/{stamp_type} refused with VAL-ETD-003 on 9 Oct 2026 (UTC). Its category is Integration.
| What you notice | Why |
|---|---|
| The count in the title grows, and a notice you had read is unread again | ITS keeps one notice per problem and updates it each time more requests are refused. It becomes unread again so that you see the problem is still going on |
| Some of these notices are Urgent and others Needs attention | The notice has the urgency of the refusals it counts. See Urgent or Needs attention |
| The Secretariat's notice names an organisation where yours says your system | When a problem is urgent, the Secretariat gets its own copy naming the organisation |
To act on one:
-
Select the notice.
Failed transmissions opens, already filtered to that error code, that day and that request and, for the Secretariat, that organisation. The notice is marked read on the way.
-
Open a refusal in the list to read which fields were wrong and the correlation ID your system's logs carry. See Open one refusal.
Your colleagues' use of the portal is never counted in these notices.
When requests from your system have been refused, those notices sit at the top, tagged Urgent or Needs attention and Integration, above the declaration notices. The screenshot shows a day with none.

A notice that a declaration was lodged reads Kenya lodged transit declaration KEMBATD2609281, whose route includes your country.
Rule and limit changes
When the Secretariat changes a rule or a limit on Settings, ITS tells the administrators of every LIVE State Party and REC, and the Secretariat itself. The notices are in the Rules and limits category. The State Parties and RECs are also e-mailed; the Secretariat is not. A State Party or REC still in the sandbox is not told. See How you hear about a change.
| Notice | Severity | What Open does |
|---|---|---|
| Intake limit changed: and the name of the limit. The sentence gives the moment (UTC day and time) the change applies from, the limit from then, and what it was | Needs attention when the limit was lowered, otherwise For information | Opens Settings at that limit |
| Transit rule tightened: or Transit rule relaxed: and the name of the rule | Needs attention when the rule was tightened, otherwise For information | There is no Open button. Open Settings from All areas to read the rule |
A lowered limit matters to your customs system's team: a declaration over the limit is refused when it is lodged, and on any amendment that changes it.
Other languages
Times such as 5 hours ago follow the language the portal is set to. A notice whose title and sentence have not been translated reads in English, whatever the language.
Related pages
- Find your way around
- Failed transmissions
- Settings
- Start your day as a State Party
- Notifications, for Portal notices and machine reconciliation routes