Named-user sharing versus public links, smallest-useful permissions, expiry dates and link passwords - sharing without leaking.
Sharing is the reason the cloud exists - and the way most home clouds eventually leak something. ownCloud gives you two very different tools, named sharing and public links, plus three small settings that decide how much damage a forwarded link can do. This page is the short, honest discipline for all of them.
ownCloud shares in two ways, and confusing them is where leaks begin. Sharing with a named user or group keeps the file inside your cloud - the person logs in, and you can unshare them personally at any time. A public link is different: anyone who has the link has the access, logged in or not. Links are perfect for one photo for grandma and dangerous for the office accounts folder - not because the feature is bad, but because a link can be forwarded, and you will never know.
Every permission you do not grant is an accident that cannot happen.
Most shares are needed for days. Set the expiry date when you create the link and the share cleans itself up - the forgotten forever-link is the classic home-cloud leak. For anything private, add a link password and send it by a different channel than the link itself: link by email, password by phone call. A forwarded email then still does not open the file.
Classic ownCloud shows you what you have shared - spend two minutes there monthly. Unshare what the project no longer needs, check nothing sensitive is sitting on a public link, and look at who inside the office can see the shared folders. Sharing is ownCloud whole point - this review is simply how it stays a feature instead of becoming the incident report.
The video builds the cloud - this page keeps what you share from it under your control.
Watch Full VideoYes - anyone holding the link can forward it, and every new holder gets the same access until the link expires or you delete it. That is why private material belongs behind named-user sharing or, at minimum, a password-protected link with an expiry date.
Treat the honest answer as no, not reliably enough to lean on. Public links are designed for easy access, not for audited access. If knowing exactly who opened a file matters, share it with a named user account instead of a link.
Create a dedicated upload folder and share it with upload permission and an expiry date, ideally with a link password. When the job is done, the link dies on schedule and the folder holds only what was sent to you.