Owners & access

A common worry when committees first consider a shared portal is that everyone will suddenly see everything — private discussions, sensitive disputes, financial detail. Page-level permissions exist to prevent exactly that.

How it works

• Each page (documents, maintenance, compliance, Committee Hub, meetings, and so on) can be switched on or off for a given seat
• Owners without a committee or manager seat see only what the committee has explicitly opened up to them
• A strata or building manager's seat can be scoped to whatever the committee wants them to see — full visibility, or just specific pages like maintenance and compliance
• Contractors can be invited into a single Committee Hub thread without any broader portal access at all

Typical access patterns

• Committee members: full access to committee-facing pages, aside from anything the committee itself decides to restrict
• Owners: documents (selected categories), notices, meeting minutes, and shareable request forms — rarely Committee Hub or the compliance register
• Manager: whatever the committee agrees to, commonly maintenance, compliance and documents, sometimes read-only

Why granular beats all-or-nothing

A binary "owner" versus "committee" split forces uncomfortable trade-offs — either owners see nothing useful, or they see everything including sensitive committee discussion. Page-level control lets the committee be as open or as conservative as suits the building, and adjust it over time without an all-or-nothing migration.

Changing access

Access can be changed at any time as roles change — a new committee member, a departing manager, or simply the committee deciding to open up a page it previously kept closed.

Owners often assume a shared portal means full visibility into everything the committee does. In Flex Strata, visibility is deliberately set by the committee rather than defaulted to "everything."

Commonly opened up to owners

• Selected document categories, most often by-laws, minutes and insurance certificates
• Notices sent to the building or their lot
• Meeting minutes once finalised
• A shareable request form for raising a maintenance issue or general request

Commonly kept to the committee

• Committee Hub discussion threads
• The compliance register's day-to-day working detail
• Contractor register and quote comparisons
• Internal spend approvals and audit log detail

Why this split works

Owners are entitled to certain records under their state's legislation, but the committee also needs room to discuss and decide things candidly before a position is settled. Keeping the working detail private while opening up the outcomes and required records strikes a workable balance most committees land on.

Adjusting the balance

Some committees choose to be more transparent than the minimum — opening up more document categories, for example — while others keep access tighter and rely on notices for owner communication. Flex Strata doesn't mandate either approach; the committee sets it based on what suits the building and its owners.

A note on legislated rights

Regardless of what's switched on in the portal, owners' statutory rights to inspect or request certain records under their state's strata legislation still apply — the portal's settings are a convenience layer for day-to-day access, not a substitute for those legal rights. If an owner formally requests a record they're legislatively entitled to, that request should be honoured through whatever process applies, portal settings notwithstanding.

Getting information to owners reliably, and being able to prove it was sent, matters more than committees often expect until a dispute makes it matter a lot.

What notices are typically used for

• Meeting notices and agendas
• Updates on planned works or building access
• By-law reminders or breach-related communication
• General announcements the committee wants on the record as having been sent

Why a delivery record matters

A recurring source of dispute in strata is an owner claiming they never received something the committee insists was sent. A stored record of what was sent, to whom, and when removes the guesswork from that argument, whether the dispute is about a meeting notice, a by-law reminder or a breach notice.

Notices versus other communication

Notices are one-way and formal, distinct from Committee Hub's private committee discussion and from informal channels like email threads with individual owners. Anything the committee wants to be able to point to later as "we told you" belongs in a notice, not a casual message.

Sending to a lot versus the whole building

Notices can be targeted — a single lot for something specific to that owner, such as a breach notice, or the whole building for something universal, like a meeting notice or a works schedule. Choosing the right audience avoids both under-informing and unnecessarily broadcasting a matter that only concerns one owner.

What notices don't replace

For matters requiring a formal resolution — spending above the committee's authority, by-law changes — the notice communicates the outcome, but the resolution itself still needs to be properly moved and recorded at a meeting or through a ballot.

Getting owners to report issues in a consistent, trackable way is a common frustration — reports arrive by text, by email, by a comment in the car park, and half of them never make it to a place the committee can actually act on.

What a shareable request form solves

Instead of asking owners to log into a portal (which not every owner wants or needs regularly), a request form can be shared as a simple public link — on a noticeboard, in a welcome pack, or via a notice — that anyone can fill in without an account.

What happens to a submitted request

Once submitted, the request lands in the committee's workflow the same way an internally raised item would — it can be triaged, turned into a tracked maintenance job if relevant, assigned, and followed up, rather than sitting in an inbox waiting to be remembered.

Typical uses

• Reporting a maintenance issue (a leak, a broken gate, a lighting fault)
• General queries or requests to the committee
• Requests specific to a lot, such as a renovation notification, depending on what the committee sets the form up to capture

Why this beats an email address

A generic "committee@" email address tends to become a black hole — messages arrive with no consistent structure, get missed, or get replied to by whoever happens to check it that week. A structured form captures the same information every time and puts it straight into a tracked workflow rather than an inbox.

Keeping it simple for owners

The point of a public form is to lower the barrier for owners to report something, not to make them navigate the same tools the committee uses day to day — owners submitting a request don't need portal access at all to do so.

By-law disputes are one of the more sensitive parts of committee work, partly because getting the process wrong can be as damaging as the underlying breach itself.

What's typically tracked

• The initial complaint or observed breach, with relevant detail (date, description, evidence)
• Any breach notice issued, and when
• Instructions given to a strata or building manager to act on the committee's behalf
• The outcome — resolved, escalated, or referred to a tribunal

Why a clear record matters more than usual here

Disputes are exactly the situation where "we can't quite remember what we sent or when" becomes a real problem — if a breach notice is later challenged, having a dated, complete record of what was issued, on what basis, and what response (if any) was received puts the committee in a far stronger position.

Manager instruction

Many committees rely on their strata manager to issue formal breach notices and manage the enforcement process, since it needs to be done correctly under the relevant state legislation. Recording the instruction given to the manager — and the manager's actions in response — keeps the committee's own record complete, even though the manager may be running the formal process.

What Flex Strata does and doesn't do

Flex Strata tracks the record of a dispute or breach and the actions taken — it doesn't issue legally binding notices itself or provide legal advice. Breach notices need to comply with your state's specific legislative requirements (form, content, timeframes), so involve your strata manager or a lawyer for anything beyond a straightforward, low-stakes matter.

Escalation

If a dispute can't be resolved directly, most states provide a tribunal or mediation pathway. Having a complete, dated record of the dispute's history — built up through the process rather than reconstructed for the tribunal at the last minute — makes that process considerably less stressful.

Every Australian state and territory gives owners some right to access strata records, but the details — what must be provided, within what timeframe, and whether a fee applies — are set by each state's own legislation rather than a single national rule.

Commonly accessible records

• Meeting minutes and notices
• By-laws and registered amendments
• Insurance details
• The strata roll or equivalent register of owners, generally with some privacy limits on what's shared

What committees commonly get wrong

Assuming a record request needs to be refused because it feels sensitive, when the owner may have a clear legislative right to it; or, at the other extreme, handing over records that go beyond what was actually requested or legislatively required, potentially exposing other owners' private information unnecessarily.

How Flex Strata helps with this

Because documents are organised into categories with clear permissions, and notices and minutes are stored with their history, responding to a legitimate owner request is usually a matter of confirming what's already accessible or exporting the specific record needed — rather than searching through scattered files to work out what exists.

When it's more complicated

Requests that go beyond what's already open to owners, or that raise a question about privacy (for example, personal information about another owner or a contractor), are worth checking against your state's legislation or your manager's advice before responding, rather than guessing.

Setting expectations upfront

Committees that proactively make common records (by-laws, minutes, insurance) visible to owners by default tend to get fewer formal record requests overall, simply because owners can already see what they need without asking.

Keeping track of who's who — and what they should be able to see — gets messier as a committee turns over, unless there's a single place managing it.

Core roles

• Committee roles: chair, secretary, treasurer, ordinary member
• Manager seats: strata manager or building manager, with committee-set access
• Owner seats: for owners without a committee position, generally with more limited default access

What changes with a role

Assigning a role sets a sensible default level of access for that type of user, which the committee can then fine-tune page by page using the permissions described elsewhere in this hub. A newly invited treasurer, for instance, starts with relevant defaults rather than needing every permission configured manually from scratch.

Managing turnover

When someone's position changes — elected out at an AGM, resigning mid-term, or simply changing role from secretary to chair — updating their entry in people management immediately reflects the change in what they can see, without needing to delete and recreate their account.

Multiple roles and buildings

Some people wear more than one hat — an owner who's also on the committee, or a manager who oversees several buildings on Flex Strata. People management keeps these distinct so access is correct for each context rather than blending together.

Why this matters for governance

Clear, current role records mean access always reflects who's actually elected or serving, which matters if a decision's validity is ever questioned — a resolution passed with someone voting in a role they no longer held is exactly the kind of technicality worth avoiding.