A subscription database holds names, addresses, payment history and marketing consent for thousands of people. It's exactly the kind of system that should be locked down properly, and exactly the kind that often isn't: shared logins, everyone with admin rights, and no way of telling who changed what.
Avio takes the opposite approach. Strong login, tight permissions and a full trail of what happened. And because publishers change their products all the time, the set-up is in your hands, not stuck in a developer's queue.
Two-factor login for everyone
Every user logs in with a password plus a one-time code from an authenticator app. Not optional, not just for admins. If a password leaks, it isn't enough on its own.
Permissions that fit the job
Avio has around 60 permissions, so each user sees and does only what their role needs. A customer service adviser doesn't need the same access as your finance manager, and in Avio they don't get it. Removing a free order and removing an invoiced one are separate permissions, because they matter to different people.
User accounts can be set to expire, which is handy for temps and contractors: the access ends when the contract does, even if nobody remembers to switch it off. A users and permissions report exports who can do what, ready for your next security audit.
A searchable audit trail
The event log records logins, failed logins and changes to orders down to the field, with the operator who made them. Filter by the last month, three months, a year, five years or everything, and search within it.
So when a customer says their subscription was cancelled without their say-so, you can see exactly when, and who did it. When an auditor asks who has access and who used it, you've got the answer.
The work queue
Customer service requests get tracked from request to resolution. Each task records its type, the product, who raised it and who it's waiting on. Every task keeps a full update trail and can carry attachments, so the email from the customer sits with the task.
Record locking stops two people working the same case at once, and open work shows on the dashboard, so nothing sits forgotten in someone's inbox.
Configure Avio to your business
Publishers launch titles, change prices and restructure brands. None of that should need a developer. In Avio, your administrators manage:
- Brands and companies: several companies or brands, with products, product families, types (journals, events, gifts, lists and web products, for example) and classifications.
- Prices: prices by currency, plus bundle prices.
- Circulation codes: status codes, subscription types, sales channels, opportunity types and prospect statuses.
- Data capture: demographic question sets at person, address, product or price level, plus record sources, next actions and communication types.
- Geography: world regions, countries and sales regions.
- Finance settings: currencies and rate history, VAT rates and rules, and payment, refund and write-off types.
Multi-brand without the mess
Running several brands from one system means one customer record across all of them, while each brand keeps its own identity. Marketing preferences are held per brand, products sit in their own families, and each brand or company has its own invoice template. See finance for how invoices and payments work.
The people behind it
Security isn't only features. As a company we hold Cyber Essentials certification, and our in-house UK development team works with AI coding tools under tight human control. Our post on quality over AI in B2B publishing and the how we build page say more about how we work.
How it fits with the rest
The same principles apply to the Avio API: read-only, scoped keys, rate limited, every call logged. And everything your team does on a customer record lands in the event log.
Book an Avio demo and we'll show you the permissions and the audit trail.
Questions
Is two-factor authentication optional?
No. Every user logs in with a password plus a one-time code from an authenticator app.
Can we limit what each person can do?
Yes. Around 60 permissions control what each user can see and do, and accounts can be set to expire.
Can we see who changed an order?
Yes. The event log records logins, failed logins and changes to orders down to the field, with the operator, and it's searchable.
Can one Avio set-up run several companies or brands?
Yes. You can set up several companies or brands, each with its own products, prices and invoice template.
Do we need a developer to add a new title?
No. Products, prices, issue schedules, codes and demographic questions are all managed on screen by your own administrators.