S-115 · Detailed guide · Theme 5

Secure Shared Drive Guide

Members can find shared files while sensitive information remains appropriately restricted.

Where this idea came from

Playbook entry: S-115 · Secure Shared Drive Guide
Theme: Theme 5: Digital, Data & Systems · Subtheme 8: Cybersecurity & Risk
Source material: Current playbook index title and category plus an internally authored detailed-guide draft

Initiative-specific development wave

How this draft was developed

These sources support general principles for digital, data and systems, accessibility, privacy, safety, systems or responsible governance; they are not an endorsement of Secure Shared Drive Guide, a finding that it suits any club or approval of its local design.

Primary references consulted

Rotary Clubs (Rotary International)
Used for: Rotary describes club participation through service, friendship, diversity, integrity and leadership, including online participation for people affected by schedules, mobility or distance.
Small business cyber security guide (Australian Signals Directorate's Australian Cyber Security Centre)
Used for: A practical security baseline includes multi-factor authentication, software updates, regular tested backups and advice suited to the organisation's actual systems and risk.
Chapter 11: APP 11 Security of personal information (Office of the Australian Information Commissioner)
Used for: Entities covered by the Privacy Act must take reasonable steps to protect personal information and destroy or de-identify it when it is no longer needed, subject to lawful retention requirements.
Quick reference guide for responding to data breaches (Office of the Australian Information Commissioner)
Used for: Organisations should contain, assess and respond to suspected data breaches, determine applicable notification duties and review the event to reduce recurrence.

Candidate District material consulted

These records remain draft evidence and still need a human source decision.

Theme_4_All_80_Initiatives_Complete
The exact current-title crosswalk establishes a candidate legacy record for later comparison. No legacy code, unsupported claim or unchecked operational detail was copied into this draft; current official privacy, security, accessibility and governance controls take precedence.

Theme 5 source-assurance wave

What has been checked

4 current primary pages used by this guide were reopened on 9 August 2026.
4 attributed source claim(s) were mapped to their bounded use in this initiative.
Candidate District material remains separate and does not establish this result.

See each source's scope and limit

Rotary Clubs
Supports: Rotary club participation context and the value of accessible online or hybrid participation.
Does not establish: Product configuration, legal compliance, local suitability or approval of a named initiative.
Small business cyber security guide
Supports: A practical minimum cyber-security baseline for smaller organisations and volunteer-run systems.
Does not establish: That the baseline is sufficient for a club's actual risk, system architecture, supplier arrangements or legal obligations.
Chapter 11: APP 11 Security of personal information
Supports: Security, access, retention and disposal safeguards where the Privacy Act and APP 11 apply.
Does not establish: That a club's controls are reasonable, that the Privacy Act applies or that a particular retention period is correct.
Quick reference guide for responding to data breaches
Supports: A proportionate sequence for preparing for and responding to suspected personal-information breaches.
Does not establish: Whether an incident is an eligible data breach, who must be notified or the club's legal duties in a specific event.

What still needs a person to confirm

Confirm which privacy, records, safeguarding and other legal duties apply to the club and this local design.
Confirm current ClubRunner or other platform features, permissions, licence settings and supplier instructions in the club's actual account.
Test accessibility and alternative participation routes with affected members rather than inferring conformance from the guide.
Confirm every local fact, starting point, measure, cost, owner and claim before the club decides to proceed.
Resolve any candidate District-source provenance and approval decision without treating the candidate as controlled authority.

The source-verification release gate remains closed.

Checks still on hold

The current Theme 5 index controls the code and title. The exact-title legacy Digital candidate is recorded only as attributed, unapproved evidence and does not replace current identity, controls or source authority.
The connected Drive refresh returned an internal error on 9 August 2026. No unseen file was inferred or promoted; the 7 August intake, duplicate decisions, quarantines, rights boundaries and public-write permission hold remain in force and no sharing was changed.
Before local delivery, the club must approve the decision, participant choices, access arrangements, privacy and records plan, role boundaries, referral or escalation routes, resource limit and the specific control for this boundary: volunteer capability does not replace professional advice for a serious incident, compromised account, legal duty or complex configuration.
Formal human review has not started. Secure Shared Drive Guide remains an internal initiative-specific draft until all 1,000 initiatives reach the Full-Corpus Review Build and every source, editorial, local-suitability, accessibility and governance gate is resolved.

Still an internal draft: source interpretation, local suitability, accessibility, governance and editorial approval remain open checks.

Why a club might use this

It protects trust by making safer system and information habits part of everyday club work.

It may suit: Members who use or look after club systems and information, including people who need extra help.

Use it when

Consider Secure Shared Drive Guide when access, passwords, devices, backups or incident responsibilities are unclear.
A club where the club has a defined user need, accountable owner, current platform information, proportionate data plan and a safe way to test and reverse the change.
A club with a real need for practical cyber resilience and capacity to support a maintained club artefact with a defined user, owner, version, source of truth and review cycle.
A 90-day trial of Secure Shared Drive Guide with a starting point, named participants, a resource ceiling and a scheduled continue, adapt or stop decision.

Before the club starts

A board-approved brief naming which accounts, devices, data and response capability the club will protect first, the local authority, people affected, fixed constraints, resource ceiling, decision date and stop conditions.
A starting-point record and participant plan suited to a maintained club artefact with a defined user, owner, version, source of truth and review cycle, with accessible information, voluntary choices and a supported alternative route where needed.
Named delivery, evidence and decision owners, including a person authorised to pause Secure Shared Drive Guide when a safeguard, permission or boundary is not met.
A proportionate check of governing documents, privacy, information security, accessibility, conflicts, safeguarding, work health and safety, records, finance and referral duties for the actual local design.

Capacity guide

Likely cost: Moderate if devices, password management or specialist support are needed
Lead time: 4–8 weeks for the first security uplift
People: A board sponsor, cyber safety owner and authorised system administrators

A useful club conversation

Questions worth asking

Whose experience, authority, access or safety could be missed if Secure Shared Drive Guide is designed only by regular attendees, confident digital users or current leaders?
What would make a tested current version with ownership, access, change and retirement controls credible enough for the club's decision, and what would still remain uncertain?
What local adaptation would still respect this boundary: Volunteer capability does not replace professional advice for a serious incident, compromised account, legal duty or complex configuration.

Common traps

Trying Secure Shared Drive Guide when A club with no open decision, no accountable owner, no capacity to act on a tested current version with ownership, access, change and retirement controls or no safe way to pause the trial.
Proceeding with Secure Shared Drive Guide when Secure Shared Drive Guide must not be used for collecting more data because it is possible, using live sensitive data for training, automating formal judgement or deploying an unowned system without privacy, security, accessibility and recovery controls. Volunteer capability does not replace professional advice for a serious incident, compromised account, legal duty or complex configuration.
A volunteer-built workflow becomes unowned, inaccurate or impossible to recover. — Name a service owner, document dependencies, keep tested backups and rollback steps and schedule a maintenance decision.

A practical 90-day path

Three milestones for Secure Shared Drive Guide
When	What the club does	Evidence to keep
Days 1–30: Agree the local design	Write the decision brief for Secure Shared Drive Guide: define which accounts, devices, data and response capability the club will protect first, the starting evidence, people affected, local authority, resource limit, success signals and stop conditions. Identify users and non-users, map access and digital-confidence barriers, explain data use and permissions and retain an equivalent human or non-digital route where essential participation is involved. Apply this specifically to Secure Shared Drive Guide and record which relevant experiences or users are still missing.	An approved decision and boundary brief A participant, access and information-handling plan
Days 31–60: Run and adjust the first version	Build and test a maintained club artefact with a defined user, owner, version, source of truth and review cycle for Secure Shared Drive Guide; complete the Secure Shared Drive Guide System Ownership and Version Register, rehearse the boundary wording and confirm who may decide, refer, pause, recover or close the work. Use synthetic or minimised test data, least privilege, versioned configuration, accessible instructions, exception handling and a rollback; do not expose live credentials or private member information. Capture only the evidence needed to judge whether Secure Shared Drive Guide advances practical cyber resilience.	A tested system ownership and version register and delivery pack A controlled activity and evidence record
Days 61–90: Review the evidence and decide	Compare the evidence with the starting point, validate meaning with affected participants or users, record gaps and unintended effects and prepare a tested current version with ownership, access, change and retirement controls without overstating what the trial proves. Make and record the authorised continue, adapt, refer, scale or stop decision for Secure Shared Drive Guide; explain the reason, complete every action, close unnecessary records and schedule the 90-day follow-up.	A tested current version with ownership, access, change and retirement controls A published participant response, closed action register and next-step decision

Fit it to the club you have

Small club

Choose the smallest maintainable system, use shared role-based administration rather than one person's account and retain printable or telephone alternatives. Apply this specifically to Secure Shared Drive Guide, a maintained club artefact with a defined user, owner, version, source of truth and review cycle and the club's actual capacity.

Larger club

Separate data, platform, content and approval roles, use staged permissions and keep a shared change and incident register. Apply this specifically to Secure Shared Drive Guide, a maintained club artefact with a defined user, owner, version, source of truth and review cycle and the club's actual capacity.

Regional or rural club

Design for variable connectivity, older devices and limited local support, with offline continuity and clear escalation to a trusted specialist. Apply this specifically to Secure Shared Drive Guide, a maintained club artefact with a defined user, owner, version, source of truth and review cycle and the club's actual capacity.

Metropolitan, hybrid or online club

Test across devices, assistive technology and channels, provide captions and accessible documents and keep equivalent controls for remote users. Apply this specifically to Secure Shared Drive Guide, a maintained club artefact with a defined user, owner, version, source of truth and review cycle and the club's actual capacity.

Learn, adapt and know when to stop

Evidence worth keeping

Secure Shared Drive Guide produces a tested current version with ownership, access, change and retirement controls by the promised decision date, with evidence limitations, participation gaps and unintended effects stated.
People affected can explain the purpose, their choices, the boundary and how to raise an access, privacy, safety or governance concern.
The trial shows whether practical cyber resilience improved from the recorded starting point without shifting hidden workload, risk or exclusion elsewhere.

Change course when

The club proceeds with Secure Shared Drive Guide without respecting this boundary: volunteer capability does not replace professional advice for a serious incident, compromised account, legal duty or complex configuration. — Put the boundary in the brief and participant information, give the delivery lead stop authority and move any excluded matter to its responsible process.
The system excludes members or creates a single digital path for essential participation. — Test with varied users, provide accessible instructions and retain an equivalent supported alternative.
Permissions, integrations or exports expose more personal information than the purpose requires. — Minimise fields, use least privilege, test permissions, control exports and review access after the trial.

How to put it into practice

Detailed implementation steps for Secure Shared Drive Guide
Step	Action	Suggested owner	Timing	Evidence or output
1	Write the decision brief for Secure Shared Drive Guide: define which accounts, devices, data and response capability the club will protect first, the starting evidence, people affected, local authority, resource limit, success signals and stop conditions.	Board sponsor and information owner	Week one	An approved decision and boundary brief
2	Identify users and non-users, map access and digital-confidence barriers, explain data use and permissions and retain an equivalent human or non-digital route where essential participation is involved. Apply this specifically to Secure Shared Drive Guide and record which relevant experiences or users are still missing.	Board sponsor and information owner with the access and privacy contacts	Weeks one and two	A participant, access and information-handling plan
3	Build and test a maintained club artefact with a defined user, owner, version, source of truth and review cycle for Secure Shared Drive Guide; complete the Secure Shared Drive Guide System Ownership and Version Register, rehearse the boundary wording and confirm who may decide, refer, pause, recover or close the work.	System lead, privacy contact and access tester	Before the trial	A tested system ownership and version register and delivery pack
4	Use synthetic or minimised test data, least privilege, versioned configuration, accessible instructions, exception handling and a rollback; do not expose live credentials or private member information. Capture only the evidence needed to judge whether Secure Shared Drive Guide advances practical cyber resilience.	System lead, privacy contact and access tester	Weeks three to eight	A controlled activity and evidence record
5	Compare the evidence with the starting point, validate meaning with affected participants or users, record gaps and unintended effects and prepare a tested current version with ownership, access, change and retirement controls without overstating what the trial proves.	System lead, privacy contact and access tester with an independent reviewer	Within seven days of the trial	A tested current version with ownership, access, change and retirement controls
6	Make and record the authorised continue, adapt, refer, scale or stop decision for Secure Shared Drive Guide; explain the reason, complete every action, close unnecessary records and schedule the 90-day follow-up.	Service owner and independent reviewer	By day 90	A published participant response, closed action register and next-step decision

Controls and safeguards

Check the selected approach against the club's actual needs, capacity and responsibilities before putting it into use.
Name the system and data owners, restrict access, provide an accessible alternative and document how errors or failures will be recovered.
The club proceeds with Secure Shared Drive Guide without respecting this boundary: volunteer capability does not replace professional advice for a serious incident, compromised account, legal duty or complex configuration. — Put the boundary in the brief and participant information, give the delivery lead stop authority and move any excluded matter to its responsible process.
The system excludes members or creates a single digital path for essential participation. — Test with varied users, provide accessible instructions and retain an equivalent supported alternative.
Permissions, integrations or exports expose more personal information than the purpose requires. — Minimise fields, use least privilege, test permissions, control exports and review access after the trial.
A volunteer-built workflow becomes unowned, inaccurate or impossible to recover. — Name a service owner, document dependencies, keep tested backups and rollback steps and schedule a maintenance decision.
The current Theme 5 index controls the code and title. The exact-title legacy Digital candidate is recorded only as attributed, unapproved evidence and does not replace current identity, controls or source authority.
The connected Drive refresh returned an internal error on 9 August 2026. No unseen file was inferred or promoted; the 7 August intake, duplicate decisions, quarantines, rights boundaries and public-write permission hold remain in force and no sharing was changed.
Before local delivery, the club must approve the decision, participant choices, access arrangements, privacy and records plan, role boundaries, referral or escalation routes, resource limit and the specific control for this boundary: volunteer capability does not replace professional advice for a serious incident, compromised account, legal duty or complex configuration.
Formal human review has not started. Secure Shared Drive Guide remains an internal initiative-specific draft until all 1,000 initiatives reach the Full-Corpus Review Build and every source, editorial, local-suitability, accessibility and governance gate is resolved.

What to measure

After 90 days, review Secure Shared Drive Guide. Look for current access records, stronger authentication, tested recovery and incidents being contained, recorded and reviewed promptly.
Secure Shared Drive Guide produces a tested current version with ownership, access, change and retirement controls by the promised decision date, with evidence limitations, participation gaps and unintended effects stated.
People affected can explain the purpose, their choices, the boundary and how to raise an access, privacy, safety or governance concern.
The trial shows whether practical cyber resilience improved from the recorded starting point without shifting hidden workload, risk or exclusion elsewhere.
Every accepted action has an owner, due date and completion evidence, and the club records a reasoned continue, adapt, refer, scale or stop decision.

Follow-up: At the 90-day review, compare the recorded measures with the starting point, resolve the listed governance holds and tell participants whether Secure Shared Drive Guide will change, continue or stop.

Made for this initiative

Tailored supporting documents

These working documents use the decisions, safeguards and evidence needs of this initiative. Complete them with the people affected and keep the agreed version with the club's project record.

Secure Shared Drive Guide User Need and System Boundary Brief

Define the user problem, information flow and excluded uses.

Open supporting document

Secure Shared Drive Guide Data Inventory and Purpose Map

Link every field and transfer to a necessary purpose.

Open supporting document

Secure Shared Drive Guide Privacy, Consent and Notice Check

Make information handling and choices clear before collection or publication.

Open supporting document

Secure Shared Drive Guide Access and Permission Matrix

Apply least privilege and accountable access reviews.

Open supporting document

Secure Shared Drive Guide Accessible User Test Script

Test the real task with varied users and alternatives.

Open supporting document

Secure Shared Drive Guide Configuration and Change Register

Maintain a reviewable record of settings, integrations and releases.

Open supporting document

Secure Shared Drive Guide Incident, Exception and Recovery Card

Give volunteers a safe response route when the workflow fails or data is exposed.

Open supporting document

Secure Shared Drive Guide Handover, Backup and Maintenance Plan

Keep the service operable beyond one volunteer.

Open supporting document

Secure Shared Drive Guide Cybersecurity & Risk Delivery Check

Test whether Secure Shared Drive Guide genuinely advances practical cyber resilience within the subtheme boundary.

Open supporting document

Secure Shared Drive Guide System Ownership and Version Register

Keep the artefact current, findable, controlled and maintainable.

Open supporting document

Secure Shared Drive Guide Evidence, Decision and Close-Out Record

Bring the evidence, limitations, participant response and final decision for Secure Shared Drive Guide into one accountable record.

Open supporting document

Related playbook entries

S-114
S-116

Supporting worksheets

Before your club says yes

Does the idea fit?

Talk with the people it is meant to serve and check that the need is real.

We have checked this

Who can say yes?

Name the person or group that can approve the work, spending and any safety arrangements.

We have checked this

Are people protected?

Check privacy, consent and safety. Collect only the information you genuinely need.

We have checked this

Can everyone take part?

Check the language, format, place, technology and cost for barriers.

We have checked this

Are the facts and permissions right?

Check names, claims, images, quotations, partner references and Rotary branding.

We have checked this

How will we learn?

Note where things stand now, check in at 30, 60 and 90 days, and decide what to do next.

We have checked this