Skip to main content

What each role can do

Everything you can see and do in the ITS portal comes from two things:

  • your role, a named set of permissions that an administrator puts on your account; and
  • your organisation: the AfCFTA Secretariat, a State Party, or a Regional Economic Community (REC).

The role decides which screens and buttons you get. The organisation decides whose data those screens show. Two people with the same role, one at a State Party and one at a REC, get the same screens with different data in them. This page covers the first. For the second, see the "What you see depends on who you are" boxes in each chapter.

If a menu item or a button in this manual is missing from your screen, your role does not include it. Nothing is broken.

These are the roles as ITS sets them up

System admin and Secretariat admin can change what a built-in role grants, on the Roles screen. The tables on this page describe the roles as ITS first sets them up. If your installation has changed a role, the Roles screen shows what it grants now. System admin itself can never be changed.

The roles people hold​

Role (as the portal names it)Who holds itWhat it is for
System adminAn authorised ITS operator.Every screen, including the roles screen, but no customs act: it reads declarations and never lodges, stamps, amends, attaches, cancels or acknowledges. Nobody can grant it from the portal, and nobody can change it.
Secretariat adminThe AfCFTA Secretariat's administrator.Governance, the rules and limits on Settings, every organisation's connection in System integration, every report, the customs office register for all of Africa, the Consortium ledger, the Audit trail, the roles, and the Secretariat's own users. It reads declarations but cannot lodge or stamp them.
Organisation adminThe administrator of a State Party or a REC.The organisation's own users, its customs offices, its own connection in System integration, every report, and read-only access to declarations, all limited to the countries it administers. It also reads the Consortium ledger and Settings.
PartnerThe technical contact of a State Party or REC.The organisation's own connection in System integration. It usually comes together with Organisation admin.
Customs officerAn officer at a customs station, usually working in a national customs system rather than in the portal.Lodging declarations and stamping them along the corridor. In the portal: reading declarations, Failed transmissions, three report areas and Settings.
Departure authorityThe customs administration of the departure country.Amending and cancelling its own declarations. In the portal: reading declarations, Failed transmissions and Settings.
Most declaration work happens outside the portal

ITS is used system to system. A national customs system lodges, stamps, amends and cancels declarations through the ITS API, not through the portal. The declaration permissions below belong to those systems and to officers whose systems act for them. In the portal a person reads declarations; there is no button to lodge one.

The roles systems hold​

Some roles are not meant for people. They let a connected customs system, or a part of ITS itself, do its job. The portal leaves them out of the role picker, the roles shown on a person and the Roles tab, so you never give one by mistake.

RoleWhat it is
Partner systemA State Party's or REC's customs system calling ITS: it reads declarations, acknowledges what ITS sends it and reads a few reports. Every partner credential issued in System integration carries it, with Customs officer and Departure authority.
Environment access rolesAdmit a system's credential to Sandbox or to Live.
Notification publisher, Reporting publisher, Localization publisher and other service rolesUsed by ITS's own services. They grant nothing in the portal.

One more role grants nothing in ITS: Localization admin lets a person correct a translation of ITS's own text in the translation service. It is listed on the Roles tab, with that description, but no administrator can give it from the portal: it is not among the roles any organisation may give.

How to read the tables​

MarkMeaning
YesThe screen or button is there and works.
Read onlyThe screen opens and you can search and filter, but the buttons that change something are not there.
NoNot shown. The portal hides what you may not use instead of greying it out.
SystemDone by a connected customs system through the API, not in the portal.

Screens​

Overview, Declarations, Reports and Users & roles are in the header. The rest open from All areas, in the group named in brackets.

ScreenSystem adminSecretariat adminOrganisation adminPartnerCustoms officerDeparture authority
OverviewYesYesYesNoYesYes
Declarations list and declaration pagesRead onlyRead onlyRead onlyNoRead onlyRead only
Reports: Transit volumes, Time & delaysYesYesYesNoYesNo
Reports: RegisterYesYesYesNoYesNo
Reports: IntegrationYesYesYesNoNoNo
Reports: WorkforceYesYesYesNoNoNo
UsersYesYesYesNoNoNo
RolesYesYesNoNoNoNo
Notifications and the bell (Operations)YesYesYesYesYesYes
Failed transmissions (Operations)Yes, every organisationYes, every organisationYes, its ownNoYes, its ownYes, its own
Consortium ledger (Oversight)Read onlyRead onlyRead onlyNoNoNo
Track a consignment, Verify a document (Oversight)YesYesYesYesYesYes
Governance (Administration)YesYesNoNoNoNo
Customs offices (Administration)YesYesYesRead onlyRead onlyRead only
System integration (Administration)Yes, every organisationYes, every organisationYes, its ownYes, its ownNoNo
Audit trail (Administration)Read onlyRead onlyNoNoNoNo
Settings (Administration)Yes, two sectionsYesRead onlyRead only, two sectionsRead only, two sectionsRead only, two sections
Translations (Administration)YesYesNoNoNoNo

Track and Verify are public: anyone can use them, signed in or not.

The Consortium ledger and the Audit trail are read only for everybody who can open them: nothing on either screen changes anything.

In All areas, the administrator of a State Party or of a REC has Consortium ledger, System integration and Settings, and does not have Governance, Audit trail or Translations. The Secretariat has all six.

Reports opens on the first area you may read

If your role reads some report areas but not others, Reports shows only the tabs you may open. Each tab opens completely or is not shown, so an empty tile always means "nothing happened", never "you may not see this".

Where you start after signing in​

Your roleThe portal opens on
System admin, Secretariat adminSystem integration
Organisation admin, Customs officer, Departure authorityOverview
Partner, on its ownSystem integration

Declarations​

ActionSystem adminSecretariat adminOrganisation adminCustoms officerDeparture authorityPartner system
Read a declaration, its history and its transit documentYesYesYesYesYesSystem
See Who has been told on the History tabYesYesOnly for its own country's declarationsOnly for its own country's declarationsOnly for its own country's declarationsSystem
Lodge a declarationNoNoNoSystemNoNo
Stamp it along the corridorNoNoNoSystemNoNo
Amend itNoNoNoSystemSystemNo
Attach documentsNoNoNoSystemNoNo
Cancel itNoNoNoNoSystemNo
Acknowledge an announcement from ITSNoNoNoNoNoSystem

The Secretariat, the operator's System admin included, reads every declaration and performs no customs act, not even through the API. That is intended: a customs act belongs to the country that performs it.

Failed transmissions​

Everybody who reads declarations can open Failed transmissions. A State Party or a REC reads the refusals of its own organisation's system. The Secretariat reads every organisation's, with an Organisation column and a filter to choose one. Nobody changes anything on this screen. See Failed transmissions.

Customs offices​

ActionSystem adminSecretariat adminOrganisation adminEverybody else who can open it
Read the register for all of AfricaYesYesYesYes
New office, Edit, Withdraw, reopenEvery countryEvery countryOnly the countries it administersNo
Bulk uploadEvery countryEvery countryOnly the countries it administersNo
ExportYesYesYesNo

A REC administers only the members that have delegated their submissions to it, not every member of the community. See Governance.

Governance​

Only the Secretariat (System admin and Secretariat admin) can open Governance. It records which countries take part, which RECs exist, who their members are and who submits for whom. Organisation admin cannot see it at all.

One effect shows in Reports: a REC's name is read from Governance, so in the Onboarding report a State Party or a REC sees a REC as its code, such as AMU, where the Secretariat sees its name.

Settings​

Everybody who signs in can open Settings and read the rules and limits the Secretariat sets for every State Party and REC. What you see and do there depends on your role.

On SettingsSystem adminSecretariat adminOrganisation adminPartner, Customs officer, Departure authority
Read Declarations (the limits on one declaration)YesYesYesYes
Read Transit rulesYesYesYesYes
Read OperationsNo, the section is not shownYesYesNo, the section is not shown
Open a rule's HistoryYesYesNoNo
Change a value, or Withdraw oneDeclarations and Transit rulesYesNoNo

See Settings.

System integration​

ActionSystem adminSecretariat adminOrganisation adminPartner
See the register of every organisation's connectionYesYesNo. A REC sees itself and the members it submits forNo
Onboard an organisation, approve Live access, suspend, restore or withdraw itYesYesNoNo
Approve a receiving endpoint, or switch back to a displaced oneYesYesNoNo
Open another organisation's review screenYesYesA REC's administrator only, read only, for a member State it files forNo
Work on its own organisation's connection: credentials, addresses, endpointsNoNoYesYes

Only the Secretariat approves. An organisation declares its receiving endpoint, and ITS calls it once the Secretariat has approved it. A REC's administrator reads the review screen of a member State it files for, without the Secretariat's buttons.

See System integration.

Consortium ledger and Audit trail​

ScreenWho can open itWhat they can do
Consortium ledgerSystem admin, Secretariat admin, Organisation adminRead who holds the ledger, its rule and every batch written. Everybody sees the same page.
Audit trailSystem admin, Secretariat adminRead who did what. A State Party or REC administrator cannot open it.

Users​

ActionSystem adminSecretariat adminOrganisation admin
See the organisation's usersYesYesYes
Add user, Edit, including a person's e-mail addressYesYesYes
Bulk uploadYesYesYes
Deactivate and reactivateYesYesYes
Reset second factor of another personYesYesYes
Record a duty station postingYesYesYes

Nobody can reset their own second factor or deactivate themselves. Everybody changes their own second step from the account menu, with Change my second step.

Who may give which role. An administrator can only give the roles their organisation is allowed to give:

The administrator works forThey can give
The SecretariatSecretariat admin, Organisation admin, Customs officer, Departure authority, Partner
A State PartyCustoms officer, Departure authority
A RECCustoms officer

System admin can never be given from the portal. A REC can staff its own ITS entry but not a member's customs service. The role picker offers only the roles you may give. Roles a person already holds that you may not give are listed as Also holds, which you may neither grant nor remove, and saving keeps them.

The last administrator cannot be switched off

ITS refuses to deactivate the last active Secretariat admin or Organisation admin of an organisation, because nobody inside it could then give the role back.

Roles​

System admin and Secretariat admin can open the roles screen, look at what a role grants, create, copy, change or delete a custom role, and change what a built-in role grants. System admin itself cannot be changed, deactivated or deleted. Organisation admin has no Roles tab; typing its address shows You do not have access to this area. No administrator can give a custom role from the portal: the roles each kind of organisation may give are fixed by ITS. See Roles and permissions.

The roles in plain words​

System admin. The operator. Every screen in the portal, and the administration of roles and permissions, but no customs act. Its own role cannot be changed by anyone. On Settings it changes the limits on declarations and the transit rules, and does not see the Operations section. Keep it to the people who run the deployment.

Secretariat admin. The Secretariat's administrator. Governs who takes part and who submits for whom, sets the rules and limits on Settings, admits organisations and approves their connections in System integration, maintains the customs office register on everyone's behalf, reads every report, every declaration, the Consortium ledger and the Audit trail, manages the Secretariat's own people, and looks after the roles. It never lodges, stamps or amends a declaration.

Organisation admin. The administrator of one State Party or one REC. Reads the declarations and reports of the countries it administers, keeps its customs offices up to date, manages its own people and looks after its organisation's connection in System integration. It reads the Consortium ledger and all three sections of Settings, and changes neither. It is the same role for a State Party and a REC. The data differs because the organisation differs.

Partner. The technical contact who connects the organisation's customs system. On its own it opens System integration for its own organisation, the customs office register (read only), notifications and Settings (read only), and nothing else.

Customs officer and Departure authority. Roles for the people and systems that act on declarations: lodging and stamping (officer), amending and cancelling (departure country). Their work happens in the national customs system, which calls ITS. In the portal both read declarations, Failed transmissions for their own organisation, the customs office register and Settings; a Customs officer also reads three report areas: Transit volumes, Time & delays and Register.