Client PortalManaged IT for industry associations
IT Support for Industry Associations and Member Bodies
An association is held together by a list. Who is a member, what they paid, when it lapses, what they are entitled to and how to reach them. Lose that list, or let the wrong person into it, and there is no organisation left to run.
Which is awkward, because most industry bodies are not-for-profit organisations run from a small Melbourne office by a handful of permanent staff, alongside a committee that changes every year.
Want the number first? Our pricing is published: AgileCORE from $85 and AgileCOMPLETE from $130 per user per month ex GST, plus the AgileSECURE add-on at $44. Estimate your monthly figure in two minutes, or book a conversation.
The structure that causes the trouble
Four rings of access, and most associations only manage the outer one
Almost every association we look at has the same shape. There is a public face, a members-only layer, the systems the staff run the organisation on, and a very small number of people who can change anything. The outer ring gets attention because the public sees it. The inner rings are where the risk actually sits.
Public
The website, the events calendar, the contact form. Everyone can see it, so everyone notices when it is wrong.
Members
The portal, the directory, member resources, CPD records where you keep them. Each member should see their own material and the shared material, and nobody else's.
Staff and committee
The membership database, renewals, finance, the mailing list, the event registrations. This is where people are added quickly at busy times and removed slowly, if at all.
Administrators
Whoever can change the above, reset a password, export the whole list or delete it. In a surprising number of associations this is one volunteer, and sometimes a former one.
Drawn like that, the work is obvious: each ring has to be separate from the one inside it, and somebody has to own the question of who sits in each. That is most of what we do for an association, and it is rarely what the conversation starts with.
Every year, on purpose
Your organisation hands itself over to new people once a year
A committee rotates. A treasurer steps down, a secretary takes over, a president finishes a term. In a company this would be a carefully run transition. In an association it happens at an annual general meeting, often among volunteers, and the technology side of it is usually a list of passwords in an email.
What goes wrong is predictable. The outgoing treasurer keeps access to the finance system because nobody asked for it back. The social media account is still tied to someone's personal login from four committees ago. A file nobody can open is on a laptop that left with a past secretary. The association has no record of who holds what, so it cannot hand anything over cleanly even when everyone involved is trying to.
This is a solvable problem and the solution is boring. Accounts belong to the organisation rather than to a person, roles are granted to the office rather than to the office-bearer, handover is a checklist that runs every year, and there is a record of who had what and when it ended. Done once, it makes every subsequent AGM a formality.
Two things members notice immediately
The list is personal information, and the email has to arrive
Member records are personal information, and whether the Privacy Act applies to your association depends on its turnover and what it does. Our compliance obligations page sets out what applies to Victorian organisations. Either way, members assume you are looking after their details, and that assumption is doing a lot of work.
The second one is less obvious and more irritating. An association sends mail to a large list, which is exactly the pattern that gets filtered. If your renewal notices are landing in junk, members do not renew and nobody tells you why. That is a technical problem with a technical fix: the sending records on your domain configured properly, the platform you send through authorised to send as you, and someone watching whether the mail is actually being delivered.
What we check first
- Who can export the full membership list, and whether that is logged
- Whether the member portal separates one member's data from another's
- Whether a restore of the membership database has ever been tested
- How quickly a departing committee member loses access
- Whether your domain is set up so your mail is trusted
- Whether anyone would notice a sign-in from somewhere unusual
AgileSECURE delivers these controls aligned to the SMB1001 maturity framework.
Scope
What we take responsibility for
Agreed in writing on day one in a Responsibility and Accountability Matrix, which for an association doubles as the document a new committee inherits.
The membership system
The platform your member database, renewals and event registrations run on, monitored and backed up, with restores tested by performing one, and the vendor relationship handled so your general manager is not the escalation path.
Access, by office rather than by person
Microsoft 365 and identity managed so roles belong to the position, joining and leaving run as a process at every committee change, and administrator access is deliberate, listed and small.
Reaching the membership
Domain and sending records configured so your mail is trusted and arrives, monitoring for the mailbox changes that precede impersonation, and controls aligned to SMB1001 through AgileSECURE.
Published pricing
AgileMANAGED: structured IT from $85 per user / month
We publish our pricing because an organisation that has to put a budget to a committee deserves to know the number before the first meeting, not after the third.
AgileCORE
Remote support, monitoring, security baselines and Microsoft 365 management. The usual fit for an association with a small permanent staff.
View AgileCORE →AgileCOMPLETE
Everything in CORE, plus onsite support, managed servers with 24/7 monitoring, and quarterly business reviews that give a committee something to read.
View AgileCOMPLETE →Where we work
Based in Mornington, working with bodies based in town
Agile IT Solutions has been based in Mornington since 2007.
Many of the industry bodies we deal with keep their secretariat in or near the CBD, close to the members and the venues they use. Most issues are resolved remotely, which suits an organisation whose committee is scattered across the state, and onsite support across our service area is included with AgileCOMPLETE.
If you would rather see how we work before talking about your own organisation, our case studies set out what we actually did and what changed.
Questions
IT questions from associations and member bodies
Our committee changes every year. How do we stop access walking out the door?
By making accounts belong to the organisation rather than to a person, and by granting access to the office rather than to the office-bearer. Then a handover is a change of who holds a role, not a transfer of passwords. We run the joining and leaving as a standard process at each committee change and keep a record of who held what and when it ended, so the association can always answer that question even years later.
Do you support our membership or association management platform?
We do not write it and we are not its consultant. We take responsibility for everything underneath it: the platform it runs on, the data, the backups, the devices and the identities that reach it, and the vendor relationship when something needs escalating. When the fault sits in the application, we deal with that vendor rather than handing you back a ticket number.
Our renewal emails keep going to junk. Can that be fixed?
Usually, and it is more common than people expect, because sending a lot of mail at once to a large list is exactly the pattern filters are built to catch. The fix is to configure the sending records on your domain properly, authorise the platform you send through to send as you, and then actually watch delivery rather than assume it. Associations often lose renewals to this without ever learning that is what happened.
Much of our work is done by volunteers. Does that change anything?
It changes the process, not the standard. A volunteer needs access that matches what they actually do, for as long as they are doing it, and the organisation needs a record of it. What does not work is treating volunteers as a special case that the normal rules skip, because that is how an association ends up with people holding access years after they stepped back. We will make it simple enough that it does not become a burden on people giving their time.
We are a small secretariat. Are we big enough to bother?
Association size is a poor guide here, because the thing you hold is out of proportion to your headcount. Four staff can be custodians of several thousand members' personal details, their payment history and their professional records. If that describes you, the question is not whether it is worth managing properly, it is who is doing it now. We work best with organisations of roughly 5 to 50 staff, and we will tell you plainly if you are not there yet.
How do we get started?
A discovery conversation, ideally with whoever runs the office and one committee member, because the two see different halves of the problem. We work out what you run on today, who can reach what, and where the gaps are, then set out what a structured managed service would look like. No obligation and no quote pushed at you in the first meeting.