11 June, 2026
A few small habits are behind most data hygiene issues at KAUST. Here is what they look like and what to do instead.
Sharing is how work gets done at KAUST. The problem is not the act of sharing. It is the default settings, the forgotten links, and the access that quietly outlasts the reason it was created. Small choices add up across files, folders, and sites in ways nobody planned for.
Here are four habits worth fixing.
Anyone links require no sign-in and can be forwarded to people you never intended to include. There is no way to know who ultimately uses them. KAUST does not currently impose a maximum sharing-link lifetime. A link without a suitable end date can remain available much longer than intended.
Use Anyone links only for information approved for public disclosure. For other information, consider a Specific People link limited to authorized recipients. Also check existing direct permissions and other links.
A useful test: was this information approved for public disclosure? If not, do not use Anyone.
Temporary sharing has a way of becoming permanent. A contractor reviews a document. An external collaborator contributes to a project. The work ends, but the access stays.
Where the sharing option supports it, set an expiration date that matches the work, such as a project end or review deadline. Otherwise, set a date to review or remove access.
If access needs to continue, review the reason and extend or renew it when appropriate. Broad sharing without an end date needs a strong, continuing reason.
SharePoint sites can end up giving access to far more people than intended, often because a default was never reviewed after setup. Most of those people will never stumble across the content. But the access is there.
This matters more now. As AI tools become available, existing permissions deserve another look. These tools work within applicable access controls, but broad access can make information available to more people than intended. Review permissions according to the information and its authorized audience.
If you manage a SharePoint site, check who has access. The goal is not to lock everything down. The goal is to make sure the access reflects the actual intent.
When a colleague changes teams or departments, some access may continue through direct sharing, groups, or site permissions. Do not assume a role change automatically removes everything.
When a project wraps up, review the sharing on the main files and remove anyone who no longer needs it.
When a colleague moves to a new role, check whether they still have direct access to things you shared with them personally.
The Shared view in OneDrive is a useful starting point, but it is not a complete inventory of all permissions. Review specific links, direct access, and relevant group or site permissions.
Before sharing, the question is not whether there is a reason not to. It is whether this person genuinely needs this access, and for how long. That shift, from sharing as a default to sharing as a deliberate choice, is what responsible data stewardship looks like in practice.
If information needs to remain publicly available indefinitely, an approved public website is a better home than an open OneDrive or SharePoint link. Request a website. GBC approval is required before Internet publication.