Disability and Interpreting Services · Melbourne, VIC

Building a Structured Workspace Foundation for a Disability Services Provider

OfficePro Consulting delivered a series of SharePoint Foundation Workshops for a Melbourne disability and interpreting services provider, moving the team off a single shared login toward a structured Microsoft 365 workspace. An Operations SharePoint site was created during the engagement, with document libraries, a simple permissions model and a plan to retire the shared logins.

Live workshops, run remotely
1 Operations site created
SharePoint · Microsoft Teams · Microsoft 365
Discuss your SharePoint project →
Live
Hands-on workshops, screen shared
1 site
Operations site built during the engagement
Clear model
What goes where across Teams, SharePoint and OneDrive
Reference pack
Delivered to the team after the training

The challenge: one login, shared by everyone

The whole team worked from a single shared login, one account holding the email, the OneDrive and the calendar. A second shared login sat behind the bookings system. It felt convenient, but it created real problems.

One shared login
The whole team signs into a single account for email, files and calendar
!
OneDrive as a shared drive
Files treated like a local drive across the team
Sync conflicts
!
Competing versions
People edit out of sync and overwrite each other
Version clashes
!
No audit trail
Nobody can see who changed what
No accountability
!
Messy offboarding
Nobody can be removed cleanly from a shared account
Access stuck
1 login
Shared by the whole team
2 shared
Logins in use, including the bookings system
No trail
No way to see who changed what
No split
Access could not be separated by role

What we built

A series of SharePoint Foundation Workshops, run live and screen shared, that set up the foundation during the engagement rather than leaving a list of things to do.

1
Working model and structure. We started with when to use Microsoft Teams, when to use SharePoint and when to use OneDrive, then created an Operations SharePoint site with document libraries mapped to how the team actually works, not a copy of the old folder tree.
2
Access and governance. A simple Owners, Members and Visitors model backed by security groups, with the rule of groups over individuals and access restricted only where needed, plus governance house rules for naming, who can create sites and how permission changes are requested.
3
Retiring shared logins and onboarding. A plan to move to proper Microsoft 365 patterns, a shared mailbox, a group calendar, SharePoint libraries and security groups and a first version of external onboarding using SharePoint and Microsoft Forms, with a save and resume onboarding portal scoped as a follow-up build.

How it works

The Operations SharePoint site holds the team's working files in document libraries mapped to how they actually work, rather than a copy of the old folder tree. Access runs on a simple model of Owners, Members and Visitors, backed by security groups added into the default SharePoint groups, so permissions are granted to groups rather than named people and restricted only where needed, such as a private library for HR or finance.

The plan to retire the shared logins uses proper Microsoft 365 patterns: a shared mailbox for shared email, a group calendar for the shared calendar, SharePoint libraries for shared files and security groups for access. A first version of external onboarding uses SharePoint and Microsoft Forms, with a save and resume portal scoped as a separate follow-up build.

Engagement snapshot

TypeWorkshops + live setup
FormatRemote
Site createdOperations
DeliveryLive, hands-on

What the training covered

1
Goals and current setup
2
Teams vs SharePoint working model
3
Identity and shared logins
4
SharePoint structure build
5
Permissions and governance
6
External onboarding discussion

Technologies

SharePointMicrosoft TeamsOneDriveMicrosoft 365 GroupsSecurity GroupsMicrosoft Forms

Related services

This engagement drew on our SharePoint and client portal services to set the workspace foundation and scope the onboarding build.

View all services →

The results: a foundation set up once, properly

What changed by the end of the workshops, from a shared login to a structured workspace.

Per person
Each person moving to their own access
One shared login→Per-person access
Structured
Libraries mapped to real workflows
OneDrive clashes→SharePoint libraries
Live site
Operations site built during the engagement
No structure→Operations site
Role-based
Owners, Members and Visitors model
Ad hoc sharing→Defined roles
The team finished the training with a working foundation rather than a to-do list. The Operations site was live, with libraries that match how they work and they had a clear model for Microsoft Teams, SharePoint and OneDrive so files stop landing in the wrong place. They also had a defined plan to move every person onto their own access and retire the shared logins. The team set their own next steps: stand up Microsoft Teams, migrate data across and then book a follow-up session for the external SharePoint publishing site.
Facing a similar challenge?
Tell us what your team is dealing with. We will show you what is possible.
TALK TO US →

More client stories

More from our recent work.

Ready to structure your workspace?

Tell us how your team shares files and logins today. We'll map out what a structured SharePoint foundation looks like for your organisation, what it takes to set up and whether it's the right move. No commitment, no sales pitch.
contact@officeproconsulting.com.au
1300 160 336Talk to an Australian consultant
Australia BasedRemote and on-site consulting services available Australia-wide
Microsoft Partner logo
Thanks. Your enquiry has been sent. We’ll get back to you within 1 business day.