How AusLanka Keeps Business, Organiser, Staff and Admin Access Separate
A plain-English guide to AusLanka account roles, why access is separated and how members, business owners, organisers and event staff use the right pathway.
6 August 20267 min readAusLanka Editorial Team
One AusLanka account can help a community member discover businesses and events, while approved responsibilities allow the right people to manage business or event work. The important word is right. Someone who can update a business profile should not automatically control an event, and a volunteer helping at one event should not receive broad access to everything.
This separation protects people, organisations and the quality of information on the platform. It also avoids the classic committee problem where everybody thinks somebody else has the key—until the hall door is still locked and guests are arriving.
This article explains the public purpose of AusLanka roles in plain English. It intentionally does not describe security systems, private administration tools or sensitive technical details.
Start with a community member account
A normal member account is the starting point for everyday participation. Members can use the public and member features currently available to discover community information, browse businesses and events, and manage their own relevant activity.
Being a member does not automatically make someone a business owner, event organiser, staff member or platform administrator. Those responsibilities follow separate approval or invitation pathways.
Why separate roles matter
Different activities carry different responsibilities. Updating your own contact preferences is not the same as publishing a business address. Creating an event is not the same as checking tickets at the door. Platform-wide administration is different again.
Separating roles supports three useful principles:
People receive only the access needed for their task.
Responsibility stays connected to the correct business or event.
Important actions can follow the appropriate approval and review process.
It is the digital version of an organised community function: the treasurer, stage manager and tea table volunteers all help, but nobody needs every clipboard.
Business owner or business manager responsibilities
An approved business role is for managing information connected to a particular business profile. Depending on the options currently available, this may include maintaining public business details and using relevant business management features.
A business role may involve:
Keeping the business name, description and contact details accurate
Maintaining opening hours, location and service information
Adding appropriate images, products, services, menus, offers or updates
Reviewing business activity available in the dashboard
Helping customers find current, useful public information
A business role should only be used by someone authorised to represent that business. If ownership changes or a manager leaves, review access promptly rather than leaving an old invitation floating around like a forgotten event banner in the garage.
Event organiser responsibilities
An organiser role is for creating or managing eligible events through the available organiser pathway. It is separate from business management because an event may be run by an association, community group, promoter or individual organiser rather than a listed business.
An organiser may be responsible for:
Publishing accurate event information
Choosing the appropriate listing or ticketing model
Maintaining dates, times, venue and accessibility details
Managing attendee communication and event changes
Coordinating authorised staff for supported event-day tasks
Organiser approval does not mean the person can manage every event on AusLanka. Responsibility remains connected to the events they are authorised to work with.
Event staff and scanner responsibilities
Some events need staff or volunteers to support entry. These roles should be limited to the event and tasks they have been invited to perform. A person helping scan or check tickets does not need broad control over unrelated organiser or business information.
Good event-staff practice
Invite only people who genuinely need access.
Explain the task and the event-day process before doors open.
Ask staff to use their own authorised account rather than sharing logins.
Keep attendee information private and use it only for the event task.
Remove or review access after the event when it is no longer needed.
Sharing one password among ten volunteers may feel quick, but so does putting all the sambol in one unlabelled container. Confusion arrives immediately.
Platform administration is different
Administration responsibilities exist to support and operate the platform. They are not ordinary community, business or event roles, and they are not granted simply because someone is prominent in a group or helps organise an event.
For safety, AusLanka does not publish detailed explanations of internal administration systems, permission structures or security operations. Community users do not need that information to choose the correct public pathway.
Use the correct pathway
If you want to manage a business
Use the current business application, claim or invitation pathway shown by AusLanka. Provide truthful information and make sure you are authorised to act for the business.
If you want to organise events
Use the organiser application or approval pathway currently available. Approval may involve checks relevant to the organiser function.
If you are helping at an event
Accept only the event-specific invitation provided by the authorised organiser. Ask the organiser what the role includes and how long it is needed.
If you only want to attend or explore
A member account is enough for the relevant community experience. You do not need an organiser or business role to browse public listings or attend events.
Never share an account
Each person should use their own account. Shared accounts make it harder to know who made a change, remove access when somebody leaves or protect personal information.
If a colleague needs access, use the appropriate invitation or support pathway. Do not send them your password, verification message or sign-in code. AusLanka support should never need your password.
Review access when circumstances change
Community groups and small businesses change over time. Committee members rotate, staff move on and volunteers finish their event-day shift.
Build a simple review into your process:
List who currently has an approved responsibility.
Confirm each person still needs it.
Check that the correct business or event is attached.
Remove or request help with outdated access.
Update the authorised contact when leadership changes.
A short review after each major event or committee handover is much easier than untangling access two years later.
What to do if access looks wrong
If you can see a responsibility you no longer need, or you believe someone has inappropriate access to a business or event, do not try to investigate other people’s accounts. Record the relevant public details and contact AusLanka through the official support path.
Never publish screenshots containing personal information, ticket details, private contact data or administration screens. Share only what support requests through the appropriate private channel.
A simple rule to remember
Use your member account for your own community activity. Use a business role only for a business you are authorised to manage. Use an organiser role for your approved events. Give event staff only the event-specific responsibility they need. Leave platform administration to authorised platform personnel.
Clear roles make AusLanka safer and easier to use. Everyone can focus on their part of the job—and the person checking tickets does not accidentally become responsible for rewriting the restaurant menu.
Choose the right AusLanka path
Visit the relevant AusLanka business, organiser or help area and follow the pathway that matches your real responsibility. If you are unsure, contact official support before sharing information or accepting an invitation.
