Find answers, support paths, and rollout guidance fast
Search the same approved public knowledge source used by AwraIQ. Results stay grounded in published AWRA resources, so buyers, customers, and support teams work from one source of truth.
Product helpImplementationSecurity reviewsBilling & support
Nigeria is digitizing tax administration fast, and "we handle FIRS" has become the most casually thrown-around claim in software demos. What VAT and naira operations actually require of your records, and how to tell a records claim from an integration claim.
The cheapest integration available and the only one that changes behaviour rather than moving data. Six channels, why three topic channels beat one, and the mute problem that makes this look like it is working for months after it stopped.
The feature that removes a daily job: a C2B payment quoting an invoice number attaches itself to that invoice. Collections, disbursements and reversal on your own Daraja credentials — plus the four gaps to plan a payout process around.
A Nairobi build looks competitive against three years of subscription and never prices maintenance or the day the developer becomes unavailable. The four questions, a five-year comparison, and the two cases where building genuinely wins.
One authenticated door instead of a per-vendor list. How the token differs from the HMAC signature, why replay protection matters more through ordinary failure than through attack, and the honest limit on what an inbound event can do.
The connectors here share one shape: they push rather than pull, they are safe to run twice, they stop at two hundred records a run, and the button and the nightly job are the same code. Each of those is a decision worth understanding.
Thirteen templates download and eight import. Which is which, why the other five deliberately have no importer, the dependency order that stops a file failing on row one, and the fifty-row habit that substitutes for a preview.
Every integrations page is a grid of logos, and the tiles are four completely different products with four different failure modes. How to decode any of them with two questions, and which one to connect on day one.
Two independent guards against double filing, retries with backoff, the signed receipt stored on the invoice — and the two gaps a VAT-registered business must decide about before go-live: credit notes, and what a till does offline.
Social sign-in is safe when the provider says the address was verified. Microsoft's directory interface does not carry that field at all, which turns a one-line check into a question about what a corporate username proves.
Fiscal regimes differ enormously in architecture and almost not at all in what they assume about your records. Six data conditions, five of which are configuration decisions made once.
Four storage connectors archive the same documents under the same filenames. Ask each what happens when the name is already taken and you get four different answers — one skips, one refuses on principle, two would replace.
Every refresh clears the tab and writes it again from the first cell. That makes the sheet a reliable mirror and makes anything typed into it temporary — which everybody needs to know before the second week.
Connecting your own email account moves four kinds of message and no others. Password resets and sign-in links keep going through the platform — enforced by the shape of the code rather than a setting.
Signing in with a provider hands you an address and a claim about whether it was verified. Skip the claim and you have built an account takeover that works on anybody whose address can be guessed.
Five connected accounts are tried in a fixed order before the platform sends anything, and a failure at any of them is a fall-through rather than an error. A good design with one uncomfortable consequence.
A valid Notion token that has been shared with nothing can reach nothing, and it reports itself as working. The empty list that produces on the first attempt is the most useful thing about it.
A Slack incoming webhook has no signature, no key and no account behind it. Whoever holds the URL can post to that channel as you, forever — which makes it a credential wearing a link's clothing.
Each register is emptied and rewritten from the first cell on every run, which makes the tab a mirror rather than a record. One obvious cost, one hidden one, and one security property nobody asks about.
A connection can hold an address, be switched on, and have proved it works — three separate facts. Collapsing them into one green tick is how a screen claims something nobody ever checked.
There is no screen for choosing which spreadsheet to export into, and its absence is not an omission. The permission this connector holds cannot open a file it did not create.
Most products disconnect by deleting their copy of the credential. The grant stays live in your account indefinitely — and the difference is which token gets sent back.
Seven providers in this series pin an interface version and only one does it with a date in a header. It is the best of the seven, for a reason that has nothing to do with the format.
Answers to common questions about AWRA OpsHub, inventory, procurement, accounting, and integrations.
Page 2 of 10 · 224 articles
Still need a human answer?
For rollout planning, enterprise procurement, billing, security review, or customer support, share the context and we will route it to the right owner.
We use necessary cookies for secure sessions. With your permission, we also use cookies and browser storage for preferences, analytics, and demo engagement. Privacy Policy
AWRA OpsHub
Cookie settings
Cookie Consent Manager
Necessary cookies stay on for login, CSRF protection, and security. You can choose the optional categories below.
Overview
General Information
AWRA uses cookies and browser storage to keep public pages secure, remember selected preferences, measure website performance, and manage demo engagement prompts.
You can choose whether functional and marketing engagement storage apply. Analytics measurement is always active in this AWRA setup.
These settings apply to AWRA public website experiences such as the homepage, feature pages, pricing calculator, blog, help center, and request-demo page. Authenticated dashboard and vendor portal sessions still rely on required security cookies.
Required
Always active
Functional
Optional
Analytics
Always active
Marketing
Optional
For more context on privacy handling, open the Privacy Policy.
Required Cookies
Required Cookies
Always Active
Required cookies and storage support basic website delivery, secure sessions, request protection, and remembering the consent choice itself.
These cannot be switched off from this manager because disabling them would break login/session behavior, form protection, or the ability to remember the privacy choice you save.
Cookie details
Session security: keeps secure server sessions working while browsing AWRA.
CSRF protection: helps verify form submissions and protect requests.
Consent record: stores the preference decision so the banner does not keep asking after a choice is saved.
Examples: Laravel session cookies, CSRF tokens, and the AWRA consent preference record.
Duration: session security can expire with the browser/session; saved consent can last longer so the same browser remembers the choice.
Functional Cookies
Functional Cookies
Functional storage improves the public website experience by remembering interface choices, helper states, dismissed notices, and short-lived interaction preferences.
Turning this off does not stop secure required cookies or analytics. It only limits optional convenience memory.
If disabled, AWRA may show some helper prompts again or forget non-essential display choices. Core public pages, contact forms, and request-demo forms still work.
Cookie details
UI preferences: remembered display choices and helper states where available.
Dismissed notices: session-level or preference-level memory for notices the visitor has closed.
Frequency helpers: optional browser storage that prevents repeated prompts when allowed.
Examples: localStorage or sessionStorage values for dismissed banners, guide/helper states, and lightweight public-page preferences.
Effect when off: AWRA avoids optional convenience memory unless it is also allowed through marketing and engagement preferences.
Analytics Cookies
Analytics Cookies
Always Active
Analytics helps AWRA understand public page performance, traffic patterns, and content usefulness so we can improve the marketing website.
This category does not by itself enable demo popups, exit-intent prompts, or advertising pixels. Those are controlled by Marketing & engagement.
In this AWRA setup, Google Analytics and Google Tag Manager measurement are treated as mandatory website measurement and remain active.
Cookie details
Google Analytics / GTM: measures aggregate traffic and page activity.
Performance insight: helps identify which public pages, docs, and demo paths visitors use.
Operational signal: supports website quality decisions without enabling demo popups by itself.
Examples: Google measurement identifiers such as GA/GTM tags and related browser identifiers set by Google scripts.
Use: page views, source/referrer trends, public content performance, and product education page effectiveness.
Marketing & engagement
Marketing & engagement
Marketing and engagement storage supports demo prompts, exit-intent prompts, campaign attribution, and future advertising pixels.
When disabled, AWRA will not auto-open demo or exit-intent popups. CTA buttons can still open a form because that is a direct visitor action.
When enabled, AWRA can remember that a visitor already saw, dismissed, or submitted a demo prompt so the same popup is not repeated aggressively.
Cookie details
Demo prompt memory: tracks whether an auto prompt or exit prompt was recently dismissed.
Demo submission memory: avoids asking again after a visitor submits a demo request.
Campaign context: keeps source page, referrer, and UTM context available for demo requests.
Examples: popup frequency caps, demo-submitted flags, engagement source fields, and UTM/referrer context.
Effect when off: auto demo prompts and exit-intent prompts stay blocked; normal navigation and manually clicked CTA buttons still work.